Trace number 278985

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.119981 0.13372

General information on the benchmark

NameMaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-30/
kbtree-5-2-4-5-30-01_ext.xml
MD5SUM763e3f6bb745ab8cff53bcf0f541c9db
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best Number of satisfied constraints211
Best CPU time to get the best result obtained on this benchmark0.115981
SatisfiableYES
(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 3 1 3 0 2 4 2 3 2 1 3 1 0 0 4 0 4 0 0 3 1 3 1 3 0 4 3 2 3 3 4 2 3 2 2 4 0 2 1 2 4 3 1 2 3 1 1 0 3 4 1 1 1 2 3 2 4 3 3 1 1 3 
OPTIMUM
c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/278985-1169289950/unknown.xml to /tmp/evaluation/278985-1169289950/unknown.wcsp

Verifier Data (download as text)

0 unsatisfied constraints, 211 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/node55/watcher-278985-1169289950 -o ROOT/results/node55/solver-278985-1169289950 -C 2400 -M 900 /tmp/evaluation/278985-1169289950/solver.sh /tmp/evaluation/278985-1169289950/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: 1.85 1.94 1.90 3/80 14931
/proc/meminfo: memFree=1202568/2055920 swapFree=4192192/4192956
[pid=14930] ppid=14928 vsize=652 CPUtime=0
/proc/14930/stat : 14930 (solver.sh) R 14928 14930 14553 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 277393309 667648 25 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 248758990101 0 0 4096 0 0 0 0 17 1 0 0
/proc/14930/statm: 163 25 18 79 0 53 0

[startup+0.102997 s]
/proc/loadavg: 1.85 1.94 1.90 3/80 14931
/proc/meminfo: memFree=1202568/2055920 swapFree=4192192/4192956
[pid=14930] ppid=14928 vsize=47576 CPUtime=0.06
/proc/14930/stat : 14930 (solver.sh) S 14928 14930 14553 0 -1 4194304 878 3255 0 0 0 0 4 2 21 0 1 0 277393309 48717824 361 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 248761215834 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/14930/statm: 11894 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 47576

Child status: 0
Real time (s): 0.13372
CPU time (s): 0.119981
CPU user time (s): 0.077988
CPU system time (s): 0.041993
CPU usage (%): 89.7255
Max. virtual memory (cumulated for all children) (KiB): 47576

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.077988
system time used= 0.041993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5802
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= 96
involuntary context switches= 39

runsolver used 0.004999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node55 on Sat Jan 20 10:45:50 UTC 2007


IDJOB= 278985
IDBENCH= 9222
IDSOLVER= 70
FILE ID= node55/278985-1169289950

PBS_JOBID= 3609701

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-30/kbtree-5-2-4-5-30-01_ext.xml
COMMAND LINE= /tmp/evaluation/278985-1169289950/solver.sh /tmp/evaluation/278985-1169289950/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node55/convwatcher-278985-1169289950 -o ROOT/results/node55/conversion-278985-1169289950 -C 600 -M 900 /tmp/evaluation/278985-1169289950/translate /tmp/evaluation/278985-1169289950/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node55/watcher-278985-1169289950 -o ROOT/results/node55/solver-278985-1169289950 -C 2400 -M 900  /tmp/evaluation/278985-1169289950/solver.sh /tmp/evaluation/278985-1169289950/unknown

META MD5SUM SOLVER= fe7e38206dd9591eb05752f9e2c48642
MD5SUM BENCH=  763e3f6bb745ab8cff53bcf0f541c9db

RANDOM SEED= 430822830

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.218
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	: 5931.00
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.218
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:       1203048 kB
Buffers:         52008 kB
Cached:         668048 kB
SwapCached:        268 kB
Active:         158920 kB
Inactive:       616148 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1203048 kB
SwapTotal:     4192956 kB
SwapFree:      4192192 kB
Dirty:            2672 kB
Writeback:           0 kB
Mapped:          74008 kB
Slab:            63084 kB
Committed_AS:  6094400 kB
PageTables:       1848 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 node55 on Sat Jan 20 10:45:51 UTC 2007