Trace number 233679

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.296954 0.306744

General information on the benchmark

Nametaillard/os-taillard-15/
os-taillard-15-105-1.xml
MD5SUMa2fec2135601327cf8139475a92a1e5b
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.296954
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size1005
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.22
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 = No restart
0.25	c 
0.25	c Solving
0.25	c
0.29	s SATISFIABLE
0.29	v 688 507 849 919 621 807 411 83 0 330 741 258 166 554 782 507 271 94 175 139 722 907 596 0 564 672 156 312 390 454 621 165 0 79 698 242 554 312 672 473 366 76 909 430 544 472 607 684 756 365 181 160 561 424 0 787 242 983 651 270 551 93 57 388 822 308 292 650 181 746 611 431 456 0 122 97 764 615 508 0 253 889 489 431 746 490 344 935 181 319 293 318 650 0 918 778 375 689 760 496 477 562 827 209 83 293 0 810 703 385 473 198 880 554 745 840 99 778 862 630 171 465 685 812 577 292 62 907 551 607 522 456 787 408 195 783 614 405 62 258 323 562 582 0 181 57 166 693 862 477 500 382 536 431 198 323 175 820 417 614 95 756 271 0 724 779 611 544 837 630 0 485 755 857 95 344 720 171 424 267 166 382 745 267 508 431 314 628 807 0 689 99 871 98 571 51 473 522 61 872 319 812 685 160 431 209 291 553 0 83 330 381 918 53 156 485 98 430 0 672 79 739 571 264 881
0.29	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/node11/watcher-233679-1168327324 -o ROOT/results/node11/solver-233679-1168327324 -C 1800 -M 900 /tmp/evaluation/233679-1168327324/mistral/bin/solver /tmp/evaluation/233679-1168327324/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.13 2.15 2.09 5/86 30334
/proc/meminfo: memFree=1633384/2055920 swapFree=4192812/4192956
[pid=30333] ppid=30331 vsize=540 CPUtime=0
/proc/30333/stat : 30333 (solver) R 30331 30333 28383 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 181127508 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7979812 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/30333/statm: 135 26 21 92 0 18 0

[startup+0.104987 s]
/proc/loadavg: 2.13 2.15 2.09 5/86 30334
/proc/meminfo: memFree=1633384/2055920 swapFree=4192812/4192956
[pid=30333] ppid=30331 vsize=8368 CPUtime=0.09
/proc/30333/stat : 30333 (solver) R 30331 30333 28383 0 -1 4194304 1164 0 0 0 9 0 0 0 18 0 1 0 181127508 8568832 1132 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8413673 0 0 4096 0 0 0 0 17 1 0 0
/proc/30333/statm: 2092 1132 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.306744
CPU time (s): 0.296954
CPU user time (s): 0.281957
CPU system time (s): 0.014997
CPU usage (%): 96.8084
Max. virtual memory (cumulated for all children) (KiB): 8764

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.281957
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= 3014
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= 16

runsolver used 0.003999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node11 on Tue Jan  9 07:22:05 UTC 2007


IDJOB= 233679
IDBENCH= 6625
FILE ID= node11/233679-1168327324

PBS_JOBID= 3502707

Free space on /tmp= 66546 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  a2fec2135601327cf8139475a92a1e5b

RANDOM SEED= 242572027

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.261
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	: 5931.00
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.261
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:       1633864 kB
Buffers:         71572 kB
Cached:         215660 kB
SwapCached:          0 kB
Active:         171360 kB
Inactive:       185904 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1633864 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3520 kB
Writeback:           0 kB
Mapped:          92404 kB
Slab:            49588 kB
Committed_AS:  5898928 kB
PageTables:       2352 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= 66546 MiB



End job on node11 on Tue Jan  9 07:22:05 UTC 2007