Trace number 209015

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.8412 11.9032

DiagnosticValue
CHECKS9322820
NODES200

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-8.xml
MD5SUMc1b791b97abe156da51c58ae8c63048a
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.55776
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.87	s SATISFIABLE
11.87	v -2636 -2396 2576 -2588 -2280 2552 -2464 -2532 -2464 2320 -2280 -2640 2416 -2292 -2492 2656 -2644 -2552 -2280 2608 -2640 -2508 -2340 -2616 -2640 -2496 2616 -2648 2604 -2332 -2600 -2428 -2628 -2464 -2548 -2512 -2588 2572 2440 2492 2556 2320 2488 2504 -2464 -2368 -2532 -2580 -2432 -2540 -2484 -2656 -2348 -2404 -2336 2320 -2364 -2472 -2484 -2320 2468 2320 2436 2512 -2536 -2516 -2492 -2436 -2648 -2364 2604 2480 -2628 -2532 -2344 -2588 -2292 2600 -2600 2280 2280 2376 2356 -2364 2472 2596 2564 -2600 -2532 -2640 -2396 -2424 2572 -2532 -2456 2528 -2476 2488 2512 2616 -2596 2628 -2568 2512 -2436 2416 2580 -2524 -2380 2320 -2468 -2320 2376 2588 2360 -2528 -2456 2604 2476 -2656 -2416 -2552 2384 -2284 -2412 -2308 -2436 -2424 -2376 -2476 -2596 -2556 -2424 2424 -2372 2532 -2596 -2340 2552 -2584 -2348 2656 2456 -2304 -2432 2592 2384 -2656 -2444 -2416 -2620 -2656 -2532 2464 -2332 -2440 -2592 -2400 2528 -2556 -2444 2292 -2572 2324 2564 -2636 2492 -2472 -2644 2400 2408 -2616 -2436 -2424 -2332 -2404 2476 -2404 -2364 -2388 -2624 2280 2536 -2324 -2616 -2608 2456 -2316 -2548 -2424 -2428 -2368 2280 2596 -2408 -2616 -2336 -2416 -2300 -2552 
11.87	d CHECKS 9.32282e+06
11.87	d NODES 200
11.87

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/node7/watcher-209015-1168191335 -o ROOT/results/node7/solver-209015-1168191335 -C 1800 -M 900 /tmp/evaluation/209015-1168191335/VALCSP /tmp/evaluation/209015-1168191335/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: 2.15 2.09 2.02 5/94 25816
/proc/meminfo: memFree=1330976/2055920 swapFree=4192812/4192956
[pid=25815] ppid=25813 vsize=18540 CPUtime=0
/proc/25815/stat : 25815 (runsolver) R 25813 25815 24820 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 167528944 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 244671114535 0 0 4096 24578 0 0 0 17 1 0 0
/proc/25815/statm: 4635 279 244 17 0 2626 0

[startup+0.108719 s]
/proc/loadavg: 2.15 2.09 2.02 5/94 25816
/proc/meminfo: memFree=1330976/2055920 swapFree=4192812/4192956
[pid=25815] ppid=25813 vsize=3844 CPUtime=0.09
/proc/25815/stat : 25815 (VALCSP) R 25813 25815 24820 0 -1 4194304 712 0 0 0 9 0 0 0 20 0 1 0 167528944 3936256 690 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530207 0 0 4096 0 0 0 0 17 1 0 0
/proc/25815/statm: 961 690 64 8 0 633 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3844

[startup+0.516759 s]
/proc/loadavg: 2.15 2.09 2.02 5/94 25816
/proc/meminfo: memFree=1330976/2055920 swapFree=4192812/4192956
[pid=25815] ppid=25813 vsize=9652 CPUtime=0.5
/proc/25815/stat : 25815 (VALCSP) R 25813 25815 24820 0 -1 4194304 2161 0 0 0 49 1 0 0 24 0 1 0 167528944 9883648 2139 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530955 0 0 4096 0 0 0 0 17 1 0 0
/proc/25815/statm: 2413 2139 64 8 0 2085 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 9652

[startup+1.33884 s]
/proc/loadavg: 2.14 2.08 2.02 3/94 25816
/proc/meminfo: memFree=1312992/2055920 swapFree=4192812/4192956
[pid=25815] ppid=25813 vsize=20476 CPUtime=1.32
/proc/25815/stat : 25815 (VALCSP) R 25813 25815 24820 0 -1 4194304 4869 0 0 0 129 3 0 0 25 0 1 0 167528944 20967424 4847 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530867 0 0 4096 0 0 0 0 17 1 0 0
/proc/25815/statm: 5119 4847 64 8 0 4791 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 20476

[startup+2.98302 s]
/proc/loadavg: 2.14 2.08 2.02 3/94 25816
/proc/meminfo: memFree=1297888/2055920 swapFree=4192812/4192956
[pid=25815] ppid=25813 vsize=42124 CPUtime=2.96
/proc/25815/stat : 25815 (VALCSP) R 25813 25815 24820 0 -1 4194304 10266 0 0 0 291 5 0 0 25 0 1 0 167528944 43134976 10244 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530218 0 0 4096 0 0 0 0 17 1 0 0
/proc/25815/statm: 10531 10244 64 8 0 10203 0
Current children cumulated CPU time (s) 2.96
Current children cumulated vsize (KiB) 42124

[startup+6.26536 s]
/proc/loadavg: 2.13 2.08 2.02 3/94 25816
/proc/meminfo: memFree=1250976/2055920 swapFree=4192812/4192956
[pid=25815] ppid=25813 vsize=84496 CPUtime=6.22
/proc/25815/stat : 25815 (VALCSP) R 25813 25815 24820 0 -1 4194304 20863 0 0 0 611 11 0 0 25 0 1 0 167528944 86523904 20841 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530980 0 0 4096 0 0 0 0 17 1 0 0
/proc/25815/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.9032
CPU time (s): 11.8412
CPU user time (s): 11.5902
CPU system time (s): 0.250961
CPU usage (%): 99.4791
Max. virtual memory (cumulated for all children) (KiB): 155908

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 11.5902
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= 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= 370

runsolver used 0.015997 s user time and 0.043993 s system time

The end

Launcher Data (download as text)

Begin job on node7 on Sun Jan  7 17:35:35 UTC 2007


IDJOB= 209015
IDBENCH= 4490
FILE ID= node7/209015-1168191335

PBS_JOBID= 3478985

Free space on /tmp= 66551 MiB

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

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  c1b791b97abe156da51c58ae8c63048a

RANDOM SEED= 479447077

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.220
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.220
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:       1331456 kB
Buffers:         71360 kB
Cached:         267824 kB
SwapCached:          0 kB
Active:         445536 kB
Inactive:       222348 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1331456 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             564 kB
Writeback:           0 kB
Mapped:         356452 kB
Slab:            40644 kB
Committed_AS:  5502440 kB
PageTables:       2992 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= 66551 MiB



End job on node7 on Sun Jan  7 17:35:47 UTC 2007