Trace number 207614

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 3.98539 4.02082

General information on the benchmark

Namefapp/test01-04/test01/
test01-0150-10.xml
MD5SUMca801d693e5f281aecf2d953ed79f03d
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 benchmark0.918859
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables150
Number of constraints1460
Maximum constraint arity2
Maximum domain size302
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1460
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.02
0.21	c 	variables.............    0
0.21	c 	predicates............    0
0.21	c 	constraints...........  0.1
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
4.01	s SATISFIABLE
4.01	v -2644 -2632 -2460 -2288 -2572 -2448 2140 2476 -2700 -2700 -2340 -2640 -2332 2680 2404 -2516 -2576 -2660 2372 -2684 -2700 -2700 2432 -2656 -2236 2564 -2620 2476 2628 -2388 -2144 -2604 -2660 -2680 -2144 -2544 2180 2372 2532 -2260 -2620 -2560 -2660 2220 2660 -2332 -2164 -2148 2720 -2548 2624 -2472 2668 2408 -2336 -2672 -2700 -2284 2296 -2412 -2600 -2688 -2544 2148 -2700 -2564 -2196 -2700 2364 -2248 -2396 -2660 2640 -2504 -2700 2344 -2476 2180 -2436 2184 -2188 -2660 -2236 -2140 -2508 -2408 -2372 -2380 2180 2120 -2648 2584 -2660 -2348 2160 -2576 2536 -2324 2516 2228 2384 -2656 2248 -2672 -2124 2660 -2176 -2188 -2636 2600 -2668 2392 -2580 2328 2564 -2220 2424 -2684 -2368 2196 2620 -2536 -2664 -2644 -2352 2184 2468 -2696 -2676 -2688 2208 2508 2580 -2660 -2188 -2632 2256 -2696 2660 -2216 2296 2524 2516 2628 2604 2420 -2648 -2464 2448 -2700
4.01	d          SAT       931 BTS       3.8 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/node30/watcher-207614-1168182507 -o ROOT/results/node30/solver-207614-1168182507 -C 1800 -M 900 /tmp/evaluation/207614-1168182507/mistral/bin/solver /tmp/evaluation/207614-1168182507/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: 1.98 1.81 1.76 5/94 2781
/proc/meminfo: memFree=1292360/2055920 swapFree=4191880/4192956
[pid=2780] ppid=2778 vsize=540 CPUtime=0
/proc/2780/stat : 2780 (solver) R 2778 2780 2360 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 166644649 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7017252 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/2780/statm: 135 26 21 92 0 18 0

[startup+0.104229 s]
/proc/loadavg: 1.98 1.81 1.76 5/94 2781
/proc/meminfo: memFree=1292360/2055920 swapFree=4191880/4192956
[pid=2780] ppid=2778 vsize=13748 CPUtime=0.09
/proc/2780/stat : 2780 (solver) R 2778 2780 2360 0 -1 4194304 1503 0 0 0 9 0 0 0 18 0 1 0 166644649 14077952 1471 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4158769320 0 0 4096 0 0 0 0 17 1 0 0
/proc/2780/statm: 3437 1471 708 92 0 1781 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 13748

[startup+0.512251 s]
/proc/loadavg: 1.98 1.81 1.76 5/94 2781
/proc/meminfo: memFree=1292360/2055920 swapFree=4191880/4192956
[pid=2780] ppid=2778 vsize=14276 CPUtime=0.49
/proc/2780/stat : 2780 (solver) R 2778 2780 2360 0 -1 4194304 1644 0 0 0 49 0 0 0 22 0 1 0 166644649 14618624 1612 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134710272 0 0 4096 0 0 0 0 17 1 0 0
/proc/2780/statm: 3569 1612 717 92 0 1913 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 14276

[startup+1.3333 s]
/proc/loadavg: 1.98 1.81 1.76 3/94 2781
/proc/meminfo: memFree=1288712/2055920 swapFree=4191880/4192956
[pid=2780] ppid=2778 vsize=14276 CPUtime=1.31
/proc/2780/stat : 2780 (solver) R 2778 2780 2360 0 -1 4194304 1644 0 0 0 131 0 0 0 25 0 1 0 166644649 14618624 1612 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134711073 0 0 4096 0 0 0 0 17 1 0 0
/proc/2780/statm: 3569 1612 717 92 0 1913 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 14276

[startup+2.97041 s]
/proc/loadavg: 1.98 1.81 1.76 3/94 2781
/proc/meminfo: memFree=1288712/2055920 swapFree=4191880/4192956
[pid=2780] ppid=2778 vsize=14276 CPUtime=2.93
/proc/2780/stat : 2780 (solver) R 2778 2780 2360 0 -1 4194304 1644 0 0 0 293 0 0 0 25 0 1 0 166644649 14618624 1612 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134722033 0 0 4096 0 0 0 0 17 1 0 0
/proc/2780/statm: 3569 1612 717 92 0 1913 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 14276

Child status: 0
Real time (s): 4.02082
CPU time (s): 3.98539
CPU user time (s): 3.9774
CPU system time (s): 0.007998
CPU usage (%): 99.119
Max. virtual memory (cumulated for all children) (KiB): 14280

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 3.9774
system time used= 0.007998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1656
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= 166

runsolver used 0.002999 s user time and 0.017997 s system time

The end

Launcher Data (download as text)

Begin job on node30 on Sun Jan  7 15:08:27 UTC 2007


IDJOB= 207614
IDBENCH= 4301
FILE ID= node30/207614-1168182507

PBS_JOBID= 3479172

Free space on /tmp= 66485 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/test01-04/test01/test01-0150-10.xml
COMMAND LINE= /tmp/evaluation/207614-1168182507/mistral/bin/solver /tmp/evaluation/207614-1168182507/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node30/watcher-207614-1168182507 -o ROOT/results/node30/solver-207614-1168182507 -C 1800 -M 900  /tmp/evaluation/207614-1168182507/mistral/bin/solver /tmp/evaluation/207614-1168182507/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  ca801d693e5f281aecf2d953ed79f03d

RANDOM SEED= 76074815

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.234
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.234
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:       1292840 kB
Buffers:         37804 kB
Cached:         201016 kB
SwapCached:        268 kB
Active:         549972 kB
Inactive:       142996 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1292840 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3276 kB
Writeback:           0 kB
Mapped:         479788 kB
Slab:            54032 kB
Committed_AS:  4120896 kB
PageTables:       3080 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= 66485 MiB



End job on node30 on Sun Jan  7 15:08:31 UTC 2007