Trace number 209159

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.4813 11.5887

DiagnosticValue
CHECKS8305410
NODES200

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-5.xml
MD5SUMd95687246792a6ac7ed4a97541fb6e3f
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.34979
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.56	s SATISFIABLE
11.56	v -2612 2380 2656 -2580 -2312 2520 2472 -2532 -2484 -2304 2344 -2640 2432 -2432 -2492 -2568 -2632 -2552 2280 -2604 2640 -2420 -2332 -2528 -2556 -2496 2632 -2648 2616 2392 2576 2496 2616 -2368 2460 2512 -2640 -2524 -2452 -2608 2572 -2320 2500 -2444 -2460 -2352 -2548 2612 -2508 2592 2440 -2580 -2376 -2444 2308 2352 2336 -2468 2396 -2368 2536 2364 -2420 -2540 -2456 -2492 2492 -2412 2564 -2376 2592 2364 2600 -2532 -2328 -2608 -2296 2600 -2600 2320 2328 2348 2292 2404 2584 2584 -2588 2596 -2648 -2616 2328 -2436 -2572 -2532 -2412 2460 -2532 -2500 -2624 -2608 2612 -2648 -2500 2512 -2532 -2460 2552 -2628 -2320 -2324 -2524 -2280 2336 -2656 -2320 -2540 -2412 -2592 2452 2568 2372 2500 -2476 2320 -2328 -2280 2420 2400 2328 -2460 -2600 -2536 -2432 2420 -2288 2532 -2572 2280 -2584 2604 -2320 -2648 2472 -2288 -2460 -2480 -2360 -2616 2356 -2368 2652 2592 -2484 -2440 2656 -2404 2624 2280 -2460 -2624 -2480 -2616 2508 -2376 2552 -2640 2492 -2420 -2656 2412 -2284 -2620 -2288 -2408 -2336 -2364 -2572 -2336 -2404 -2336 2644 -2404 2616 -2280 -2656 -2608 -2420 2332 -2620 -2400 -2484 2324 -2284 2576 -2392 -2608 -2376 -2372 -2292 -2552 
11.56	d CHECKS 8.30541e+06
11.56	d NODES 200
11.56

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/node34/watcher-209159-1168191778 -o ROOT/results/node34/solver-209159-1168191778 -C 1800 -M 900 /tmp/evaluation/209159-1168191778/VALCSP /tmp/evaluation/209159-1168191778/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: 3.39 3.45 3.11 5/81 12475
/proc/meminfo: memFree=1025304/2055920 swapFree=4192812/4192956
[pid=12474] ppid=12472 vsize=18540 CPUtime=0
/proc/12474/stat : 12474 (runsolver) R 12472 12474 12202 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 167571577 18984960 279 18446744073709551615 4194304 4267372 548682069088 18446744073709551615 254195330343 0 0 4096 24578 0 0 0 17 1 0 0
/proc/12474/statm: 4635 279 244 17 0 2626 0

[startup+0.10818 s]
/proc/loadavg: 3.39 3.45 3.11 5/81 12475
/proc/meminfo: memFree=1025304/2055920 swapFree=4192812/4192956
[pid=12474] ppid=12472 vsize=3712 CPUtime=0.09
/proc/12474/stat : 12474 (VALCSP) R 12472 12474 12202 0 -1 4194304 676 0 0 0 9 0 0 0 20 0 1 0 167571577 3801088 654 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530207 0 0 4096 0 0 0 0 17 1 0 0
/proc/12474/statm: 928 654 64 8 0 600 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3712

[startup+0.516212 s]
/proc/loadavg: 3.39 3.45 3.11 5/81 12475
/proc/meminfo: memFree=1025304/2055920 swapFree=4192812/4192956
[pid=12474] ppid=12472 vsize=9916 CPUtime=0.5
/proc/12474/stat : 12474 (VALCSP) R 12472 12474 12202 0 -1 4194304 2208 0 0 0 49 1 0 0 24 0 1 0 167571577 10153984 2186 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134531029 0 0 4096 0 0 0 0 17 1 0 0
/proc/12474/statm: 2479 2186 64 8 0 2151 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 9916

[startup+1.33728 s]
/proc/loadavg: 3.39 3.45 3.11 3/81 12475
/proc/meminfo: memFree=1008216/2055920 swapFree=4192812/4192956
[pid=12474] ppid=12472 vsize=21004 CPUtime=1.31
/proc/12474/stat : 12474 (VALCSP) R 12472 12474 12202 0 -1 4194304 4977 0 0 0 129 2 0 0 25 0 1 0 167571577 21508096 4955 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530262 0 0 4096 0 0 0 0 17 1 0 0
/proc/12474/statm: 5251 4955 64 8 0 4923 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 21004

[startup+2.97441 s]
/proc/loadavg: 3.39 3.45 3.11 3/81 12475
/proc/meminfo: memFree=993688/2055920 swapFree=4192812/4192956
[pid=12474] ppid=12472 vsize=42916 CPUtime=2.94
/proc/12474/stat : 12474 (VALCSP) R 12472 12474 12202 0 -1 4194304 10465 0 0 0 288 6 0 0 25 0 1 0 167571577 43945984 10443 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530915 0 0 4096 0 0 0 0 17 1 0 0
/proc/12474/statm: 10729 10443 64 8 0 10401 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 42916

[startup+6.25467 s]
/proc/loadavg: 3.36 3.44 3.11 4/81 12475
/proc/meminfo: memFree=948504/2055920 swapFree=4192812/4192956
[pid=12474] ppid=12472 vsize=85948 CPUtime=6.18
/proc/12474/stat : 12474 (VALCSP) R 12472 12474 12202 0 -1 4194304 21244 0 0 0 607 11 0 0 25 0 1 0 167571577 88010752 21222 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530955 0 0 4096 0 0 0 0 17 1 0 0
/proc/12474/statm: 21487 21222 64 8 0 21159 0
Current children cumulated CPU time (s) 6.18
Current children cumulated vsize (KiB) 85948

Child status: 0
Real time (s): 11.5887
CPU time (s): 11.4813
CPU user time (s): 11.2483
CPU system time (s): 0.232964
CPU usage (%): 99.0724
Max. virtual memory (cumulated for all children) (KiB): 155908

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 11.2483
system time used= 0.232964
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= 253

runsolver used 0.012998 s user time and 0.044993 s system time

The end

Launcher Data (download as text)

Begin job on node34 on Sun Jan  7 17:42:58 UTC 2007


IDJOB= 209159
IDBENCH= 4499
FILE ID= node34/209159-1168191778

PBS_JOBID= 3479260

Free space on /tmp= 66536 MiB

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

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  d95687246792a6ac7ed4a97541fb6e3f

RANDOM SEED= 528424972

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.227
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.227
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:       1025720 kB
Buffers:         39220 kB
Cached:         301528 kB
SwapCached:          0 kB
Active:         806876 kB
Inactive:       155112 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1025720 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             336 kB
Writeback:           0 kB
Mapped:         638064 kB
Slab:            52300 kB
Committed_AS:  3506196 kB
PageTables:       3000 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= 66536 MiB



End job on node34 on Sun Jan  7 17:43:10 UTC 2007