Trace number 207901

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 16.8294 17.0194

General information on the benchmark

NametravellingSalesman/travellingSalesman-25/
tsp-25-66_ext.xml
MD5SUMfcadb94f08912b090e26967068500721
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark2.03269
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables76
Number of constraints350
Maximum constraint arity3
Maximum domain size1001
Number of constraints which are defined in extension350
Number of constraints which are defined in intension0
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 	relations............. 0.02
0.21	c 	constraints........... 0.13
0.21	c Allocating memory
0.21	c 
0.21	c time limit = -1
0.21	c heuristic = dom/wdeg
0.21	c restart policy = No restart
0.21	c 
0.21	c Solving
0.21	c
17.00	s SATISFIABLE
17.00	v 13 12 8 3 7 1 10 0 16 3 12 13 1 4 14 3 17 1 21 1 25 3 2 2 18 1 20 22 4 5 19 1 3 3 5 9 9 4 15 0 22 4 6 7 24 8 23 4 11 6 15 16 16 19 32 36 39 40 41 44 46 47 69 74 75 78 87 91 91 95 102 110 114 120 120 0
17.00	d          SAT      1967 BTS        17 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-207901-1168183765 -o ROOT/results/node29/solver-207901-1168183765 -C 1800 -M 900 /tmp/evaluation/207901-1168183765/mistral/bin/solver /tmp/evaluation/207901-1168183765/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: 0.94 0.99 1.10 5/97 16876
/proc/meminfo: memFree=1461200/2055920 swapFree=4191880/4192956
[pid=16875] ppid=16873 vsize=18540 CPUtime=0
/proc/16875/stat : 16875 (runsolver) R 16873 16875 16587 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 166770656 18984960 279 18446744073709551615 4194304 4267372 548682069056 18446744073709551615 221780700455 0 0 4096 24578 0 0 0 17 1 0 0
/proc/16875/statm: 4635 279 244 17 0 2626 0

[startup+0.103064 s]
/proc/loadavg: 0.94 0.99 1.10 5/97 16876
/proc/meminfo: memFree=1461200/2055920 swapFree=4191880/4192956
[pid=16875] ppid=16873 vsize=34972 CPUtime=0.09
/proc/16875/stat : 16875 (solver) R 16873 16875 16587 0 -1 4194304 7657 0 0 0 6 3 0 0 18 0 1 0 166770656 35811328 7621 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134789269 0 0 4096 0 0 0 0 17 0 0 0
/proc/16875/statm: 8743 7621 700 92 0 7087 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 34972

[startup+0.511078 s]
/proc/loadavg: 0.94 0.99 1.10 5/97 16876
/proc/meminfo: memFree=1461200/2055920 swapFree=4191880/4192956
[pid=16875] ppid=16873 vsize=65024 CPUtime=0.49
/proc/16875/stat : 16875 (solver) R 16873 16875 16587 0 -1 4194304 15314 0 0 0 43 6 0 0 22 0 1 0 166770656 66584576 15278 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134790374 0 0 4096 0 0 0 0 17 0 0 0
/proc/16875/statm: 16256 15278 711 92 0 14600 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 65024

[startup+1.33213 s]
/proc/loadavg: 1.02 1.01 1.11 4/97 16876
/proc/meminfo: memFree=1386960/2055920 swapFree=4191880/4192956
[pid=16875] ppid=16873 vsize=65024 CPUtime=1.31
/proc/16875/stat : 16875 (solver) R 16873 16875 16587 0 -1 4194304 15314 0 0 0 125 6 0 0 25 0 1 0 166770656 66584576 15278 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134790560 0 0 4096 0 0 0 0 17 0 0 0
/proc/16875/statm: 16256 15278 711 92 0 14600 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 65024

[startup+2.97023 s]
/proc/loadavg: 1.02 1.01 1.11 3/97 16876
/proc/meminfo: memFree=1304592/2055920 swapFree=4191880/4192956
[pid=16875] ppid=16873 vsize=65024 CPUtime=2.87
/proc/16875/stat : 16875 (solver) R 16873 16875 16587 0 -1 4194304 15314 0 0 0 281 6 0 0 25 0 1 0 166770656 66584576 15278 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134790565 0 0 4096 0 0 0 0 17 0 0 0
/proc/16875/statm: 16256 15278 711 92 0 14600 0
Current children cumulated CPU time (s) 2.87
Current children cumulated vsize (KiB) 65024

[startup+6.25043 s]
/proc/loadavg: 1.02 1.01 1.11 3/97 16876
/proc/meminfo: memFree=1183568/2055920 swapFree=4191880/4192956
[pid=16875] ppid=16873 vsize=65024 CPUtime=6.05
/proc/16875/stat : 16875 (solver) R 16873 16875 16587 0 -1 4194304 15314 0 0 0 599 6 0 0 25 0 1 0 166770656 66584576 15278 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134790355 0 0 4096 0 0 0 0 17 1 0 0
/proc/16875/statm: 16256 15278 711 92 0 14600 0
Current children cumulated CPU time (s) 6.05
Current children cumulated vsize (KiB) 65024

[startup+12.7108 s]
/proc/loadavg: 1.17 1.04 1.12 3/97 16876
/proc/meminfo: memFree=1130256/2055920 swapFree=4191880/4192956
[pid=16875] ppid=16873 vsize=65024 CPUtime=12.51
/proc/16875/stat : 16875 (solver) R 16873 16875 16587 0 -1 4194304 15314 0 0 0 1245 6 0 0 25 0 1 0 166770656 66584576 15278 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134637093 0 0 4096 0 0 0 0 17 1 0 0
/proc/16875/statm: 16256 15278 711 92 0 14600 0
Current children cumulated CPU time (s) 12.51
Current children cumulated vsize (KiB) 65024

Child status: 0
Real time (s): 17.0194
CPU time (s): 16.8294
CPU user time (s): 16.7515
CPU system time (s): 0.077988
CPU usage (%): 98.884
Max. virtual memory (cumulated for all children) (KiB): 65024

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

runsolver used 0.012998 s user time and 0.055991 s system time

The end

Launcher Data (download as text)

Begin job on node29 on Sun Jan  7 15:29:25 UTC 2007


IDJOB= 207901
IDBENCH= 4342
FILE ID= node29/207901-1168183765

PBS_JOBID= 3479205

Free space on /tmp= 66544 MiB

BENCH NAME= HOME/pub/bench/CPAI06/travellingSalesman/travellingSalesman-25/tsp-25-66_ext.xml
COMMAND LINE= /tmp/evaluation/207901-1168183765/mistral/bin/solver /tmp/evaluation/207901-1168183765/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node29/watcher-207901-1168183765 -o ROOT/results/node29/solver-207901-1168183765 -C 1800 -M 900  /tmp/evaluation/207901-1168183765/mistral/bin/solver /tmp/evaluation/207901-1168183765/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  fcadb94f08912b090e26967068500721

RANDOM SEED= 335345747

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:       1465008 kB
Buffers:         56168 kB
Cached:         393748 kB
SwapCached:        448 kB
Active:         129276 kB
Inactive:       391536 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1465008 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            5848 kB
Writeback:           0 kB
Mapped:          97752 kB
Slab:            54632 kB
Committed_AS:  4189560 kB
PageTables:       2464 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= 66544 MiB



End job on node29 on Sun Jan  7 15:29:43 UTC 2007