Trace number 278868

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
Toulbar2 2007-01-12OPTIMUM 3.23151 3.25661

General information on the benchmark

NameMaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-40/
kbtree-5-2-4-5-40-11_ext.xml
MD5SUM85249722d0019a5e205062738cf9149b
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints204
Best CPU time to get the best result obtained on this benchmark0.212967
Satisfiable
(Un)Satisfiability was proved
Number of variables62
Number of constraints211
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension211
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SOL 4 3 3 3 1 4 4 0 2 4 4 3 3 0 3 3 1 3 3 1 4 3 4 1 2 3 0 4 1 1 0 1 1 4 4 1 3 1 4 2 3 4 4 3 0 3 4 4 1 4 2 2 3 2 0 2 4 2 2 2 1 3 
OPTIMUM
c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/278868-1169289419/unknown.xml to /tmp/evaluation/278868-1169289419/unknown.wcsp

Verifier Data (download as text)

7 unsatisfied constraints, 204 satisfied constraints

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node70/watcher-278868-1169289419 -o ROOT/results/node70/solver-278868-1169289419 -C 2400 -M 900 /tmp/evaluation/278868-1169289419/solver.sh /tmp/evaluation/278868-1169289419/unknown 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 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.92 1.15 1.55 4/72 7205
/proc/meminfo: memFree=1425824/2055920 swapFree=4192812/4192956
[pid=7204] ppid=7202 vsize=8652 CPUtime=0
/proc/7204/stat : 7204 (solver.sh) R 7202 7204 7047 0 -1 4194304 334 0 0 0 0 0 0 0 17 0 1 0 76438841 8859648 278 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 4230001 0 2 4096 73728 0 0 0 17 1 0 0
/proc/7204/statm: 2163 279 207 79 0 156 0

[startup+0.105008 s]
/proc/loadavg: 0.92 1.15 1.55 4/72 7205
/proc/meminfo: memFree=1425824/2055920 swapFree=4192812/4192956
[pid=7204] ppid=7202 vsize=47556 CPUtime=0.01
/proc/7204/stat : 7204 (solver.sh) S 7202 7204 7047 0 -1 4194304 848 2275 0 0 0 0 0 1 19 0 1 0 76438841 48697344 362 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 233401674586 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/7204/statm: 11889 362 246 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

[startup+0.513044 s]
/proc/loadavg: 0.92 1.15 1.55 4/72 7205
/proc/meminfo: memFree=1425824/2055920 swapFree=4192812/4192956
[pid=7204] ppid=7202 vsize=47556 CPUtime=0.01
/proc/7204/stat : 7204 (solver.sh) S 7202 7204 7047 0 -1 4194304 848 2275 0 0 0 0 0 1 19 0 1 0 76438841 48697344 362 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 233401674586 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/7204/statm: 11889 362 246 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

[startup+1.33413 s]
/proc/loadavg: 0.92 1.15 1.55 3/76 7250
/proc/meminfo: memFree=1379768/2055920 swapFree=4192812/4192956
[pid=7204] ppid=7202 vsize=47556 CPUtime=0.01
/proc/7204/stat : 7204 (solver.sh) S 7202 7204 7047 0 -1 4194304 848 2275 0 0 0 0 0 1 19 0 1 0 76438841 48697344 362 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 233401674586 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/7204/statm: 11889 362 246 79 0 217 0
[pid=7233] ppid=7204 vsize=2696 CPUtime=0
/proc/7233/stat : 7233 (toulbar2) S 7204 7204 7047 0 -1 4194304 245 0 0 0 0 0 0 0 18 0 1 0 76438845 2760704 208 18446744073709551615 134512640 134813436 4294956592 18446744073709551615 4294960144 0 65536 4102 0 18446744071563356171 0 0 17 0 0 0
/proc/7233/statm: 674 208 186 73 0 11 0
[pid=7237] ppid=7233 vsize=1108 CPUtime=1.27
/proc/7237/stat : 7237 (narycsp) R 7233 7204 7047 0 -1 4194304 420 0 0 0 127 0 0 0 25 0 1 0 76438846 1134592 142 18446744073709551615 134512640 135380208 4294956592 18446744073709551615 134528283 0 0 4096 512 0 0 0 17 1 0 0
/proc/7237/statm: 277 142 112 211 0 46 0
Current children cumulated CPU time (s) 1.28
Current children cumulated vsize (KiB) 51360

[startup+2.97129 s]
/proc/loadavg: 0.92 1.15 1.55 3/76 7250
/proc/meminfo: memFree=1379768/2055920 swapFree=4192812/4192956
[pid=7204] ppid=7202 vsize=47556 CPUtime=0.01
/proc/7204/stat : 7204 (solver.sh) S 7202 7204 7047 0 -1 4194304 848 2275 0 0 0 0 0 1 19 0 1 0 76438841 48697344 362 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 233401674586 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/7204/statm: 11889 362 246 79 0 217 0
[pid=7233] ppid=7204 vsize=5568 CPUtime=2.9
/proc/7233/stat : 7233 (toulbar2) R 7204 7204 7047 0 -1 4194304 447 816 0 0 40 0 250 0 22 0 1 0 76438845 5701632 376 18446744073709551615 134512640 134813436 4294956592 18446744073709551615 134542193 0 0 4096 0 0 0 0 17 1 0 0
/proc/7233/statm: 1392 376 281 73 0 729 0
Current children cumulated CPU time (s) 2.91
Current children cumulated vsize (KiB) 53124

Child status: 0
Real time (s): 3.25661
CPU time (s): 3.23151
CPU user time (s): 3.19251
CPU system time (s): 0.038994
CPU usage (%): 99.2291
Max. virtual memory (cumulated for all children) (KiB): 53124

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 3.19251
system time used= 0.038994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6104
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= 94
involuntary context switches= 80

runsolver used 0.006998 s user time and 0.010998 s system time

The end

Launcher Data (download as text)

Begin job on node70 on Sat Jan 20 10:36:59 UTC 2007


IDJOB= 278868
IDBENCH= 9000
IDSOLVER= 70
FILE ID= node70/278868-1169289419

PBS_JOBID= 3609759

Free space on /tmp= 66561 MiB

SOLVER NAME= Toulbar2 2007-01-12
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-40/kbtree-5-2-4-5-40-11_ext.xml
COMMAND LINE= /tmp/evaluation/278868-1169289419/solver.sh /tmp/evaluation/278868-1169289419/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node70/convwatcher-278868-1169289419 -o ROOT/results/node70/conversion-278868-1169289419 -C 600 -M 900 /tmp/evaluation/278868-1169289419/translate /tmp/evaluation/278868-1169289419/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node70/watcher-278868-1169289419 -o ROOT/results/node70/solver-278868-1169289419 -C 2400 -M 900  /tmp/evaluation/278868-1169289419/solver.sh /tmp/evaluation/278868-1169289419/unknown

META MD5SUM SOLVER= fe7e38206dd9591eb05752f9e2c48642
MD5SUM BENCH=  85249722d0019a5e205062738cf9149b

RANDOM SEED= 785510230

TIME LIMIT= 2400 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.234
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.234
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:       1426368 kB
Buffers:         44068 kB
Cached:         493192 kB
SwapCached:        144 kB
Active:         129872 kB
Inactive:       428912 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1426368 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            4396 kB
Writeback:           0 kB
Mapped:          34632 kB
Slab:            56372 kB
Committed_AS:   803272 kB
PageTables:       1716 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= 66561 MiB



End job on node70 on Sat Jan 20 10:37:03 UTC 2007