Trace number 287255

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 20.4419 20.451

General information on the benchmark

Namelard/
lard-83-83.xml
MD5SUMee46835fd00d02a10e04381bf08a6075
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark17.1344
SatisfiableYES
(Un)Satisfiability was proved
Number of variables83
Number of constraints3403
Maximum constraint arity2
Maximum domain size84
Number of constraints which are defined in extension3403
Number of constraints which are defined in intension0
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.01	c 	relations............. 18.8
18.76	c 	constraints........... 1.25
20.01	c Allocating memory
20.24	c 
20.24	c time limit = -1
20.24	c heuristic = dom/wdeg
20.24	c restart policy = No restart
20.24	c 
20.24	c Solving
20.24	c
20.35	s SATISFIABLE
20.35	v 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
20.35	d          SAT         0 BTS      0.07 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-287255-1170112750 -o ROOT/results/node30/solver-287255-1170112750 -C 1800 -M 900 /tmp/evaluation/287255-1170112750/mistral/bin/solver /tmp/evaluation/287255-1170112750/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.01 1.53 2.13 2/78 26123
/proc/meminfo: memFree=1509376/2055920 swapFree=4192812/4192956
[pid=26122] ppid=26120 vsize=6920 CPUtime=0
/proc/26122/stat : 26122 (solver) R 26120 26122 24985 0 -1 4194304 400 0 0 0 0 0 0 0 18 0 1 0 5039210 7086080 380 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7020632 0 0 4096 0 0 0 0 17 1 0 0
/proc/26122/statm: 1730 380 356 92 0 30 0

[startup+0.102679 s]
/proc/loadavg: 1.01 1.53 2.13 2/78 26123
/proc/meminfo: memFree=1509376/2055920 swapFree=4192812/4192956
[pid=26122] ppid=26120 vsize=8660 CPUtime=0.09
/proc/26122/stat : 26122 (solver) R 26120 26122 24985 0 -1 4194304 1199 0 0 0 9 0 0 0 18 0 1 0 5039210 8867840 1167 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4156466793 0 0 4096 0 0 0 0 17 1 0 0
/proc/26122/statm: 2165 1167 702 92 0 477 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8660

[startup+0.510736 s]
/proc/loadavg: 1.01 1.53 2.13 2/78 26123
/proc/meminfo: memFree=1509376/2055920 swapFree=4192812/4192956
[pid=26122] ppid=26120 vsize=13644 CPUtime=0.5
/proc/26122/stat : 26122 (solver) R 26120 26122 24985 0 -1 4194304 2463 0 0 0 49 1 0 0 22 0 1 0 5039210 13971456 2431 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/26122/statm: 3411 2431 702 92 0 1723 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 13644

[startup+1.33085 s]
/proc/loadavg: 1.01 1.52 2.12 2/78 26123
/proc/meminfo: memFree=1494912/2055920 swapFree=4192812/4192956
[pid=26122] ppid=26120 vsize=23748 CPUtime=1.32
/proc/26122/stat : 26122 (solver) R 26120 26122 24985 0 -1 4194304 4971 0 0 0 130 2 0 0 25 0 1 0 5039210 24317952 4939 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4156466772 0 0 4096 0 0 0 0 17 1 0 0
/proc/26122/statm: 5937 4939 702 92 0 4249 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 23748

[startup+2.96809 s]
/proc/loadavg: 1.01 1.52 2.12 2/78 26123
/proc/meminfo: memFree=1478528/2055920 swapFree=4192812/4192956
[pid=26122] ppid=26120 vsize=43684 CPUtime=2.95
/proc/26122/stat : 26122 (solver) R 26120 26122 24985 0 -1 4194304 9973 0 0 0 290 5 0 0 25 0 1 0 5039210 44732416 9941 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4159420380 0 0 4096 0 0 0 0 17 1 0 0
/proc/26122/statm: 10921 9941 702 92 0 9233 0
Current children cumulated CPU time (s) 2.95
Current children cumulated vsize (KiB) 43684

[startup+6.24755 s]
/proc/loadavg: 1.01 1.51 2.12 2/78 26123
/proc/meminfo: memFree=1440768/2055920 swapFree=4192812/4192956
[pid=26122] ppid=26120 vsize=83832 CPUtime=6.23
/proc/26122/stat : 26122 (solver) R 26120 26122 24985 0 -1 4194304 20013 0 0 0 610 13 0 0 25 0 1 0 5039210 85843968 19981 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8084062 0 0 4096 0 0 0 0 17 1 0 0
/proc/26122/statm: 20958 19981 702 92 0 19270 0
Current children cumulated CPU time (s) 6.23
Current children cumulated vsize (KiB) 83832

[startup+12.7005 s]
/proc/loadavg: 1.01 1.50 2.11 2/78 26123
/proc/meminfo: memFree=1357840/2055920 swapFree=4192812/4192956
[pid=26122] ppid=26120 vsize=162908 CPUtime=12.69
/proc/26122/stat : 26122 (solver) R 26120 26122 24985 0 -1 4194304 39786 0 0 0 1247 22 0 0 25 0 1 0 5039210 166817792 39754 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7452283 0 0 4096 0 0 0 0 17 1 0 0
/proc/26122/statm: 40727 39754 702 92 0 39039 0
Current children cumulated CPU time (s) 12.69
Current children cumulated vsize (KiB) 162908

Child status: 0
Real time (s): 20.451
CPU time (s): 20.4419
CPU user time (s): 20.0799
CPU system time (s): 0.361944
CPU usage (%): 99.9553
Max. virtual memory (cumulated for all children) (KiB): 240556

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 20.0799
system time used= 0.361944
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 59205
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= 17
involuntary context switches= 437

runsolver used 0.020996 s user time and 0.06299 s system time

The end

Launcher Data (download as text)

Begin job on node30 on Mon Jan 29 23:19:12 UTC 2007


IDJOB= 287255
IDBENCH= 19810
IDSOLVER= 84
FILE ID= node30/287255-1170112750

PBS_JOBID= 3689961

Free space on /tmp= 66498 MiB

SOLVER NAME= Mistral 2006-12-04
BENCH NAME= HOME/pub/bench/CPAI06/lard/lard-83-83.xml
COMMAND LINE= /tmp/evaluation/287255-1170112750/mistral/bin/solver /tmp/evaluation/287255-1170112750/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node30/watcher-287255-1170112750 -o ROOT/results/node30/solver-287255-1170112750 -C 1800 -M 900  /tmp/evaluation/287255-1170112750/mistral/bin/solver /tmp/evaluation/287255-1170112750/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  ee46835fd00d02a10e04381bf08a6075

RANDOM SEED= 454017419

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.270
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.270
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:       1509856 kB
Buffers:         15456 kB
Cached:         365208 kB
SwapCached:          0 kB
Active:         309520 kB
Inactive:       185476 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1509856 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           68272 kB
Writeback:           0 kB
Mapped:         133240 kB
Slab:            36596 kB
Committed_AS:   594636 kB
PageTables:       1792 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= 66498 MiB



End job on node30 on Mon Jan 29 23:19:32 UTC 2007