Trace number 279489

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-12SAT 0.080986 0.115942

General information on the benchmark

NameMaxCSP/kbtree/kbtree-9-2-3-5/kbtree-9-2-3-5-10/
kbtree-9-2-3-5-10-01_ext.xml
MD5SUM30f17da237c56167ee991c9e749feb34
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best Number of satisfied constraints309
Best CPU time to get the best result obtained on this benchmark0.080986
SatisfiableYES
(Un)Satisfiability was proved
Number of variables58
Number of constraints309
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension309
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 0 2 4 1 2 3 0 4 3 1 4 3 1 0 0 3 3 1 4 0 3 1 0 2 4 4 4 2 3 4 4 1 2 0 0 1 2 3 1 3 2 4 1 2 3 3 3 4 1 4 2 0 4 3 2 2 2 1 
OPTIMUM
c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/279489-1169294050/unknown.xml to /tmp/evaluation/279489-1169294050/unknown.wcsp

Verifier Data (download as text)

0 unsatisfied constraints, 309 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/node65/watcher-279489-1169294050 -o ROOT/results/node65/solver-279489-1169294050 -C 2400 -M 900 /tmp/evaluation/279489-1169294050/solver.sh /tmp/evaluation/279489-1169294050/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.78 0.95 1.05 5/70 3102
/proc/meminfo: memFree=1460780/2055920 swapFree=4191892/4192956
[pid=3101] ppid=3097 vsize=5180 CPUtime=0
/proc/3101/stat : 3101 (solver.sh) R 3097 3101 2964 0 -1 4194304 82 0 0 0 0 0 0 0 18 0 1 0 76902372 5304320 55 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 4206624 0 0 4096 0 0 0 0 17 1 0 0
/proc/3101/statm: 1296 70 53 79 0 106 0

[startup+0.103897 s]
/proc/loadavg: 0.78 0.95 1.05 5/70 3102
/proc/meminfo: memFree=1460780/2055920 swapFree=4191892/4192956
[pid=3101] ppid=3097 vsize=47564 CPUtime=0.02
/proc/3101/stat : 3101 (solver.sh) S 3097 3101 2964 0 -1 4194304 877 3260 0 0 0 0 0 2 16 0 1 0 76902372 48705536 361 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 257203301210 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/3101/statm: 11891 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 47564

Child status: 0
Real time (s): 0.115942
CPU time (s): 0.080986
CPU user time (s): 0.040993
CPU system time (s): 0.039993
CPU usage (%): 69.8504
Max. virtual memory (cumulated for all children) (KiB): 47564

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.040993
system time used= 0.039993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5800
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= 92
involuntary context switches= 33

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node65 on Sat Jan 20 11:54:10 UTC 2007


IDJOB= 279489
IDBENCH= 10140
IDSOLVER= 70
FILE ID= node65/279489-1169294050

PBS_JOBID= 3609808

Free space on /tmp= 66561 MiB

SOLVER NAME= Toulbar2 2007-01-12
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/kbtree/kbtree-9-2-3-5/kbtree-9-2-3-5-10/kbtree-9-2-3-5-10-01_ext.xml
COMMAND LINE= /tmp/evaluation/279489-1169294050/solver.sh /tmp/evaluation/279489-1169294050/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node65/convwatcher-279489-1169294050 -o ROOT/results/node65/conversion-279489-1169294050 -C 600 -M 900 /tmp/evaluation/279489-1169294050/translate /tmp/evaluation/279489-1169294050/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node65/watcher-279489-1169294050 -o ROOT/results/node65/solver-279489-1169294050 -C 2400 -M 900  /tmp/evaluation/279489-1169294050/solver.sh /tmp/evaluation/279489-1169294050/unknown

META MD5SUM SOLVER= fe7e38206dd9591eb05752f9e2c48642
MD5SUM BENCH=  30f17da237c56167ee991c9e749feb34

RANDOM SEED= 758868245

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.263
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.263
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:       1461244 kB
Buffers:         48804 kB
Cached:         456108 kB
SwapCached:        396 kB
Active:         116020 kB
Inactive:       408680 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1461244 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            4600 kB
Writeback:           0 kB
Mapped:          28600 kB
Slab:            55428 kB
Committed_AS:   992216 kB
PageTables:       1788 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 node65 on Sat Jan 20 11:54:12 UTC 2007