Trace number 233602

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.379941 0.387321

General information on the benchmark

Nametaillard/os-taillard-15/
os-taillard-15-100-7.xml
MD5SUM402aa05425216409344b299698caa086
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.379941
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size916
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3150
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.23
0.25	c Allocating memory
0.25	c 
0.25	c time limit = -1
0.25	c heuristic = dom/wdeg
0.25	c restart policy = Geometric increment
0.25	c restart base = 149
0.25	c restart factor = 1.33
0.25	c 
0.25	c Solving
0.25	c
0.37	s SATISFIABLE
0.37	v 0 770 528 241 442 389 181 195 824 122 489 598 285 271 718 99 466 195 333 397 828 484 0 571 291 168 773 642 639 681 883 569 655 135 732 253 341 481 59 198 0 861 405 882 806 396 226 287 352 484 712 369 869 585 610 823 544 63 0 150 684 340 0 85 352 555 453 257 428 133 869 806 654 178 153 396 56 226 648 0 797 85 96 598 320 456 731 160 99 568 760 639 333 497 60 578 843 369 778 172 447 239 155 0 177 774 298 198 291 96 51 484 837 0 613 675 463 824 259 382 287 313 0 489 234 862 801 750 565 99 168 392 684 456 120 75 228 298 78 153 453 27 578 567 745 355 843 181 655 322 234 436 92 162 571 607 0 680 484 801 649 514 203 731 341 861 0 650 489 797 228 569 198 195 320 405 177 735 544 95 172 141 27 0 466 403 291 518 231 857 96 53 675 352 735 247 567 607 298 253 497 0 555 436 654 773 392 356 162 58 397 160 169 585 424 836 541 0 63 203 732 298 667 492 92
0.37	d          SAT       483 BTS      0.09 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/node29/watcher-233602-1168327049 -o ROOT/results/node29/solver-233602-1168327049 -C 1800 -M 900 /tmp/evaluation/233602-1168327049/tramontane/bin/solver /tmp/evaluation/233602-1168327049/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.13 2.40 2.17 5/87 2309
/proc/meminfo: memFree=1420248/2055920 swapFree=4191880/4192956
[pid=2308] ppid=2306 vsize=540 CPUtime=0
/proc/2308/stat : 2308 (solver) R 2306 2308 2052 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 181099131 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4129572 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/2308/statm: 135 26 21 92 0 18 0

[startup+0.103573 s]
/proc/loadavg: 2.13 2.40 2.17 5/87 2309
/proc/meminfo: memFree=1420248/2055920 swapFree=4191880/4192956
[pid=2308] ppid=2306 vsize=8236 CPUtime=0.09
/proc/2308/stat : 2308 (solver) R 2306 2308 2052 0 -1 4194304 1142 0 0 0 9 0 0 0 18 0 1 0 181099131 8433664 1110 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134575745 0 0 4096 0 0 0 0 17 1 0 0
/proc/2308/statm: 2059 1110 705 92 0 403 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8236

Child status: 0
Real time (s): 0.387321
CPU time (s): 0.379941
CPU user time (s): 0.362944
CPU system time (s): 0.016997
CPU usage (%): 98.0946
Max. virtual memory (cumulated for all children) (KiB): 15128

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

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node29 on Tue Jan  9 07:17:30 UTC 2007


IDJOB= 233602
IDBENCH= 6619
FILE ID= node29/233602-1168327049

PBS_JOBID= 3503016

Free space on /tmp= 66541 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  402aa05425216409344b299698caa086

RANDOM SEED= 122397882

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.241
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.241
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:       1420728 kB
Buffers:         14404 kB
Cached:         475064 kB
SwapCached:        268 kB
Active:         170600 kB
Inactive:       410300 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1420728 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3880 kB
Writeback:           0 kB
Mapped:         110224 kB
Slab:            38768 kB
Committed_AS:  4032768 kB
PageTables:       2452 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= 66541 MiB



End job on node29 on Tue Jan  9 07:17:31 UTC 2007