Trace number 278964

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
CSP4J - MaxCSP 2006-12-19? (problem) 0.472927 0.516098

DiagnosticValue
NODES0

General information on the benchmark

NameMaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-80/
kbtree-5-2-4-5-80-21_ext.xml
MD5SUM3756417940e45c981229c71a7ba8dc2b
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints117
Best CPU time to get the best result obtained on this benchmark4.07038
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)

0.49	s UNSATISFIABLE
0.49	d NODES 0

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node4/watcher-278964-1169289742 -o ROOT/results/node4/solver-278964-1169289742 -C 2400 -M 900 /tmp/evaluation/278964-1169289742/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/278964-1169289742/unknown.xml 

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: 1.84 1.91 1.89 5/87 2806
/proc/meminfo: memFree=1291808/2055920 swapFree=4182144/4192956
[pid=2805] ppid=2803 vsize=5352 CPUtime=0
/proc/2805/stat : 2805 (cspfj.sh) S 2803 2805 2480 0 -1 4194304 269 0 0 0 0 0 0 0 20 0 1 0 277369774 5480448 228 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 259913384018 0 0 4100 65536 18446744071563648864 0 0 17 1 0 0
/proc/2805/statm: 1338 228 191 169 0 49 0
[pid=2807] ppid=2805 vsize=2424 CPUtime=0
/proc/2807/stat : 2807 (dirname) R 2805 2805 2480 0 -1 4194304 58 0 0 0 0 0 0 0 22 0 1 0 277369775 2482176 33 18446744073709551615 4194304 4208292 548682069488 18446744073709551615 259910599968 0 0 4096 0 0 0 0 17 1 0 0
/proc/2807/statm: 606 33 26 3 0 7 0

[startup+0.105765 s]
/proc/loadavg: 1.84 1.91 1.89 5/87 2806
/proc/meminfo: memFree=1291808/2055920 swapFree=4182144/4192956
[pid=2805] ppid=2803 vsize=5352 CPUtime=0
/proc/2805/stat : 2805 (cspfj.sh) S 2803 2805 2480 0 -1 4194304 315 128 0 0 0 0 0 0 20 0 1 0 277369774 5480448 240 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2805/statm: 1338 240 201 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.513955 s]
/proc/loadavg: 1.84 1.91 1.89 5/87 2806
/proc/meminfo: memFree=1291808/2055920 swapFree=4182144/4192956
[pid=2805] ppid=2803 vsize=5352 CPUtime=0
/proc/2805/stat : 2805 (cspfj.sh) S 2803 2805 2480 0 -1 4194304 315 128 0 0 0 0 0 0 20 0 1 0 277369774 5480448 240 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 259913212740 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2805/statm: 1338 240 201 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.516098
CPU time (s): 0.472927
CPU user time (s): 0.438933
CPU system time (s): 0.033994
CPU usage (%): 91.6351
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.438933
system time used= 0.033994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4232
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 597
involuntary context switches= 495

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Sat Jan 20 10:42:22 UTC 2007


IDJOB= 278964
IDBENCH= 9172
IDSOLVER= 65
FILE ID= node4/278964-1169289742

PBS_JOBID= 3609579

Free space on /tmp= 66563 MiB

SOLVER NAME= CSP4J - MaxCSP 2006-12-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-80/kbtree-5-2-4-5-80-21_ext.xml
COMMAND LINE= /tmp/evaluation/278964-1169289742/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/278964-1169289742/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-278964-1169289742 -o ROOT/results/node4/solver-278964-1169289742 -C 2400 -M 900  /tmp/evaluation/278964-1169289742/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/278964-1169289742/unknown.xml

META MD5SUM SOLVER= ae5901f6cce23734dab709fa25e92adb
MD5SUM BENCH=  3756417940e45c981229c71a7ba8dc2b

RANDOM SEED= 363727711

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.223
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.223
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:       1292288 kB
Buffers:         65904 kB
Cached:         515084 kB
SwapCached:       2180 kB
Active:         254288 kB
Inactive:       426248 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1292288 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:             492 kB
Writeback:           0 kB
Mapped:         110520 kB
Slab:            67544 kB
Committed_AS:  7907812 kB
PageTables:       2532 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= 66563 MiB



End job on node4 on Sat Jan 20 10:42:23 UTC 2007