Trace number 209148

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 1.44478 1.44893

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-9.xml
MD5SUMcef6f21687f99f4d2823ff8263a0f14a
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.44478
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.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.01	c 	variables.............    0
0.02	c 	predicates............    0
0.02	c 	constraints........... 0.16
0.17	c Allocating memory
0.17	c 
0.17	c time limit = -1
0.17	c heuristic = dom/wdeg
0.17	c restart policy = No restart
0.17	c 
0.17	c Solving
0.17	c
1.44	s SATISFIABLE
1.44	v -2600 -2424 2652 2540 2300 2544 -2532 -2492 -2468 2284 -2324 -2580 -2444 -2320 -2532 -2360 -2568 -2484 2308 -2656 -2636 2416 -2320 -2400 -2636 -2540 2616 -2648 2616 2280 -2600 2468 -2636 -2368 -2456 2524 -2640 -2644 -2464 -2592 2592 -2348 -2460 -2428 2404 -2384 2452 2564 2460 -2516 -2504 2604 -2336 -2392 -2320 -2340 2380 -2420 -2356 -2376 2508 2392 -2464 -2452 2500 2532 -2460 -2448 -2616 -2408 -2528 -2500 -2600 -2516 -2320 2584 -2360 2596 2620 2288 -2336 2280 2420 -2352 2616 2580 -2536 2596 -2552 -2640 -2320 -2452 -2532 -2492 2508 2500 2492 -2512 -2576 2616 2632 -2624 -2540 -2532 -2512 -2460 2556 -2576 -2340 2324 -2476 2328 -2412 2596 2332 -2552 2508 -2612 -2408 2628 2468 2492 2492 -2300 2308 2332 -2476 -2392 2280 2436 -2580 -2656 -2492 2444 2348 -2500 -2640 -2380 -2600 -2592 2372 -2656 -2484 2280 2440 2504 -2352 -2608 -2396 -2320 2524 2656 2604 -2432 2280 2460 -2640 2292 2500 -2620 -2464 2320 2412 -2340 2652 -2620 2476 -2480 -2656 -2424 2320 2564 -2360 -2408 -2400 2404 -2552 -2448 2364 2376 -2632 -2352 2612 2340 -2648 -2608 -2420 2380 2580 -2392 2436 2280 -2284 -2616 2424 2588 -2452 2468 -2360 -2492
1.44	d          SAT       157 BTS       1.3 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/node38/watcher-209148-1168191727 -o ROOT/results/node38/solver-209148-1168191727 -C 1800 -M 900 /tmp/evaluation/209148-1168191727/mistral/bin/solver /tmp/evaluation/209148-1168191727/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.07 2.06 1.63 5/81 21622
/proc/meminfo: memFree=1241224/2055920 swapFree=4192812/4192956
[pid=21621] ppid=21619 vsize=6792 CPUtime=0
/proc/21621/stat : 21621 (solver) R 21619 21621 21058 0 -1 4194304 425 0 0 0 0 0 0 0 18 0 1 0 167572488 6955008 404 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8575864 0 0 4096 0 0 0 0 17 1 0 0
/proc/21621/statm: 1698 404 365 92 0 30 0

[startup+0.103863 s]
/proc/loadavg: 2.07 2.06 1.63 5/81 21622
/proc/meminfo: memFree=1241224/2055920 swapFree=4192812/4192956
[pid=21621] ppid=21619 vsize=15724 CPUtime=0.09
/proc/21621/stat : 21621 (solver) R 21619 21621 21058 0 -1 4194304 1603 0 0 0 9 0 0 0 18 0 1 0 167572488 16101376 1571 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 9041531 0 0 4096 0 0 0 0 17 1 0 0
/proc/21621/statm: 3931 1571 706 92 0 2275 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 15724

[startup+0.511961 s]
/proc/loadavg: 2.07 2.06 1.63 5/81 21622
/proc/meminfo: memFree=1241224/2055920 swapFree=4192812/4192956
[pid=21621] ppid=21619 vsize=16516 CPUtime=0.5
/proc/21621/stat : 21621 (solver) R 21619 21621 21058 0 -1 4194304 1817 0 0 0 49 1 0 0 21 0 1 0 167572488 16912384 1785 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134722033 0 0 4096 0 0 0 0 17 1 0 0
/proc/21621/statm: 4129 1785 717 92 0 2473 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 16516

[startup+1.33311 s]
/proc/loadavg: 2.07 2.06 1.63 3/81 21622
/proc/meminfo: memFree=1237000/2055920 swapFree=4192812/4192956
[pid=21621] ppid=21619 vsize=16516 CPUtime=1.32
/proc/21621/stat : 21621 (solver) R 21619 21621 21058 0 -1 4194304 1817 0 0 0 131 1 0 0 25 0 1 0 167572488 16912384 1785 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134709313 0 0 4096 0 0 0 0 17 1 0 0
/proc/21621/statm: 4129 1785 717 92 0 2473 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 16516

Child status: 0
Real time (s): 1.44893
CPU time (s): 1.44478
CPU user time (s): 1.42878
CPU system time (s): 0.015997
CPU usage (%): 99.7134
Max. virtual memory (cumulated for all children) (KiB): 16520

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.42878
system time used= 0.015997
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= 12
involuntary context switches= 60

runsolver used 0.004999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node38 on Sun Jan  7 17:42:08 UTC 2007


IDJOB= 209148
IDBENCH= 4498
FILE ID= node38/209148-1168191727

PBS_JOBID= 3479342

Free space on /tmp= 66510 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  cef6f21687f99f4d2823ff8263a0f14a

RANDOM SEED= 353193723

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.267
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.267
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:       1241832 kB
Buffers:         22720 kB
Cached:         221264 kB
SwapCached:          0 kB
Active:         591836 kB
Inactive:       160472 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1241832 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3296 kB
Writeback:           0 kB
Mapped:         527524 kB
Slab:            46088 kB
Committed_AS:  4399424 kB
PageTables:       2920 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= 66510 MiB



End job on node38 on Sun Jan  7 17:42:10 UTC 2007