Trace number 238656

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-21? (problem) 0.046991 0.055014

General information on the benchmark

NameblackHole/BH-4-7/
BlackHole-4-7-h-5_ext.xml
MD5SUM70077fec9d8f4e4d0f96094f9edfe278
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Satisfiable
(Un)Satisfiability was proved
Number of variables112
Number of constraints1262
Maximum constraint arity2
Maximum domain size28
Number of constraints which are defined in extension1262
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.05	error: index out of range
0.05	> c 
c 
c 
c conversion script
c 
c

Verifier Data (download as text)

ERROR: Unexpected answer ! (SAT/UNSAT expected)
Got answer:

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node4/watcher-238656-1168357857 -o ROOT/results/node4/solver-238656-1168357857 -C 1800 -M 900 /tmp/evaluation/238656-1168357857/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: 1.92 1.99 1.99 3/88 10541
/proc/meminfo: memFree=1691408/2055920 swapFree=4182144/4192956
[pid=10540] ppid=10538 vsize=5352 CPUtime=0
/proc/10540/stat : 10540 (solver) R 10538 10540 5137 0 -1 4194304 219 0 0 0 0 0 0 0 20 0 1 0 184181270 5480448 186 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 259913030608 0 0 4100 0 0 0 0 17 1 0 0
/proc/10540/statm: 1338 186 153 169 0 49 0

Child status: 0
Real time (s): 0.055014
CPU time (s): 0.046991
CPU user time (s): 0.039993
CPU system time (s): 0.006998
CPU usage (%): 85.4164
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Tue Jan  9 15:50:57 UTC 2007


IDJOB= 238656
IDBENCH= 7014
FILE ID= node4/238656-1168357857

PBS_JOBID= 3503684

Free space on /tmp= 66504 MiB

BENCH NAME= HOME/pub/bench/CPAI06/blackHole/BH-4-7/BlackHole-4-7-h-5_ext.xml
COMMAND LINE= /tmp/evaluation/238656-1168357857/solver
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node4/convwatcher-238656-1168357857 -o ROOT/results/node4/conversion-238656-1168357857 -C 600 -M 900 /tmp/evaluation/238656-1168357857/conversion /tmp/evaluation/238656-1168357857/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-238656-1168357857 -o ROOT/results/node4/solver-238656-1168357857 -C 1800 -M 900  /tmp/evaluation/238656-1168357857/solver

META MD5SUM SOLVER= d524ecf1110edbc743abd2f199c280bf
MD5SUM BENCH=  70077fec9d8f4e4d0f96094f9edfe278

RANDOM SEED= 493982140

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.223
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.223
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:       1691888 kB
Buffers:         36600 kB
Cached:         140876 kB
SwapCached:       2520 kB
Active:         256700 kB
Inactive:        52272 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1691888 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:            1120 kB
Writeback:           0 kB
Mapped:         141844 kB
Slab:            39532 kB
Committed_AS:  5648264 kB
PageTables:       2592 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= 66503 MiB



End job on node4 on Tue Jan  9 15:50:57 UTC 2007