Trace number 1073816

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock time.

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
mddc-solv 2008-06-09SAT 1.05284 1.07077

DiagnosticValue
CHECKS903

General information on the benchmark

Namecsp/modifiedRenault/
normalized-renault-mod-0_ext.xml
MD5SUM6e539860b9f62610adcc8b9d057e7a96
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.58591
Satisfiable
(Un)Satisfiability was proved
Number of variables111
Number of constraints147
Maximum constraint arity10
Maximum domain size42
Number of constraints which are defined in extension147
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.01	c loading... 1.04 secs
0.97/1.06	c smallest 4
0.97/1.06	c largest 270
0.97/1.06	c average 35.8231
0.97/1.06	
0.97/1.06	s SATISFIABLE
0.97/1.06	v 0 1 5 9 1 1 0 3 1 1 1 0 0 2 1 1 1 0 1 2 2 1 1 1 10 2 3 0 0 0 1 0 22 21 0 1 0 1 0 0 0 0 0 1 2 0 19 0 1 3 1 1 2 1 1 9 1 1 1 0 0 1 2 0 1 2 2 0 1 2 0 9 2 2 3 0 1 1 0 1 6 1 0 0 0 1 1 0 0 0 0 0 0 0 0 3 2 4 0 0 3 0 4 0 2 5 4 3 7 3 0
0.97/1.06	d CHECKS 903
0.97/1.06	c FAILS 2
0.97/1.06	c RESTARTS 0

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.2.5 (c) roussel@cril.univ-artois.fr

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1073816-1215177703/watcher-1073816-1215177703 -o /tmp/evaluation-result-1073816-1215177703/solver-1073816-1215177703 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1073816-1215177703.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2200 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.11 2.04 2.01 4/81 20367
/proc/meminfo: memFree=1671184/2055920 swapFree=4180396/4192956
[pid=20367] ppid=20365 vsize=364 CPUtime=0
/proc/20367/stat : 20367 (solver) R 20365 20367 18900 0 -1 4194304 39 0 0 0 0 0 0 0 19 0 1 0 1996743168 372736 25 996147200 134512640 134773262 4294956240 18446744073709551615 11281188 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/20367/statm: 91 25 19 63 0 3 0

[startup+0.011492 s]
/proc/loadavg: 2.11 2.04 2.01 4/81 20367
/proc/meminfo: memFree=1671184/2055920 swapFree=4180396/4192956
[pid=20367] ppid=20365 vsize=8820 CPUtime=0
/proc/20367/stat : 20367 (solver) R 20365 20367 18900 0 -1 4194304 423 0 0 0 0 0 0 0 19 0 1 0 1996743168 9031680 389 996147200 134512640 134773262 4294956240 18446744073709551615 134561728 0 0 4096 0 0 0 0 17 1 0 0
/proc/20367/statm: 2205 389 334 63 0 1222 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 8820

[startup+0.101416 s]
/proc/loadavg: 2.11 2.04 2.01 4/81 20367
/proc/meminfo: memFree=1671184/2055920 swapFree=4180396/4192956
[pid=20367] ppid=20365 vsize=9104 CPUtime=0.08
/proc/20367/stat : 20367 (solver) R 20365 20367 18900 0 -1 4194304 1530 0 0 0 8 0 0 0 19 0 1 0 1996743168 9322496 1494 996147200 134512640 134773262 4294956240 18446744073709551615 11747031 0 0 4096 0 0 0 0 17 1 0 0
/proc/20367/statm: 2276 1494 338 63 0 1293 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 9104

[startup+0.301429 s]
/proc/loadavg: 2.11 2.04 2.01 4/81 20367
/proc/meminfo: memFree=1671184/2055920 swapFree=4180396/4192956
[pid=20367] ppid=20365 vsize=9576 CPUtime=0.28
/proc/20367/stat : 20367 (solver) R 20365 20367 18900 0 -1 4194304 1596 0 0 0 28 0 0 0 21 0 1 0 1996743168 9805824 1560 996147200 134512640 134773262 4294956240 18446744073709551615 134534554 0 0 4096 0 0 0 0 17 1 0 0
/proc/20367/statm: 2394 1560 338 63 0 1411 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 9576

