Trace number 209052

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
Mistral 2006-12-04SAT 2.88356 2.92975

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)

0.21	c 
0.21	c Parsing xml file
0.21	c 	domains...............    0
0.21	c 	variables.............    0
0.21	c 	predicates............    0
0.21	c 	constraints........... 0.14
0.21	c Allocating memory
0.21	c 
0.21	c time limit = -1
0.21	c heuristic = dom/wdeg
0.21	c restart policy = No restart
0.21	c 
0.21	c Solving
0.21	c
2.90	s SATISFIABLE
2.90	v -2600 2424 2624 -2648 2280 -2568 2472 -2532 -2444 -2280 2320 2632 2424 -2348 -2492 2448 2632 2552 -2288 2652 2568 2416 -2316 2408 -2564 -2484 2580 -2648 2616 -2388 2600 2484 2628 -2392 2456 -2512 -2572 -2492 -2424 -2572 2636 -2328 -2492 -2484 -2412 2376 2524 2580 2464 2616 -2496 2576 -2364 -2396 -2340 2320 2320 2424 -2348 -2336 2524 -2304 -2464 -2508 -2524 -2420 -2452 -2340 2612 -2384 -2592 -2300 2612 -2492 2292 -2616 -2328 2608 2592 2320 2296 2300 2284 2356 2536 2532 -2616 -2524 2532 -2640 -2320 2492 -2572 -2532 2496 2532 2460 2500 2576 -2600 -2596 -2576 -2492 -2512 2452 2460 -2656 2656 -2352 -2348 -2444 -2280 -2424 2588 -2324 2460 2416 2624 2380 2648 2456 2548 -2452 -2408 2292 2364 2432 -2400 -2288 2472 -2612 2652 2512 -2372 -2332 2492 -2640 -2392 -2596 -2640 2404 2640 -2464 2332 -2476 2608 -2360 2644 2308 2328 2540 2620 2532 -2440 -2344 -2340 2636 2284 2532 -2572 -2456 2304 2564 2280 2584 -2572 -2532 2436 -2656 -2464 2280 -2536 -2280 -2432 2288 2380 -2492 -2344 -2340 -2404 -2600 -2344 -2584 -2368 -2604 -2608 2420 2324 2608 -2400 -2484 -2320 2388 -2612 -2416 -2608 -2464 2456 -2356 -2552
2.90	d          SAT      1317 BTS       2.7 s

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/node6/watcher-209052-1168191418 -o ROOT/results/node6/solver-209052-1168191418 -C 1800 -M 900 /tmp/evaluation/209052-1168191418/mistral/bin/solver /tmp/evaluation/209052-1168191418/unknown.xml -v 1 

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.08 2.02 2.01 5/87 17836
/proc/meminfo: memFree=1291496/2055924 swapFree=4165672/4192956
[pid=17835] ppid=17833 vsize=540 CPUtime=0
/proc/17835/stat : 17835 (solver) R 17833 17835 17387 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 167537237 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 2188068 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/17835/statm: 135 26 21 92 0 18 0

[startup+0.105274 s]
/proc/loadavg: 2.08 2.02 2.01 5/87 17836
/proc/meminfo: memFree=1291496/2055924 swapFree=4165672/4192956
[pid=17835] ppid=17833 vsize=15724 CPUtime=0.09
/proc/17835/stat : 17835 (solver) R 17833 17835 17387 0 -1 4194304 1599 0 0 0 9 0 0 0 18 0 1 0 167537237 16101376 1567 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4159428341 0 0 4096 0 0 0 0 17 1 0 0
/proc/17835/statm: 3931 1567 706 92 0 2275 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 15724

[startup+0.516327 s]
/proc/loadavg: 2.08 2.02 2.01 5/87 17836
/proc/meminfo: memFree=1291496/2055924 swapFree=4165672/4192956
[pid=17835] ppid=17833 vsize=16516 CPUtime=0.5
/proc/17835/stat : 17835 (solver) R 17833 17835 17387 0 -1 4194304 1817 0 0 0 50 0 0 0 22 0 1 0 167537237 16912384 1785 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134708954 0 0 4096 0 0 0 0 17 1 0 0
/proc/17835/statm: 4129 1785 717 92 0 2473 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 16516

[startup+1.33742 s]
/proc/loadavg: 2.08 2.02 2.01 3/87 17836
/proc/meminfo: memFree=1287144/2055924 swapFree=4165672/4192956
[pid=17835] ppid=17833 vsize=16516 CPUtime=1.31
/proc/17835/stat : 17835 (solver) R 17833 17835 17387 0 -1 4194304 1817 0 0 0 131 0 0 0 25 0 1 0 167537237 16912384 1785 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134711713 0 0 4096 0 0 0 0 17 1 0 0
/proc/17835/statm: 4129 1785 717 92 0 2473 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 16516

Child status: 0
Real time (s): 2.92975
CPU time (s): 2.88356
CPU user time (s): 2.87356
CPU system time (s): 0.009998
CPU usage (%): 98.4235
Max. virtual memory (cumulated for all children) (KiB): 16520

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.87356
system time used= 0.009998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1828
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= 13
involuntary context switches= 65

runsolver used 0.006998 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node6 on Sun Jan  7 17:36:58 UTC 2007


IDJOB= 209052
IDBENCH= 4492
FILE ID= node6/209052-1168191418

PBS_JOBID= 3478993

Free space on /tmp= 66548 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp01/fapp01-0200-7.xml
COMMAND LINE= /tmp/evaluation/209052-1168191418/mistral/bin/solver /tmp/evaluation/209052-1168191418/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-209052-1168191418 -o ROOT/results/node6/solver-209052-1168191418 -C 1800 -M 900  /tmp/evaluation/209052-1168191418/mistral/bin/solver /tmp/evaluation/209052-1168191418/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  6c0d7b1018352ff183de92024cdcc4ef

RANDOM SEED= 514250835

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.240
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.240
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:      2055924 kB
MemFree:       1291976 kB
Buffers:         71740 kB
Cached:         551912 kB
SwapCached:       2424 kB
Active:         172624 kB
Inactive:       506808 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1291976 kB
SwapTotal:     4192956 kB
SwapFree:      4165672 kB
Dirty:            3312 kB
Writeback:           0 kB
Mapped:          66764 kB
Slab:            69280 kB
Committed_AS:  4839032 kB
PageTables:       2376 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= 66548 MiB



End job on node6 on Sun Jan  7 17:37:01 UTC 2007