Trace number 209047

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.0SAT 11.6822 11.7419

DiagnosticValue
CHECKS8749640
NODES200

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-7.xml
MD5SUM6c0d7b1018352ff183de92024cdcc4ef
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 benchmark1.43778
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints2053
Maximum constraint arity2
Maximum domain size190
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2053
Global constraints used (with number of constraints)

Solver Data (download as text)

11.71	s SATISFIABLE
11.71	v -2624 2388 2584 -2580 2356 -2500 -2412 -2492 -2484 2308 -2348 -2640 -2472 -2424 -2532 2572 2596 2500 -2284 -2652 2628 2456 -2336 -2532 2504 -2532 2572 -2648 2600 2384 -2640 2492 -2628 -2396 2416 2540 -2640 2520 -2424 -2440 2592 2324 2456 -2444 -2424 -2484 -2524 2616 -2432 -2608 -2456 -2568 -2388 -2656 -2320 2316 -2408 -2472 -2456 2320 2452 -2336 -2428 2512 2492 -2472 -2512 -2332 -2612 -2344 2556 2376 -2600 -2532 2280 2600 -2356 2588 -2600 2328 2280 2280 2280 2616 -2656 -2568 -2528 -2464 2480 -2600 2360 -2440 -2532 -2492 2404 2496 2512 2456 2616 -2656 2632 2640 -2536 2452 -2520 -2512 2568 -2488 -2320 -2288 -2516 -2288 -2360 2588 -2324 2416 2404 -2604 -2292 -2656 2364 -2552 -2480 -2340 -2380 2332 -2484 -2452 2352 2444 -2600 2584 2452 -2464 2340 2472 -2584 2280 -2636 -2624 2372 -2616 -2432 2320 -2420 -2540 2412 -2644 -2416 -2312 2576 2612 2560 2412 2536 -2416 2596 -2364 -2496 -2608 -2416 2496 -2564 2368 2564 -2640 -2492 -2460 2640 -2464 -2288 2528 -2320 -2356 -2316 -2356 -2480 -2384 -2396 -2348 -2584 -2296 2624 -2300 2604 -2608 2552 2320 -2620 -2452 2476 -2328 -2328 -2624 2444 -2616 -2400 -2364 -2296 -2492 
11.71	d CHECKS 8.74964e+06
11.71	d NODES 200
11.71

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/node12/watcher-209047-1168191408 -o ROOT/results/node12/solver-209047-1168191408 -C 1800 -M 900 /tmp/evaluation/209047-1168191408/VALCSP /tmp/evaluation/209047-1168191408/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.75 1.94 1.98 5/95 4525
/proc/meminfo: memFree=1353800/2055920 swapFree=4160348/4192956
[pid=4524] ppid=4522 vsize=1732 CPUtime=0
/proc/4524/stat : 4524 (VALCSP) R 4522 4524 4314 0 -1 4194304 165 0 0 0 0 0 0 0 23 0 1 0 167535800 1773568 143 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 10130240 0 0 4096 0 0 0 0 17 1 0 0
/proc/4524/statm: 433 143 62 8 0 105 0

[startup+0.105296 s]
/proc/loadavg: 1.75 1.94 1.98 5/95 4525
/proc/meminfo: memFree=1353800/2055920 swapFree=4160348/4192956
[pid=4524] ppid=4522 vsize=3712 CPUtime=0.09
/proc/4524/stat : 4524 (VALCSP) R 4522 4524 4314 0 -1 4194304 676 0 0 0 9 0 0 0 23 0 1 0 167535800 3801088 654 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530444 0 0 4096 0 0 0 0 17 1 0 0
/proc/4524/statm: 928 654 64 8 0 600 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3712

