Trace number 235412

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.532918 0.546948

General information on the benchmark

Nametaillard/os-taillard-10/
os-taillard-10-100-9.xml
MD5SUM9a2ef65edf8fd30850593c0a23951dfa
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.219965
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints900
Maximum constraint arity2
Maximum domain size604
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.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.06
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
0.53	s SATISFIABLE
0.53	v 595 163 153 354 223 53 0 97 212 92 287 50 148 416 483 377 0 180 163 527 377 273 472 320 0 522 199 97 124 186 354 307 102 0 176 305 585 39 377 489 417 377 211 522 312 245 220 481 85 0 549 309 464 0 422 483 229 385 133 109 183 505 0 227 46 464 385 320 92 596 377 290 543 514 505 472 221 148 53 16 517 489 422 354 307 223 153 69 16 0 501 430 373 309 220 186 176 109 102 0
0.53	d          SAT      4904 BTS      0.42 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/node3/watcher-235412-1168337718 -o ROOT/results/node3/solver-235412-1168337718 -C 1800 -M 900 /tmp/evaluation/235412-1168337718/mistral/bin/solver /tmp/evaluation/235412-1168337718/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.32 2.50 2.45 5/93 574
/proc/meminfo: memFree=1410464/2055920 swapFree=4192812/4192956
[pid=573] ppid=571 vsize=540 CPUtime=0
/proc/573/stat : 573 (solver) R 571 573 32290 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 182167523 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 10924836 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/573/statm: 135 26 21 92 0 18 0

[startup+0.10478 s]
/proc/loadavg: 2.32 2.50 2.45 5/93 574
/proc/meminfo: memFree=1410464/2055920 swapFree=4192812/4192956
[pid=573] ppid=571 vsize=11672 CPUtime=0.09
/proc/573/stat : 573 (solver) R 571 573 32290 0 -1 4194304 2006 0 0 0 9 0 0 0 18 0 1 0 182167523 11952128 1974 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 12219569 0 0 4096 0 0 0 0 17 1 0 0
/proc/573/statm: 2918 1974 711 92 0 1262 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11672

[startup+0.516834 s]
/proc/loadavg: 2.32 2.50 2.45 5/93 574
/proc/meminfo: memFree=1410464/2055920 swapFree=4192812/4192956
[pid=573] ppid=571 vsize=12740 CPUtime=0.49
/proc/573/stat : 573 (solver) R 571 573 32290 0 -1 4194304 2268 0 0 0 49 0 0 0 22 0 1 0 182167523 13045760 2236 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134795116 0 0 4096 0 0 0 0 17 1 0 0
/proc/573/statm: 3185 2236 716 92 0 1529 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 12740

Child status: 0
Real time (s): 0.546948
CPU time (s): 0.532918
CPU user time (s): 0.52592
CPU system time (s): 0.006998
CPU usage (%): 97.4349
Max. virtual memory (cumulated for all children) (KiB): 12740

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

runsolver used 0.001999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node3 on Tue Jan  9 10:15:19 UTC 2007


IDJOB= 235412
IDBENCH= 6768
FILE ID= node3/235412-1168337718

PBS_JOBID= 3503122

Free space on /tmp= 66557 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-10/os-taillard-10-100-9.xml
COMMAND LINE= /tmp/evaluation/235412-1168337718/mistral/bin/solver /tmp/evaluation/235412-1168337718/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node3/watcher-235412-1168337718 -o ROOT/results/node3/solver-235412-1168337718 -C 1800 -M 900  /tmp/evaluation/235412-1168337718/mistral/bin/solver /tmp/evaluation/235412-1168337718/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  9a2ef65edf8fd30850593c0a23951dfa

RANDOM SEED= 223986943

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.279
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.279
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:       1410880 kB
Buffers:         68224 kB
Cached:         305028 kB
SwapCached:          0 kB
Active:         418656 kB
Inactive:       161052 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1410880 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3096 kB
Writeback:           0 kB
Mapped:         235476 kB
Slab:            49880 kB
Committed_AS:  6052136 kB
PageTables:       2396 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= 66557 MiB



End job on node3 on Tue Jan  9 10:15:20 UTC 2007