Trace number 235247

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 0.240963 0.248533

General information on the benchmark

Nametaillard/os-taillard-10/
os-taillard-10-105-7.xml
MD5SUMcb5c2e7afef3a2e56bda1454eda70801
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.240963
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints900
Maximum constraint arity2
Maximum domain size625
Number of constraints which are defined in extension0
Number of constraints which are defined in intension900
Global constraints used (with number of constraints)

Solver Data (download as text)

0.20	c 
0.20	c Parsing xml file
0.20	c 	domains...............    0
0.20	c 	variables.............    0
0.20	c 	predicates............    0
0.20	c 	constraints........... 0.06
0.20	c Allocating memory
0.20	c 
0.20	c time limit = -1
0.20	c heuristic = dom/wdeg
0.20	c restart policy = No restart
0.20	c 
0.20	c Solving
0.20	c
0.23	s SATISFIABLE
0.23	v 375 418 501 0 320 117 80 430 200 559 354 115 542 428 457 206 615 262 11 73 239 409 376 0 466 340 304 232 225 164 561 69 150 512 423 409 364 324 0 225 189 512 157 0 449 576 66 501 428 340 304 542 466 614 603 369 216 157 84 0 466 387 158 430 354 221 299 195 77 66 561 539 499 470 377 320 241 80 66 0 0 421 579 566 479 324 297 201 114 66 549 427 369 364 309 299 241 164 94 0
0.23	d          SAT      1311 BTS      0.13 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/node2/watcher-235247-1168336629 -o ROOT/results/node2/solver-235247-1168336629 -C 1800 -M 900 /tmp/evaluation/235247-1168336629/mistral/bin/solver /tmp/evaluation/235247-1168336629/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.18 2.06 2.01 5/94 14713
/proc/meminfo: memFree=1436736/2055920 swapFree=4191880/4192956
[pid=14712] ppid=14710 vsize=540 CPUtime=0
/proc/14712/stat : 14712 (solver) R 14710 14712 12452 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 182058597 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 10535716 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/14712/statm: 135 26 21 92 0 18 0

[startup+0.103664 s]
/proc/loadavg: 2.18 2.06 2.01 5/94 14713
/proc/meminfo: memFree=1436736/2055920 swapFree=4191880/4192956
[pid=14712] ppid=14710 vsize=11408 CPUtime=0.08
/proc/14712/stat : 14712 (solver) R 14710 14712 12452 0 -1 4194304 1952 0 0 0 8 0 0 0 18 0 1 0 182058597 11681792 1920 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 11827729 0 0 4096 0 0 0 0 17 1 0 0
/proc/14712/statm: 2852 1920 711 92 0 1196 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 11408

Child status: 0
Real time (s): 0.248533
CPU time (s): 0.240963
CPU user time (s): 0.229965
CPU system time (s): 0.010998
CPU usage (%): 96.9541
Max. virtual memory (cumulated for all children) (KiB): 13152

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

runsolver used 0.001999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Tue Jan  9 09:57:10 UTC 2007


IDJOB= 235247
IDBENCH= 6753
FILE ID= node2/235247-1168336629

PBS_JOBID= 3503087

Free space on /tmp= 66533 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-10/os-taillard-10-105-7.xml
COMMAND LINE= /tmp/evaluation/235247-1168336629/mistral/bin/solver /tmp/evaluation/235247-1168336629/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-235247-1168336629 -o ROOT/results/node2/solver-235247-1168336629 -C 1800 -M 900  /tmp/evaluation/235247-1168336629/mistral/bin/solver /tmp/evaluation/235247-1168336629/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  cb5c2e7afef3a2e56bda1454eda70801

RANDOM SEED= 750512502

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.259
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	: 5931.00
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.259
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:       1437152 kB
Buffers:         74964 kB
Cached:         281948 kB
SwapCached:        292 kB
Active:         429396 kB
Inactive:       135668 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1437152 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3540 kB
Writeback:           0 kB
Mapped:         234220 kB
Slab:            37912 kB
Committed_AS:  5097804 kB
PageTables:       2752 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= 66533 MiB



End job on node2 on Tue Jan  9 09:57:10 UTC 2007