Trace number 253144

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
Diarmuid-wtdi 2006-12-21UNSAT 0.382941 0.382171

DiagnosticValue
CHECKS95539
NODES1043

General information on the benchmark

Namecoloring/
geom-30a-5-ext.xml
MD5SUM162106a1ffe1b0fbdc628fd119f2c399
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.004998
SatisfiableNO
(Un)Satisfiability was proved
Number of variables30
Number of constraints81
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension81
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.38	c Nodes on final run 205
0.38	s UNSATISFIABLE
0.38	d NODES 1043
0.38	d CHECKS 95539
0.38	c Solved on restart 7
c 
c 
c 
c conversion script
c 
c

Verifier Data (download as text)

No possible verification on an UNSAT instance

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-253144-1168383636 -o ROOT/results/node10/solver-253144-1168383636 -C 1800 -M 900 /tmp/evaluation/253144-1168383636/solver 

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.81 1.03 1.06 4/81 20274
/proc/meminfo: memFree=1874640/2055920 swapFree=4178216/4192956
[pid=20273] ppid=20271 vsize=5352 CPUtime=0
/proc/20273/stat : 20273 (solver) R 20271 20273 19990 0 -1 4194304 283 174 0 0 0 0 0 0 18 0 1 0 186758785 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 214919867039 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/20273/statm: 1338 229 192 169 0 49 0
[pid=20276] ppid=20273 vsize=5352 CPUtime=0
/proc/20276/stat : 20276 (solver) R 20273 20273 19990 0 -1 4194368 13 0 0 0 0 0 0 0 18 0 1 0 186758785 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 4412747 0 0 4100 65536 0 0 0 17 1 0 0
/proc/20276/statm: 1338 229 192 169 0 49 0

[startup+0.10291 s]
/proc/loadavg: 0.81 1.03 1.06 4/81 20274
/proc/meminfo: memFree=1874640/2055920 swapFree=4178216/4192956
[pid=20273] ppid=20271 vsize=5352 CPUtime=0
/proc/20273/stat : 20273 (solver) S 20271 20273 19990 0 -1 4194304 313 174 0 0 0 0 0 0 18 0 1 0 186758785 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 214919865156 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/20273/statm: 1338 229 192 169 0 49 0
[pid=20276] ppid=20273 vsize=3816 CPUtime=0.09
/proc/20276/stat : 20276 (xlisp) R 20273 20273 19990 0 -1 4194304 455 0 0 0 9 0 0 0 20 0 1 0 186758785 3907584 414 18446744073709551615 134512640 135322396 4294956848 18446744073709551615 4294960144 0 0 4096 130 0 0 0 17 1 0 0
/proc/20276/statm: 954 414 243 197 0 194 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9168

Child status: 0
Real time (s): 0.382171
CPU time (s): 0.382941
CPU user time (s): 0.376942
CPU system time (s): 0.005999
CPU usage (%): 100.201
Max. virtual memory (cumulated for all children) (KiB): 9168

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

runsolver used 0.005999 s user time and 0.001999 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan  9 23:00:36 UTC 2007


IDJOB= 253144
IDBENCH= 12981
FILE ID= node10/253144-1168383636

PBS_JOBID= 3522524

Free space on /tmp= 66563 MiB

BENCH NAME= HOME/pub/bench/CPAI06/coloring/geom-30a-5-ext.xml
COMMAND LINE= /tmp/evaluation/253144-1168383636/solver
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node10/convwatcher-253144-1168383636 -o ROOT/results/node10/conversion-253144-1168383636 -C 600 -M 900 /tmp/evaluation/253144-1168383636/conversion /tmp/evaluation/253144-1168383636/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-253144-1168383636 -o ROOT/results/node10/solver-253144-1168383636 -C 1800 -M 900  /tmp/evaluation/253144-1168383636/solver

META MD5SUM SOLVER= d524ecf1110edbc743abd2f199c280bf
MD5SUM BENCH=  162106a1ffe1b0fbdc628fd119f2c399

RANDOM SEED= 871124935

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:       1875120 kB
Buffers:         23140 kB
Cached:          71488 kB
SwapCached:       1864 kB
Active:          87440 kB
Inactive:        41064 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1875120 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:            1256 kB
Writeback:           0 kB
Mapped:          43644 kB
Slab:            37512 kB
Committed_AS:  5424540 kB
PageTables:       2064 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= 66563 MiB



End job on node10 on Tue Jan  9 23:00:37 UTC 2007