Trace number 268576

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 12.5571 12.6795

DiagnosticValue
CHECKS9495370
NODES200

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-10.xml
MD5SUM77e758121f45352fcd7f4ff036be2f28
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.36879
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)

12.64	s SATISFIABLE
12.64	v 2564 -2396 2616 -2508 -2356 -2564 -2572 2492 -2424 -2280 -2320 -2640 2492 2360 -2532 2592 2580 -2432 -2320 2604 -2640 -2512 -2296 -2632 -2320 -2568 -2656 -2648 2580 2400 -2600 -2616 -2344 -2464 -2552 -2472 -2640 -2656 2444 2616 -2592 2280 2504 2464 -2352 -2444 -2532 -2424 -2484 -2616 -2540 -2656 -2432 -2472 -2336 -2396 2420 -2524 -2488 2352 -2656 2420 2356 2512 -2528 -2460 -2492 -2440 -2644 -2416 -2540 2540 -2600 -2532 -2312 -2624 -2360 -2600 -2600 2284 -2392 2296 -2280 2432 -2484 2604 2584 2280 -2656 -2640 -2380 2428 -2452 -2492 -2460 2464 -2500 -2548 2444 2320 2632 2584 -2504 2448 -2536 2416 -2656 -2624 -2320 2612 -2472 -2324 -2444 -2304 -2312 -2508 -2460 2440 -2480 -2580 2420 -2552 -2468 -2320 -2352 -2304 -2420 -2460 -2364 2460 2608 -2612 -2532 2392 -2312 2532 -2604 2280 2636 -2628 -2344 2280 2452 -2352 2480 2524 2420 2280 -2448 -2404 -2384 -2616 -2616 2420 2648 -2500 -2596 2352 2464 -2644 -2500 -2608 -2572 -2380 2400 2568 2492 -2440 2620 2404 -2424 2616 -2420 -2424 -2400 -2376 -2496 -2456 2336 2392 -2588 -2460 -2576 2280 2320 2608 -2456 -2320 -2548 -2460 2432 -2384 -2652 2572 -2404 2540 -2404 -2420 -2336 2488 
12.64	d CHECKS 9.49537e+06
12.64	d NODES 200

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/node16/watcher-268576-1168979493 -o ROOT/results/node16/solver-268576-1168979493 -C 1800 -M 900 /tmp/evaluation/268576-1168979493/VALCSP /tmp/evaluation/268576-1168979493/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.80 1.87 1.55 3/86 18230
/proc/meminfo: memFree=1378968/2055920 swapFree=4191880/4192956
[pid=18229] ppid=18227 vsize=1468 CPUtime=0
/proc/18229/stat : 18229 (VALCSP) R 18227 18229 17795 0 -1 4194304 111 0 0 0 0 0 0 0 20 0 1 0 246344174 1503232 89 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 7640699 0 0 4096 0 0 0 0 17 1 0 0
/proc/18229/statm: 367 89 64 8 0 39 0

[startup+0.104064 s]
/proc/loadavg: 1.80 1.87 1.55 3/86 18230
/proc/meminfo: memFree=1378968/2055920 swapFree=4191880/4192956
[pid=18229] ppid=18227 vsize=3712 CPUtime=0.09
/proc/18229/stat : 18229 (VALCSP) R 18227 18229 17795 0 -1 4194304 676 0 0 0 9 0 0 0 20 0 1 0 246344174 3801088 654 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529359 0 0 4096 0 0 0 0 17 1 0 0
/proc/18229/statm: 928 654 64 8 0 600 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3712

[startup+0.511988 s]
/proc/loadavg: 1.80 1.87 1.55 3/86 18230
/proc/meminfo: memFree=1378968/2055920 swapFree=4191880/4192956
[pid=18229] ppid=18227 vsize=8860 CPUtime=0.49
/proc/18229/stat : 18229 (VALCSP) R 18227 18229 17795 0 -1 4194304 1964 0 0 0 49 0 0 0 24 0 1 0 246344174 9072640 1942 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529339 0 0 4096 0 0 0 0 17 1 0 0
/proc/18229/statm: 2215 1942 64 8 0 1887 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 8860

[startup+1.33283 s]
/proc/loadavg: 1.80 1.87 1.55 3/86 18230
/proc/meminfo: memFree=1363800/2055920 swapFree=4191880/4192956
[pid=18229] ppid=18227 vsize=19024 CPUtime=1.31
/proc/18229/stat : 18229 (VALCSP) R 18227 18229 17795 0 -1 4194304 4487 0 0 0 129 2 0 0 25 0 1 0 246344174 19480576 4465 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529341 0 0 4096 0 0 0 0 17 1 0 0
/proc/18229/statm: 4756 4465 64 8 0 4428 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 19024

[startup+2.96953 s]
/proc/loadavg: 1.80 1.87 1.55 3/86 18230
/proc/meminfo: memFree=1350552/2055920 swapFree=4191880/4192956
[pid=18229] ppid=18227 vsize=38692 CPUtime=2.93
/proc/18229/stat : 18229 (VALCSP) R 18227 18229 17795 0 -1 4194304 9425 0 0 0 289 4 0 0 25 0 1 0 246344174 39620608 9403 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528653 0 0 4096 0 0 0 0 17 1 0 0
/proc/18229/statm: 9673 9403 64 8 0 9345 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 38692

[startup+6.25492 s]
/proc/loadavg: 1.82 1.87 1.55 3/86 18230
/proc/meminfo: memFree=1308440/2055920 swapFree=4191880/4192956
[pid=18229] ppid=18227 vsize=78952 CPUtime=6.18
/proc/18229/stat : 18229 (VALCSP) R 18227 18229 17795 0 -1 4194304 19467 0 0 0 610 8 0 0 25 0 1 0 246344174 80846848 19445 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529332 0 0 4096 0 0 0 0 17 1 0 0
/proc/18229/statm: 19738 19445 64 8 0 19410 0
Current children cumulated CPU time (s) 6.18
Current children cumulated vsize (KiB) 78952

Child status: 0
Real time (s): 12.6795
CPU time (s): 12.5571
CPU user time (s): 12.3721
CPU system time (s): 0.184971
CPU usage (%): 99.0349
Max. virtual memory (cumulated for all children) (KiB): 155908

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 12.3721
system time used= 0.184971
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= 520

runsolver used 0.018997 s user time and 0.043993 s system time

The end

Launcher Data (download as text)

Begin job on node16 on Tue Jan 16 20:31:33 UTC 2007


IDJOB= 268576
IDBENCH= 4493
IDSOLVER= 90
FILE ID= node16/268576-1168979493

PBS_JOBID= 3565980

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp01/fapp01-0200-10.xml
COMMAND LINE= /tmp/evaluation/268576-1168979493/VALCSP /tmp/evaluation/268576-1168979493/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node16/watcher-268576-1168979493 -o ROOT/results/node16/solver-268576-1168979493 -C 1800 -M 900  /tmp/evaluation/268576-1168979493/VALCSP /tmp/evaluation/268576-1168979493/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  77e758121f45352fcd7f4ff036be2f28

RANDOM SEED= 303884846

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:       1379448 kB
Buffers:         61580 kB
Cached:         487412 kB
SwapCached:        448 kB
Active:         200100 kB
Inactive:       399636 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1379448 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:             476 kB
Writeback:           0 kB
Mapped:          69764 kB
Slab:            61596 kB
Committed_AS:  6801136 kB
PageTables:       2316 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 node16 on Tue Jan 16 20:31:46 UTC 2007