Trace number 233361

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.298953 0.301628

General information on the benchmark

Nametaillard/os-taillard-15/
os-taillard-15-105-5.xml
MD5SUM806de2aa80fa49e02b821d097063d54f
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.288955
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size1007
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.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.02	c 	variables.............    0
0.02	c 	predicates............    0
0.02	c 	constraints........... 0.22
0.24	c Allocating memory
0.24	c 
0.24	c time limit = -1
0.24	c heuristic = dom/wdeg
0.24	c restart policy = Geometric increment
0.24	c restart base = 149
0.24	c restart factor = 1.33
0.24	c 
0.24	c Solving
0.24	c
0.28	s SATISFIABLE
0.28	v 356 448 439 801 152 419 79 155 549 182 572 0 211 237 508 195 333 718 89 911 66 475 94 595 649 741 0 446 367 283 441 572 75 356 764 806 503 892 155 262 698 0 185 848 627 252 281 870 219 88 382 273 510 183 904 565 0 96 744 74 702 350 494 556 429 741 804 657 608 774 0 185 790 99 270 237 160 350 681 524 656 734 806 638 98 329 442 0 673 615 382 876 98 283 903 929 744 517 454 667 195 594 813 635 0 915 333 382 898 684 171 566 544 608 641 469 250 74 0 739 442 678 813 524 583 69 723 80 920 273 0 359 556 198 63 508 0 370 182 234 442 315 764 158 592 625 348 99 672 193 341 36 678 855 75 635 168 739 503 262 0 438 252 63 892 723 80 583 435 391 0 540 346 261 168 788 469 920 860 649 308 609 855 89 243 372 0 790 682 446 171 832 540 709 734 450 283 735 793 813 198 542 99 0 80 911 565 592 82 372 69 0 99 804 876 718 164 454 79 673 528 391 270 609 33
0.28	d          SAT         0 BTS         0 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/node13/watcher-233361-1168325591 -o ROOT/results/node13/solver-233361-1168325591 -C 1800 -M 900 /tmp/evaluation/233361-1168325591/tramontane/bin/solver /tmp/evaluation/233361-1168325591/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.42 2.40 2.21 5/87 12821
/proc/meminfo: memFree=1113664/2055920 swapFree=4192812/4192956
[pid=12820] ppid=12818 vsize=6792 CPUtime=0
/proc/12820/stat : 12820 (solver) R 12818 12820 12401 0 -1 4194304 424 0 0 0 0 0 0 0 18 0 1 0 180954335 6955008 403 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 11848568 0 0 4096 0 0 0 0 17 1 0 0
/proc/12820/statm: 1698 403 364 92 0 30 0

[startup+0.102692 s]
/proc/loadavg: 2.42 2.40 2.21 5/87 12821
/proc/meminfo: memFree=1113664/2055920 swapFree=4192812/4192956
[pid=12820] ppid=12818 vsize=8368 CPUtime=0.09
/proc/12820/stat : 12820 (solver) R 12818 12820 12401 0 -1 4194304 1168 0 0 0 9 0 0 0 18 0 1 0 180954335 8568832 1136 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 12314235 0 0 4096 0 0 0 0 17 1 0 0
/proc/12820/statm: 2092 1136 705 92 0 436 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8368

Child status: 0
Real time (s): 0.301628
CPU time (s): 0.298953
CPU user time (s): 0.283956
CPU system time (s): 0.014997
CPU usage (%): 99.1132
Max. virtual memory (cumulated for all children) (KiB): 8764

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

runsolver used 0.004999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node13 on Tue Jan  9 06:53:12 UTC 2007


IDJOB= 233361
IDBENCH= 6600
FILE ID= node13/233361-1168325591

PBS_JOBID= 3502988

Free space on /tmp= 66527 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  806de2aa80fa49e02b821d097063d54f

RANDOM SEED= 289554808

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.247
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.247
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:       1114144 kB
Buffers:        102304 kB
Cached:         605916 kB
SwapCached:          0 kB
Active:         507704 kB
Inactive:       352508 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1114144 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3488 kB
Writeback:           0 kB
Mapped:         172144 kB
Slab:            66000 kB
Committed_AS:  5078588 kB
PageTables:       2588 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= 66527 MiB



End job on node13 on Tue Jan  9 06:53:14 UTC 2007