Trace number 238961

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-rndi 2006-12-21? (problem) 0.065989 0.07673

General information on the benchmark

NameblackHole/BH-4-13/
BlackHole-4-13-m-1_ext.xml
MD5SUMa1605d2afccf6dc05f53789b17db85a0
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 variables208
Number of constraints4218
Maximum constraint arity2
Maximum domain size52
Number of constraints which are defined in extension4218
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.07	error: index out of range
0.07	> 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/node76/watcher-238961-1168362127 -o ROOT/results/node76/solver-238961-1168362127 -C 1800 -M 900 /tmp/evaluation/238961-1168362127/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
/proc/loadavg: 2.10 2.03 1.97 4/92 3681
/proc/meminfo: memFree=1476632/2055888 swapFree=4095388/4096564
[pid=3680] ppid=3678 vsize=18544 CPUtime=0
/proc/3680/stat : 3680 (runsolver) R 3678 2794 2794 0 -1 4194368 9 0 0 0 0 0 0 0 20 0 1 0 184610108 18989056 277 18446744073709551615 4194304 4267372 548682069136 18446744073709551615 206843736721 0 0 4096 24578 0 0 0 17 0 0 0
/proc/3680/statm: 4636 277 242 17 0 2626 0
Current StackSize limit: 10240 KiB


Child status: 0
Real time (s): 0.07673
CPU time (s): 0.065989
CPU user time (s): 0.058991
CPU system time (s): 0.006998
CPU usage (%): 86.0015
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.058991
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= 1189
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= 25
involuntary context switches= 6

runsolver used 0.001999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Tue Jan  9 17:02:07 UTC 2007


IDJOB= 238961
IDBENCH= 7030
FILE ID= node76/238961-1168362127

PBS_JOBID= 3503981

Free space on /tmp= 66634 MiB

BENCH NAME= HOME/pub/bench/CPAI06/blackHole/BH-4-13/BlackHole-4-13-m-1_ext.xml
COMMAND LINE= /tmp/evaluation/238961-1168362127/solver
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node76/convwatcher-238961-1168362127 -o ROOT/results/node76/conversion-238961-1168362127 -C 600 -M 900 /tmp/evaluation/238961-1168362127/conversion /tmp/evaluation/238961-1168362127/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-238961-1168362127 -o ROOT/results/node76/solver-238961-1168362127 -C 1800 -M 900  /tmp/evaluation/238961-1168362127/solver

META MD5SUM SOLVER= b57068d1450403a75f014042200261c5
MD5SUM BENCH=  a1605d2afccf6dc05f53789b17db85a0

RANDOM SEED= 345600815

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.254
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	: 6006.17
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.254
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1478584 kB
Buffers:         24468 kB
Cached:          99044 kB
SwapCached:        384 kB
Active:         465560 kB
Inactive:        59248 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1478584 kB
SwapTotal:     4096564 kB
SwapFree:      4095388 kB
Dirty:           18088 kB
Writeback:           0 kB
Mapped:         417284 kB
Slab:            37016 kB
Committed_AS:  7361548 kB
PageTables:       2848 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66631 MiB



End job on node76 on Tue Jan  9 17:02:10 UTC 2007