Trace number 233468

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.288956 0.344344

General information on the benchmark

Nametaillard/os-taillard-15/
os-taillard-15-100-5.xml
MD5SUMd426cad722d5bc2bb5dc5b0719d02128
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.288956
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size959
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.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.2
0.23	c Allocating memory
0.23	c 
0.23	c time limit = -1
0.23	c heuristic = dom/wdeg
0.23	c restart policy = No restart
0.23	c 
0.23	c Solving
0.23	c
0.28	s SATISFIABLE
0.28	v 165 21 71 801 163 228 257 670 140 0 617 344 121 496 469 255 312 894 346 230 139 366 63 494 93 741 0 583 198 612 337 517 0 80 390 892 438 732 929 572 666 262 185 848 776 181 0 860 471 738 211 273 337 153 390 774 635 67 489 21 702 350 494 556 429 741 804 657 608 774 0 185 790 99 270 165 0 350 529 438 644 774 283 262 732 660 582 77 673 681 382 876 98 283 903 929 744 517 454 667 195 594 813 635 0 830 552 382 766 601 171 67 744 141 98 657 469 250 336 0 849 810 670 429 357 175 0 273 141 454 70 727 556 198 133 99 0 432 168 213 280 379 534 198 633 813 179 876 130 744 93 518 423 632 0 336 660 845 228 766 175 552 224 330 892 165 230 776 633 652 0 307 424 80 540 702 469 394 850 320 307 804 171 89 231 877 0 369 387 414 666 609 540 496 738 744 637 726 548 849 271 369 99 0 80 568 231 414 198 456 63 552 181 0 394 80 416 774 153 507 709 845 270 609 43
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/node18/watcher-233468-1168326464 -o ROOT/results/node18/solver-233468-1168326464 -C 1800 -M 900 /tmp/evaluation/233468-1168326464/mistral/bin/solver /tmp/evaluation/233468-1168326464/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.55 2.44 2.27 5/97 29726
/proc/meminfo: memFree=767048/2055920 swapFree=4192812/4192956
[pid=29725] ppid=29723 vsize=18540 CPUtime=0
/proc/29725/stat : 29725 (runsolver) R 29723 29725 29035 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 181041181 18984960 279 18446744073709551615 4194304 4267372 548682069056 18446744073709551615 227848809767 0 0 4096 24578 0 0 0 17 1 0 0
/proc/29725/statm: 4635 279 244 17 0 2626 0

[startup+0.103214 s]
/proc/loadavg: 2.55 2.44 2.27 5/97 29726
/proc/meminfo: memFree=767048/2055920 swapFree=4192812/4192956
[pid=29725] ppid=29723 vsize=8236 CPUtime=0.09
/proc/29725/stat : 29725 (solver) R 29723 29725 29035 0 -1 4194304 1156 0 0 0 9 0 0 0 18 0 1 0 181041181 8433664 1124 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4158526116 0 0 4096 0 0 0 0 17 0 0 0
/proc/29725/statm: 2059 1124 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.344344
CPU time (s): 0.288956
CPU user time (s): 0.275958
CPU system time (s): 0.012998
CPU usage (%): 83.9149
Max. virtual memory (cumulated for all children) (KiB): 8764

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.275958
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= 2959
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= 26

runsolver used 0.001999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node18 on Tue Jan  9 07:07:44 UTC 2007


IDJOB= 233468
IDBENCH= 6609
FILE ID= node18/233468-1168326464

PBS_JOBID= 3502995

Free space on /tmp= 66547 MiB

BENCH NAME= HOME/pub/bench/CPAI06/taillard/os-taillard-15/os-taillard-15-100-5.xml
COMMAND LINE= /tmp/evaluation/233468-1168326464/mistral/bin/solver /tmp/evaluation/233468-1168326464/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node18/watcher-233468-1168326464 -o ROOT/results/node18/solver-233468-1168326464 -C 1800 -M 900  /tmp/evaluation/233468-1168326464/mistral/bin/solver /tmp/evaluation/233468-1168326464/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  d426cad722d5bc2bb5dc5b0719d02128

RANDOM SEED= 949572649

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.231
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.231
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:        767400 kB
Buffers:         75952 kB
Cached:         361900 kB
SwapCached:          0 kB
Active:         900444 kB
Inactive:       324756 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        767400 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3392 kB
Writeback:           0 kB
Mapped:         816824 kB
Slab:            46636 kB
Committed_AS:  6258452 kB
PageTables:       3548 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= 66547 MiB



End job on node18 on Tue Jan  9 07:07:45 UTC 2007