Trace number 235295

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.286956 0.300372

General information on the benchmark

Nametaillard/os-taillard-10/
os-taillard-10-105-5.xml
MD5SUM7b8cab6ec70ebd45de2b8c6678d6df2b
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.215966
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints900
Maximum constraint arity2
Maximum domain size565
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.29	s SATISFIABLE
0.29	v 152 270 354 529 437 142 0 230 312 59 534 458 339 270 31 9 0 126 223 413 554 89 518 192 0 290 510 40 336 432 519 479 354 131 441 343 59 245 9 0 312 519 335 429 233 290 109 250 146 32 161 343 131 72 416 532 519 450 268 24 0 342 473 406 275 270 195 162 109 17 529 472 429 324 274 192 127 93 67 0 450 356 335 289 270 203 195 32 31 0 479 437 427 356 287 274 192 162 72 0
0.29	d          SAT      2198 BTS      0.17 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/node23/watcher-235295-1168337114 -o ROOT/results/node23/solver-235295-1168337114 -C 1800 -M 900 /tmp/evaluation/235295-1168337114/mistral/bin/solver /tmp/evaluation/235295-1168337114/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


[startup+0.104027 s]
/proc/loadavg: 2.08 2.12 2.11 5/88 30131
/proc/meminfo: memFree=1023256/2055920 swapFree=4191880/4192956
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0
/proc/loadavg: 2.08 2.12 2.11 5/88 30131
/proc/meminfo: memFree=1023256/2055920 swapFree=4191880/4192956
[pid=30130] ppid=30128 vsize=12232 CPUtime=0.2
/proc/30130/stat : 30130 (solver) R 30128 30130 28803 0 -1 4194304 2144 0 0 0 19 1 0 0 19 0 1 0 182105871 12525568 2112 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134715242 0 0 4096 0 0 0 0 17 1 0 0
/proc/30130/statm: 3058 2112 716 92 0 1402 0

Child status: 0
Real time (s): 0.300372
CPU time (s): 0.286956
CPU user time (s): 0.273958
CPU system time (s): 0.012998
CPU usage (%): 95.5335
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node23 on Tue Jan  9 10:05:15 UTC 2007


IDJOB= 235295
IDBENCH= 6756
FILE ID= node23/235295-1168337114

PBS_JOBID= 3503368

Free space on /tmp= 66559 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  7b8cab6ec70ebd45de2b8c6678d6df2b

RANDOM SEED= 711114026

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.265
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.265
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:       1023672 kB
Buffers:         32080 kB
Cached:         876188 kB
SwapCached:        280 kB
Active:         250060 kB
Inactive:       728324 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1023672 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3068 kB
Writeback:           0 kB
Mapped:          89020 kB
Slab:            38672 kB
Committed_AS:  3895016 kB
PageTables:       2276 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= 66559 MiB



End job on node23 on Tue Jan  9 10:05:15 UTC 2007