Trace number 268526

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, and are wall clock time (not CPU 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
VALCSP 3.1SAT 18.9421 18.9929

DiagnosticValue
CHECKS11284200
NODES150

General information on the benchmark

Namefapp/test01-04/test01/
test01-0150-6.xml
MD5SUMe34066b3c2239e6f93bab53f7980f6c4
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.829872
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables150
Number of constraints1460
Maximum constraint arity2
Maximum domain size302
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1460
Global constraints used (with number of constraints)

Solver Data (download as text)

18.95	s SATISFIABLE
18.95	v 2700 2648 -2436 2304 -2508 2628 -2296 -2496 -2680 -2672 -2420 -2296 -2212 2676 2160 2188 -2584 -2660 -2200 -2660 2700 -2636 -2436 -2700 -2336 2180 2532 -2228 -2660 2636 -2140 -2632 -2632 2684 -2696 2492 -2336 -2232 -2468 -2220 -2588 2528 -2660 -2260 -2184 -2192 2412 -2192 2716 -2468 -2660 -2396 -2576 2588 -2328 -2688 -2700 -2260 -2368 -2240 -2568 -2620 -2684 2384 -2700 2592 -2296 2628 -2120 2264 -2612 -2668 -2644 2644 2672 -2260 2464 -2300 2572 -2180 2292 2680 2256 2260 2508 -2604 2252 -2380 -2600 -2556 2660 -2532 2676 2596 -2516 2596 -2544 2220 -2504 2332 -2300 -2660 2604 -2664 -2452 -2632 -2480 -2344 2656 2336 -2700 -2192 -2572 -2404 2140 2640 -2328 -2660 -2444 -2296 2144 -2556 -2700 2700 2232 2656 -2252 -2660 -2696 -2660 -2644 2212 -2548 -2640 -2152 -2704 2160 -2700 2660 2440 -2200 -2220 -2456 2616 -2180 2396 -2700 2368 -2644 2640 
18.95	d CHECKS 1.12842e+07
18.95	d NODES 150

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node75/watcher-268526-1168979409 -o ROOT/results/node75/solver-268526-1168979409 -C 1800 -M 900 /tmp/evaluation/268526-1168979409/VALCSP /tmp/evaluation/268526-1168979409/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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
Current StackSize limit: 10240 KiB

/proc/loadavg: 1.68 1.71 1.31 3/73 26181
/proc/meminfo: memFree=1785432/2055920 swapFree=4184548/4192956
[pid=26180] ppid=26178 vsize=2404 CPUtime=0
/proc/26180/stat : 26180 (VALCSP) R 26178 26180 26066 0 -1 4194304 352 0 0 0 0 0 0 0 18 0 1 0 246340514 2461696 330 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 7169659 0 0 4096 0 0 0 0 17 0 0 0
/proc/26180/statm: 601 330 64 8 0 273 0

[startup+0.102595 s]
/proc/loadavg: 1.68 1.71 1.31 3/73 26181
/proc/meminfo: memFree=1785432/2055920 swapFree=4184548/4192956
[pid=26180] ppid=26178 vsize=3856 CPUtime=0.09
/proc/26180/stat : 26180 (VALCSP) R 26178 26180 26066 0 -1 4194304 696 0 0 0 9 0 0 0 18 0 1 0 246340514 3948544 674 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528600 0 0 4096 0 0 0 0 17 0 0 0
/proc/26180/statm: 964 674 64 8 0 636 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3856

[startup+0.513643 s]
/proc/loadavg: 1.68 1.71 1.31 3/73 26181
/proc/meminfo: memFree=1785432/2055920 swapFree=4184548/4192956
[pid=26180] ppid=26178 vsize=8212 CPUtime=0.5
/proc/26180/stat : 26180 (VALCSP) R 26178 26180 26066 0 -1 4194304 1804 0 0 0 50 0 0 0 22 0 1 0 246340514 8409088 1782 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528691 0 0 4096 0 0 0 0 17 0 0 0
/proc/26180/statm: 2053 1782 64 8 0 1725 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 8212

[startup+1.33974 s]
/proc/loadavg: 1.68 1.71 1.31 3/73 26181
/proc/meminfo: memFree=1758872/2055920 swapFree=4184548/4192956
[pid=26180] ppid=26178 vsize=17188 CPUtime=1.31
/proc/26180/stat : 26180 (VALCSP) R 26178 26180 26066 0 -1 4194304 4032 0 0 0 130 1 0 0 25 0 1 0 246340514 17600512 4010 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529344 0 0 4096 0 0 0 0 17 0 0 0
/proc/26180/statm: 4297 4010 64 8 0 3969 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 17188

[startup+2.97594 s]
/proc/loadavg: 1.68 1.71 1.31 3/73 26181
/proc/meminfo: memFree=1731928/2055920 swapFree=4184548/4192956
[pid=26180] ppid=26178 vsize=36856 CPUtime=2.94
/proc/26180/stat : 26180 (VALCSP) R 26178 26180 26066 0 -1 4194304 8943 0 0 0 291 3 0 0 25 0 1 0 246340514 37740544 8921 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529339 0 0 4096 0 0 0 0 17 0 0 0
/proc/26180/statm: 9214 8921 64 8 0 8886 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 36856

[startup+6.25432 s]
/proc/loadavg: 1.70 1.72 1.31 3/73 26181
/proc/meminfo: memFree=1653088/2055920 swapFree=4184548/4192956
[pid=26180] ppid=26178 vsize=74872 CPUtime=6.22
/proc/26180/stat : 26180 (VALCSP) R 26178 26180 26066 0 -1 4194304 18478 0 0 0 615 7 0 0 25 0 1 0 246340514 76668928 18456 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529329 0 0 4096 0 0 0 0 17 0 0 0
/proc/26180/statm: 18718 18456 64 8 0 18390 0
Current children cumulated CPU time (s) 6.22
Current children cumulated vsize (KiB) 74872

[startup+12.7171 s]
/proc/loadavg: 1.72 1.72 1.31 3/73 26181
/proc/meminfo: memFree=1495152/2055920 swapFree=4184548/4192956
[pid=26180] ppid=26178 vsize=148660 CPUtime=12.67
/proc/26180/stat : 26180 (VALCSP) R 26178 26180 26066 0 -1 4194304 36927 0 0 0 1253 14 0 0 25 0 1 0 246340514 152227840 36905 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528936 0 0 4096 0 0 0 0 17 0 0 0
/proc/26180/statm: 37165 36905 64 8 0 36837 0
Current children cumulated CPU time (s) 12.67
Current children cumulated vsize (KiB) 148660

Child status: 0
Real time (s): 18.9929
CPU time (s): 18.9421
CPU user time (s): 18.6912
CPU system time (s): 0.250961
CPU usage (%): 99.7326
Max. virtual memory (cumulated for all children) (KiB): 223768

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 18.6912
system time used= 0.250961
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 55709
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= 8
involuntary context switches= 91

runsolver used 0.016997 s user time and 0.054991 s system time

The end

Launcher Data (download as text)

Begin job on node75 on Tue Jan 16 20:30:10 UTC 2007


IDJOB= 268526
IDBENCH= 4305
IDSOLVER= 90
FILE ID= node75/268526-1168979409

PBS_JOBID= 3566230

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/fapp/test01-04/test01/test01-0150-6.xml
COMMAND LINE= /tmp/evaluation/268526-1168979409/VALCSP /tmp/evaluation/268526-1168979409/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node75/watcher-268526-1168979409 -o ROOT/results/node75/solver-268526-1168979409 -C 1800 -M 900  /tmp/evaluation/268526-1168979409/VALCSP /tmp/evaluation/268526-1168979409/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  e34066b3c2239e6f93bab53f7980f6c4

RANDOM SEED= 668929120

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.218
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.218
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1804496 kB
Buffers:         19780 kB
Cached:         154568 kB
SwapCached:       2452 kB
Active:          24404 kB
Inactive:       164520 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1804496 kB
SwapTotal:     4192956 kB
SwapFree:      4184548 kB
Dirty:             796 kB
Writeback:           0 kB
Mapped:          21556 kB
Slab:            48076 kB
Committed_AS:  5086708 kB
PageTables:       1720 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= 66564 MiB



End job on node75 on Tue Jan 16 20:30:32 UTC 2007