Trace number 234270

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 6.41802 6.47755

General information on the benchmark

Nametaillard/js-taillard-15/
js-taillard-15-105-1.xml
MD5SUM1d91210cda262774f76bb7879343f3ce
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 benchmark5.14022
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables225
Number of constraints1785
Maximum constraint arity2
Maximum domain size1326
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1785
Global constraints used (with number of constraints)

Solver Data (download as text)

0.10	c 
0.10	c Parsing xml file
0.10	c 	domains...............    0
0.10	c 	variables.............    0
0.10	c 	predicates............    0
0.10	c 	constraints........... 0.12
0.15	c Allocating memory
0.15	c 
0.15	c time limit = -1
0.15	c heuristic = dom/wdeg
0.15	c restart policy = No restart
0.15	c 
0.15	c Solving
0.15	c
6.41	s SATISFIABLE
6.41	v 13 185 345 435 557 622 716 787 812 910 959 1002 1049 1219 1240 0 68 301 339 404 519 559 603 631 775 958 1024 1035 1166 1248 0 33 216 398 489 572 715 775 863 893 1002 1024 1103 1176 1216 0 35 112 192 280 369 605 770 840 893 979 1141 1240 1298 1305 49 142 229 292 305 377 418 604 696 715 860 961 1060 1133 1228 62 124 184 277 320 379 507 595 667 725 766 827 890 966 1052 0 68 139 286 320 364 369 377 402 473 526 604 1023 1085 1231 0 128 466 558 653 725 816 890 903 1045 1064 1123 1135 1176 1193 208 301 347 398 489 596 699 787 827 945 991 1010 1093 1142 1170 11 77 112 136 150 277 280 292 402 465 529 605 699 748 812 0 35 77 139 207 280 307 359 398 439 464 473 507 1037 1078 484 507 735 770 780 891 959 979 987 1045 1107 1146 1178 1186 1228 0 28 59 100 142 208 355 439 580 727 816 861 959 961 984 0 207 318 345 404 466 489 512 526 603 667 858 955 991 1248 0 150 280 318 342 426 473 558 559 663 748 816 895 915 945
6.41	d          SAT     23856 BTS         6 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-234270-1168331495 -o ROOT/results/node11/solver-234270-1168331495 -C 1800 -M 900 /tmp/evaluation/234270-1168331495/mistral/bin/solver /tmp/evaluation/234270-1168331495/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.08 2.09 2.03 5/86 31688
/proc/meminfo: memFree=1501568/2055920 swapFree=4192812/4192956
[pid=31687] ppid=31685 vsize=540 CPUtime=0
/proc/31687/stat : 31687 (solver) R 31685 31687 31004 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 181544668 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7979812 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/31687/statm: 135 26 21 92 0 18 0

[startup+0.103662 s]
/proc/loadavg: 2.08 2.09 2.03 5/86 31688
/proc/meminfo: memFree=1501568/2055920 swapFree=4192812/4192956
[pid=31687] ppid=31685 vsize=8632 CPUtime=0.09
/proc/31687/stat : 31687 (solver) R 31685 31687 31004 0 -1 4194304 1229 0 0 0 9 0 0 0 19 0 1 0 181544668 8839168 1197 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134575819 0 0 4096 0 0 0 0 17 1 0 0
/proc/31687/statm: 2158 1197 705 92 0 502 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8632

[startup+0.512742 s]
/proc/loadavg: 2.08 2.09 2.03 5/86 31688
/proc/meminfo: memFree=1501568/2055920 swapFree=4192812/4192956
[pid=31687] ppid=31685 vsize=60440 CPUtime=0.49
/proc/31687/stat : 31687 (solver) R 31685 31687 31004 0 -1 4194304 14188 0 0 0 42 7 0 0 24 0 1 0 181544668 61890560 14156 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134793702 0 0 4096 0 0 0 0 17 1 0 0
/proc/31687/statm: 15110 14156 718 92 0 13454 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 60440

[startup+1.3339 s]
/proc/loadavg: 2.08 2.09 2.03 3/86 31688
/proc/meminfo: memFree=1447616/2055920 swapFree=4192812/4192956
[pid=31687] ppid=31685 vsize=60440 CPUtime=1.3
/proc/31687/stat : 31687 (solver) R 31685 31687 31004 0 -1 4194304 14188 0 0 0 123 7 0 0 25 0 1 0 181544668 61890560 14156 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134708374 0 0 4096 0 0 0 0 17 1 0 0
/proc/31687/statm: 15110 14156 718 92 0 13454 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 60440

[startup+2.97123 s]
/proc/loadavg: 2.08 2.09 2.03 3/86 31688
/proc/meminfo: memFree=1447616/2055920 swapFree=4192812/4192956
[pid=31687] ppid=31685 vsize=60440 CPUtime=2.93
/proc/31687/stat : 31687 (solver) R 31685 31687 31004 0 -1 4194304 14188 0 0 0 286 7 0 0 25 0 1 0 181544668 61890560 14156 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134727366 0 0 4096 0 0 0 0 17 1 0 0
/proc/31687/statm: 15110 14156 718 92 0 13454 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 60440

[startup+6.25288 s]
/proc/loadavg: 2.07 2.09 2.02 3/86 31688
/proc/meminfo: memFree=1447552/2055920 swapFree=4192812/4192956
[pid=31687] ppid=31685 vsize=60440 CPUtime=6.18
/proc/31687/stat : 31687 (solver) R 31685 31687 31004 0 -1 4194304 14189 0 0 0 611 7 0 0 25 0 1 0 181544668 61890560 14157 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134727366 0 0 4096 0 0 0 0 17 1 0 0
/proc/31687/statm: 15110 14157 718 92 0 13454 0
Current children cumulated CPU time (s) 6.18
Current children cumulated vsize (KiB) 60440

Child status: 0
Real time (s): 6.47755
CPU time (s): 6.41802
CPU user time (s): 6.32504
CPU system time (s): 0.092985
CPU usage (%): 99.081
Max. virtual memory (cumulated for all children) (KiB): 60468

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

runsolver used 0.012998 s user time and 0.018997 s system time

The end

Launcher Data (download as text)

Begin job on node11 on Tue Jan  9 08:31:36 UTC 2007


IDJOB= 234270
IDBENCH= 6674
FILE ID= node11/234270-1168331495

PBS_JOBID= 3503046

Free space on /tmp= 66550 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  1d91210cda262774f76bb7879343f3ce

RANDOM SEED= 628999665

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:       1501984 kB
Buffers:         72668 kB
Cached:         213748 kB
SwapCached:          0 kB
Active:         310916 kB
Inactive:       177588 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1501984 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3228 kB
Writeback:           0 kB
Mapped:         221896 kB
Slab:            49740 kB
Committed_AS:  6059420 kB
PageTables:       2600 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= 66550 MiB



End job on node11 on Tue Jan  9 08:31:43 UTC 2007