Trace number 235264

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
Tramontane 2006-12-04SAT 0.428934 0.43492

General information on the benchmark

Nametaillard/os-taillard-10/
os-taillard-10-100-1.xml
MD5SUM74cf29d3ab94d83fc52e373a6d01ad7d
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.428934
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints900
Maximum constraint arity2
Maximum domain size587
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 = Geometric increment
0.20	c restart base = 666
0.20	c restart factor = 1.33
0.20	c 
0.20	c Solving
0.20	c
0.42	s SATISFIABLE
0.42	v 364 217 0 199 163 511 314 133 459 36 117 395 530 307 430 6 512 217 0 9 510 216 307 124 457 387 316 167 32 73 236 499 74 167 267 364 0 558 342 556 363 547 267 562 152 454 200 56 87 0 298 342 0 459 163 87 36 155 239 409 239 71 200 441 530 36 421 149 6 323 477 409 0 327 236 149 33 62 563 577 563 499 9 147 314 228 88 62 416 46 88 55 74 459 298 199 133 323 0 396
0.42	d          SAT      3176 BTS      0.31 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/node41/watcher-235264-1168336783 -o ROOT/results/node41/solver-235264-1168336783 -C 1800 -M 900 /tmp/evaluation/235264-1168336783/tramontane/bin/solver /tmp/evaluation/235264-1168336783/unknown.xml -res geom -f 3 -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.36 2.11 1.92 5/84 19430
/proc/meminfo: memFree=749944/2055920 swapFree=4191892/4192956
[pid=19429] ppid=19427 vsize=540 CPUtime=0
/proc/19429/stat : 19429 (solver) R 19427 19429 19062 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 182077577 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 1962788 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/19429/statm: 135 26 21 92 0 18 0

[startup+0.103235 s]
/proc/loadavg: 2.36 2.11 1.92 5/84 19430
/proc/meminfo: memFree=749944/2055920 swapFree=4191892/4192956
[pid=19429] ppid=19427 vsize=11140 CPUtime=0.09
/proc/19429/stat : 19429 (solver) R 19427 19429 19062 0 -1 4194304 1882 0 0 0 9 0 0 0 18 0 1 0 182077577 11407360 1850 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 3257509 0 0 4096 0 0 0 0 17 1 0 0
/proc/19429/statm: 2785 1850 713 92 0 1129 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11140

Child status: 0
Real time (s): 0.43492
CPU time (s): 0.428934
CPU user time (s): 0.418936
CPU system time (s): 0.009998
CPU usage (%): 98.6236
Max. virtual memory (cumulated for all children) (KiB): 12492

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.418936
system time used= 0.009998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2237
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.000999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node41 on Tue Jan  9 09:59:43 UTC 2007


IDJOB= 235264
IDBENCH= 6754
FILE ID= node41/235264-1168336783

PBS_JOBID= 3503371

Free space on /tmp= 66557 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-10/os-taillard-10-100-1.xml
COMMAND LINE= /tmp/evaluation/235264-1168336783/tramontane/bin/solver /tmp/evaluation/235264-1168336783/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node41/watcher-235264-1168336783 -o ROOT/results/node41/solver-235264-1168336783 -C 1800 -M 900  /tmp/evaluation/235264-1168336783/tramontane/bin/solver /tmp/evaluation/235264-1168336783/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  74cf29d3ab94d83fc52e373a6d01ad7d

RANDOM SEED= 798930795

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:        750424 kB
Buffers:         70580 kB
Cached:         422908 kB
SwapCached:        396 kB
Active:         930788 kB
Inactive:       313788 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        750424 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            3076 kB
Writeback:           0 kB
Mapped:         770468 kB
Slab:            44732 kB
Committed_AS:  4621548 kB
PageTables:       3352 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 node41 on Tue Jan  9 09:59:44 UTC 2007