[startup+0.513414 s]
/proc/loadavg: 1.75 1.94 1.98 5/95 4525
/proc/meminfo: memFree=1353800/2055920 swapFree=4160348/4192956
[pid=4524] ppid=4522 vsize=9784 CPUtime=0.5
/proc/4524/stat : 4524 (VALCSP) R 4522 4524 4314 0 -1 4194304 2197 0 0 0 49 1 0 0 25 0 1 0 167535800 10018816 2175 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530955 0 0 4096 0 0 0 0 17 1 0 0
/proc/4524/statm: 2446 2175 64 8 0 2118 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 9784

[startup+1.33452 s]
/proc/loadavg: 1.75 1.94 1.98 3/95 4525
/proc/meminfo: memFree=1337480/2055920 swapFree=4160348/4192956
[pid=4524] ppid=4522 vsize=20476 CPUtime=1.32
/proc/4524/stat : 4524 (VALCSP) R 4522 4524 4314 0 -1 4194304 4855 0 0 0 129 3 0 0 25 0 1 0 167535800 20967424 4833 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530955 0 0 4096 0 0 0 0 17 1 0 0
/proc/4524/statm: 5119 4833 64 8 0 4791 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 20476

[startup+2.97181 s]
/proc/loadavg: 1.75 1.94 1.98 3/95 4525
/proc/meminfo: memFree=1323080/2055920 swapFree=4160348/4192956
[pid=4524] ppid=4522 vsize=41860 CPUtime=2.94
/proc/4524/stat : 4524 (VALCSP) R 4522 4524 4314 0 -1 4194304 10195 0 0 0 289 5 0 0 25 0 1 0 167535800 42864640 10173 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530945 0 0 4096 0 0 0 0 17 1 0 0
/proc/4524/statm: 10465 10173 64 8 0 10137 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 41860

[startup+6.2574 s]
/proc/loadavg: 1.77 1.94 1.98 3/95 4525
/proc/meminfo: memFree=1278152/2055920 swapFree=4160348/4192956
[pid=4524] ppid=4522 vsize=84496 CPUtime=6.22
/proc/4524/stat : 4524 (VALCSP) R 4522 4524 4314 0 -1 4194304 20863 0 0 0 611 11 0 0 25 0 1 0 167535800 86523904 20841 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530216 0 0 4096 0 0 0 0 17 1 0 0
/proc/4524/statm: 21124 20841 64 8 0 20796 0
Current children cumulated CPU time (s) 6.22
Current children cumulated vsize (KiB) 84496

Child status: 0
Real time (s): 11.7419
CPU time (s): 11.6822
CPU user time (s): 11.4523
CPU system time (s): 0.229965
CPU usage (%): 99.4916
Max. virtual memory (cumulated for all children) (KiB): 155908

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 11.4523
system time used= 0.229965
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 38770
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= 589

runsolver used 0.016997 s user time and 0.040993 s system time

The end

Launcher Data (download as text)

Begin job on node12 on Sun Jan  7 17:36:48 UTC 2007


IDJOB= 209047
IDBENCH= 4492
FILE ID= node12/209047-1168191408

PBS_JOBID= 3479330

Free space on /tmp= 66318 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp01/fapp01-0200-7.xml
COMMAND LINE= /tmp/evaluation/209047-1168191408/VALCSP /tmp/evaluation/209047-1168191408/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node12/watcher-209047-1168191408 -o ROOT/results/node12/solver-209047-1168191408 -C 1800 -M 900  /tmp/evaluation/209047-1168191408/VALCSP /tmp/evaluation/209047-1168191408/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  6c0d7b1018352ff183de92024cdcc4ef

RANDOM SEED= 138519401

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.265
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.265
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:       1354216 kB
Buffers:         52396 kB
Cached:         371072 kB
SwapCached:       4660 kB
Active:         305076 kB
Inactive:       326520 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1354216 kB
SwapTotal:     4192956 kB
SwapFree:      4160348 kB
Dirty:             636 kB
Writeback:           0 kB
Mapped:         226744 kB
Slab:            54440 kB
Committed_AS:  5404420 kB
PageTables:       2516 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= 66318 MiB



End job on node12 on Sun Jan  7 17:36:59 UTC 2007