Trace number 242928

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 - Combo 2006-12-19SAT 0.368943 0.391075

DiagnosticValue
NODES188

General information on the benchmark

Namedimacs/aim-50/
aim-50-1-6-sat-3_ext.xml
MD5SUM4ddf9fbba30402f0d21e02cca1191837
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 benchmark0.015997
SatisfiableYES
(Un)Satisfiability was proved
Number of variables50
Number of constraints78
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension78
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.37	v 0 0 1 0 1 0 1 0 0 1 0 0 0 0 0 1 0 0 1 0 0 1 1 1 0 0 0 0 1 1 1 0 1 1 1 0 1 1 0 1 0 1 1 1 1 0 0 0 0 0 
0.37	s SATISFIABLE
0.37	d NODES 188

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/node19/watcher-242928-1168382975 -o ROOT/results/node19/solver-242928-1168382975 -C 1800 -M 900 /tmp/evaluation/242928-1168382975/cspfj.sh -solver Combo -competition /tmp/evaluation/242928-1168382975/unknown.xml 

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.39 0.79 1.12 4/84 17979
/proc/meminfo: memFree=1774392/2055920 swapFree=4171244/4192956
[pid=17978] ppid=17971 vsize=5352 CPUtime=0
/proc/17978/stat : 17978 (cspfj.sh) S 17971 17978 17298 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 186692292 5480448 240 18446744073709551615 4194304 4889804 548682069280 18446744073709551615 255236563780 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/17978/statm: 1338 240 201 169 0 49 0
[pid=17981] ppid=17978 vsize=0 CPUtime=0
/proc/17981/stat : 17981 (cspfj.sh) R 17978 17978 17298 0 -1 4194368 17 0 0 0 0 0 0 0 20 0 1 0 186692293 0 0 18446744073709551615 0 0 0 18446744073709551615 255236566311 0 0 4096 0 0 0 0 17 0 0 0
/proc/17981/statm: 0 0 0 0 0 0 0

[startup+0.106264 s]
/proc/loadavg: 0.39 0.79 1.12 4/84 17979
/proc/meminfo: memFree=1774392/2055920 swapFree=4171244/4192956
[pid=17978] ppid=17971 vsize=5352 CPUtime=0
/proc/17978/stat : 17978 (cspfj.sh) S 17971 17978 17298 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 186692292 5480448 240 18446744073709551615 4194304 4889804 548682069280 18446744073709551615 255236563780 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/17978/statm: 1338 240 201 169 0 49 0
[pid=17981] ppid=17978 vsize=865304 CPUtime=0.09
/proc/17981/stat : 17981 (java) R 17978 17978 17298 0 -1 0 2692 0 1 0 8 1 0 0 17 0 8 0 186692293 886071296 2437 18446744073709551615 134512640 134570532 4294956496 18446744073709551615 4072917552 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/17981/statm: 216326 2437 1436 14 0 203608 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 870656

Child status: 0
Real time (s): 0.391075
CPU time (s): 0.368943
CPU user time (s): 0.32495
CPU system time (s): 0.043993
CPU usage (%): 94.3407
Max. virtual memory (cumulated for all children) (KiB): 870832

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.32495
system time used= 0.043993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4096
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= 287
involuntary context switches= 63

runsolver used 0.002999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node19 on Tue Jan  9 22:49:35 UTC 2007


IDJOB= 242928
IDBENCH= 7429
FILE ID= node19/242928-1168382975

PBS_JOBID= 3522454

Free space on /tmp= 66559 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/aim-50/aim-50-1-6-sat-3_ext.xml
COMMAND LINE= /tmp/evaluation/242928-1168382975/cspfj.sh -solver Combo -competition /tmp/evaluation/242928-1168382975/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node19/watcher-242928-1168382975 -o ROOT/results/node19/solver-242928-1168382975 -C 1800 -M 900  /tmp/evaluation/242928-1168382975/cspfj.sh -solver Combo -competition /tmp/evaluation/242928-1168382975/unknown.xml

META MD5SUM SOLVER= ae5901f6cce23734dab709fa25e92adb
MD5SUM BENCH=  4ddf9fbba30402f0d21e02cca1191837

RANDOM SEED= 121572832

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.260
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.260
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:       1771056 kB
Buffers:         44504 kB
Cached:         144000 kB
SwapCached:      10396 kB
Active:         158744 kB
Inactive:        69452 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1771056 kB
SwapTotal:     4192956 kB
SwapFree:      4171244 kB
Dirty:            2236 kB
Writeback:           0 kB
Mapped:          53692 kB
Slab:            41396 kB
Committed_AS:  6234644 kB
PageTables:       2380 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= 66559 MiB



End job on node19 on Tue Jan  9 22:49:38 UTC 2007