Trace number 252721

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
VALCSP 3.0SAT 0.002998 0.00941598

DiagnosticValue
CHECKS2349
NODES40

General information on the benchmark

Namecoloring/
geom-40-6-ext.xml
MD5SUM583d710afa4b37469fcd77467acf26f1
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.002998
SatisfiableYES
(Un)Satisfiability was proved
Number of variables40
Number of constraints78
Maximum constraint arity2
Maximum domain size6
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.00	s SATISFIABLE
0.00	v 0 4 3 0 2 1 2 3 1 2 0 3 2 1 0 0 1 4 0 3 1 1 1 2 0 0 5 3 0 2 3 3 1 4 2 1 1 0 2 0 
0.00	d CHECKS 2349
0.00	d NODES 40
0.00

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/node10/watcher-252721-1168703624 -o ROOT/results/node10/solver-252721-1168703624 -C 1800 -M 900 /tmp/evaluation/252721-1168703624/VALCSP /tmp/evaluation/252721-1168703624/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: 1.10 1.62 1.70 5/86 14233
/proc/meminfo: memFree=951064/2055920 swapFree=4178232/4192956
[pid=14232] ppid=14230 vsize=0 CPUtime=0
/proc/14232/stat : 14232 (VALCSP) R 14230 14232 14086 0 -1 4194308 159 0 0 0 0 0 0 0 21 0 1 0 218759785 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 0 0 0 0 17 0 0 0
/proc/14232/statm: 0 0 0 0 0 0 0

Child status: 0
Real time (s): 0.00941598
CPU time (s): 0.002998
CPU user time (s): 0.001999
CPU system time (s): 0.000999
CPU usage (%): 31.8395
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Sat Jan 13 15:53:53 UTC 2007


IDJOB= 252721
IDBENCH= 12964
IDSOLVER= 79
FILE ID= node10/252721-1168703624

PBS_JOBID= 3547056

Free space on /tmp= 66562 MiB

SOLVER NAME= VALCSP 3.0
BENCH NAME= HOME/pub/bench/CPAI06/coloring/geom-40-6-ext.xml
COMMAND LINE= /tmp/evaluation/252721-1168703624/VALCSP /tmp/evaluation/252721-1168703624/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-252721-1168703624 -o ROOT/results/node10/solver-252721-1168703624 -C 1800 -M 900  /tmp/evaluation/252721-1168703624/VALCSP /tmp/evaluation/252721-1168703624/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  583d710afa4b37469fcd77467acf26f1

RANDOM SEED= 391109912

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.232
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.232
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:        944440 kB
Buffers:         77860 kB
Cached:         890688 kB
SwapCached:       2900 kB
Active:         345588 kB
Inactive:       686204 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        944440 kB
SwapTotal:     4192956 kB
SwapFree:      4178232 kB
Dirty:              84 kB
Writeback:           0 kB
Mapped:          72808 kB
Slab:            64440 kB
Committed_AS:  6128724 kB
PageTables:       2408 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= 66562 MiB



End job on node10 on Sat Jan 13 15:54:13 UTC 2007