Trace number 281466

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.377942 0.446883

DiagnosticValue
NODES0

General information on the benchmark

NameMaxCSP/randomMaxCSP/completeTight/
vcsp-15-10-100-93-11_ext.xml
MD5SUM06394180dc50cd7f907f727169a15cb3
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints33
Best CPU time to get the best result obtained on this benchmark16.1875
Satisfiable
(Un)Satisfiability was proved
Number of variables15
Number of constraints105
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension105
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.40	s UNSATISFIABLE
0.40	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/node76/watcher-281466-1169312527 -o ROOT/results/node76/solver-281466-1169312527 -C 2400 -M 900 /tmp/evaluation/281466-1169312527/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/281466-1169312527/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: 2.03 2.01 1.90 5/84 10121
/proc/meminfo: memFree=1679576/2055888 swapFree=4087964/4096564
[pid=10120] ppid=10118 vsize=5364 CPUtime=0
/proc/10120/stat : 10120 (cspfj.sh) S 10118 10120 9433 0 -1 4194304 314 124 0 0 0 0 0 0 17 0 1 0 279649824 5492736 239 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 206843734596 0 65536 4100 65538 18446744071563358023 0 0 17 1 0 0
/proc/10120/statm: 1341 239 199 169 0 51 0
[pid=10123] ppid=10120 vsize=1788 CPUtime=0
/proc/10123/stat : 10123 (java) D 10120 10120 9433 0 -1 0 193 0 0 0 0 0 0 0 18 0 1 0 279649824 1830912 157 18446744073709551615 134512640 134570532 4294956640 18446744073709551615 4294960144 0 2147483391 4096 0 18446744072100015398 0 0 17 0 0 0
/proc/10123/statm: 447 157 121 14 0 91 0

[startup+0.103763 s]
/proc/loadavg: 2.03 2.01 1.90 5/84 10121
/proc/meminfo: memFree=1679576/2055888 swapFree=4087964/4096564
[pid=10120] ppid=10118 vsize=5364 CPUtime=0
/proc/10120/stat : 10120 (cspfj.sh) S 10118 10120 9433 0 -1 4194304 314 124 0 0 0 0 0 0 17 0 1 0 279649824 5492736 239 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 206843734596 0 65536 4100 65538 18446744071563358023 0 0 17 1 0 0
/proc/10120/statm: 1341 239 199 169 0 51 0
[pid=10123] ppid=10120 vsize=865500 CPUtime=0.08
/proc/10123/stat : 10123 (java) S 10120 10120 9433 0 -1 0 2657 0 1 0 6 2 0 0 22 0 8 0 279649824 886272000 2404 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/10123/statm: 216375 2404 1421 14 0 203672 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 870864

Child status: 0
Real time (s): 0.446883
CPU time (s): 0.377942
CPU user time (s): 0.32795
CPU system time (s): 0.049992
CPU usage (%): 84.5729
Max. virtual memory (cumulated for all children) (KiB): 871944

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.32795
system time used= 0.049992
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4177
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= 468
involuntary context switches= 359

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Sat Jan 20 17:02:07 UTC 2007


IDJOB= 281466
IDBENCH= 12187
IDSOLVER= 65
FILE ID= node76/281466-1169312527

PBS_JOBID= 3610228

Free space on /tmp= 66650 MiB

SOLVER NAME= CSP4J - MaxCSP 2006-12-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/randomMaxCSP/completeTight/vcsp-15-10-100-93-11_ext.xml
COMMAND LINE= /tmp/evaluation/281466-1169312527/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/281466-1169312527/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-281466-1169312527 -o ROOT/results/node76/solver-281466-1169312527 -C 2400 -M 900  /tmp/evaluation/281466-1169312527/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/281466-1169312527/unknown.xml

META MD5SUM SOLVER= ae5901f6cce23734dab709fa25e92adb
MD5SUM BENCH=  06394180dc50cd7f907f727169a15cb3

RANDOM SEED= 89874968

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.254
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	: 6006.17
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.254
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1680056 kB
Buffers:         30268 kB
Cached:         273740 kB
SwapCached:       2128 kB
Active:          95688 kB
Inactive:       225236 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1680056 kB
SwapTotal:     4096564 kB
SwapFree:      4087964 kB
Dirty:            2624 kB
Writeback:           0 kB
Mapped:          26316 kB
Slab:            40328 kB
Committed_AS:  8256244 kB
PageTables:       1968 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66650 MiB



End job on node76 on Sat Jan 20 17:02:08 UTC 2007