[startup+0.701469 s]
/proc/loadavg: 2.11 2.04 2.01 4/81 20367
/proc/meminfo: memFree=1671184/2055920 swapFree=4180396/4192956
[pid=20367] ppid=20365 vsize=9444 CPUtime=0.68
/proc/20367/stat : 20367 (solver) R 20365 20367 18900 0 -1 4194304 1625 0 0 0 68 0 0 0 25 0 1 0 1996743168 9670656 1589 996147200 134512640 134773262 4294956240 18446744073709551615 11747031 0 0 4096 0 0 0 0 17 1 0 0
/proc/20367/statm: 2361 1589 338 63 0 1378 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 9444

Solver just ended. Dumping a history of the last processes samples

[startup+0.901493 s]
/proc/loadavg: 2.11 2.04 2.01 4/81 20367
/proc/meminfo: memFree=1671184/2055920 swapFree=4180396/4192956
[pid=20367] ppid=20365 vsize=9812 CPUtime=0.87
/proc/20367/stat : 20367 (solver) R 20365 20367 18900 0 -1 4194304 1648 0 0 0 87 0 0 0 25 0 1 0 1996743168 10047488 1612 996147200 134512640 134773262 4294956240 18446744073709551615 134604215 0 0 4096 0 0 0 0 17 1 0 0
/proc/20367/statm: 2453 1612 338 63 0 1470 0
Current children cumulated CPU time (s) 0.87
Current children cumulated vsize (KiB) 9812

[startup+1.00151 s]
/proc/loadavg: 2.10 2.04 2.01 3/82 20368
/proc/meminfo: memFree=1665864/2055920 swapFree=4180396/4192956
[pid=20367] ppid=20365 vsize=9664 CPUtime=0.97
/proc/20367/stat : 20367 (solver) R 20365 20367 18900 0 -1 4194304 1670 0 0 0 97 0 0 0 25 0 1 0 1996743168 9895936 1634 996147200 134512640 134773262 4294956240 18446744073709551615 11747031 0 0 4096 0 0 0 0 17 1 0 0
/proc/20367/statm: 2416 1634 338 63 0 1433 0
Current children cumulated CPU time (s) 0.97
Current children cumulated vsize (KiB) 9664

Child status: 0
Real time (s): 1.07077
CPU time (s): 1.05284
CPU user time (s): 1.03984
CPU system time (s): 0.012998
CPU usage (%): 98.3258
Max. virtual memory (cumulated for all children) (KiB): 9812

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.03984
system time used= 0.012998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1767
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 7
involuntary context switches= 55

runsolver used 0.004999 second user time and 0.010998 second system time

The end

Launcher Data (download as text)

Begin job on node44 at 2008-07-04 15:21:43
IDJOB=1073816
IDBENCH=56375
IDSOLVER=311
FILE ID=node44/1073816-1215177703
PBS_JOBID= 7881502
Free space on /tmp= 66544 MiB

SOLVER NAME= mddc-solv 2008-06-09
BENCH NAME= CPAI08/csp/modifiedRenault/normalized-renault-mod-0_ext.xml
COMMAND LINE= HOME/solver BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1073816-1215177703/watcher-1073816-1215177703 -o /tmp/evaluation-result-1073816-1215177703/solver-1073816-1215177703 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1073816-1215177703.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 6e539860b9f62610adcc8b9d057e7a96
RANDOM SEED=1138686485

node44.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.213
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.213
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1671664 kB
Buffers:         30624 kB
Cached:         110076 kB
SwapCached:       6316 kB
Active:         286348 kB
Inactive:        36064 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1671664 kB
SwapTotal:     4192956 kB
SwapFree:      4180396 kB
Dirty:            3796 kB
Writeback:           0 kB
Mapped:         198084 kB
Slab:            46652 kB
Committed_AS:  3798808 kB
PageTables:       2196 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66544 MiB
End job on node44 at 2008-07-04 15:21:44