Trace number 287048

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 2007-01-22? (problem) 0.106983 0.108199

General information on the benchmark

NameblackHole/BH-4-7/
BlackHole-4-7-e-5_ext.xml
MD5SUM4c58eb69aa8058c4fc80a5c46de30e6e
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.10	error: index out of range
0.10	> 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/node9/watcher-287048-1169494094 -o ROOT/results/node9/solver-287048-1169494094 -C 1800 -M 900 /tmp/evaluation/287048-1169494094/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.47 1.77 1.89 5/88 486
/proc/meminfo: memFree=1466368/2055920 swapFree=4191880/4192956
[pid=485] ppid=483 vsize=5352 CPUtime=0
/proc/485/stat : 485 (solver) R 483 485 32277 0 -1 4194304 283 174 0 0 0 0 0 0 18 0 1 0 297804970 5480448 229 18446744073709551615 4194304 4889804 548682069408 18446744073709551615 215418989215 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/485/statm: 1338 229 192 169 0 49 0
[pid=488] ppid=485 vsize=5352 CPUtime=0
/proc/488/stat : 488 (solver) R 485 485 32277 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 297804971 5480448 229 18446744073709551615 4194304 4889804 548682069408 18446744073709551615 4345746 0 0 4100 65536 0 0 0 17 1 0 0
/proc/488/statm: 1338 229 192 169 0 49 0

[startup+0.103377 s]
/proc/loadavg: 1.47 1.77 1.89 5/88 486
/proc/meminfo: memFree=1466368/2055920 swapFree=4191880/4192956
[pid=485] ppid=483 vsize=5352 CPUtime=0
/proc/485/stat : 485 (solver) S 483 485 32277 0 -1 4194304 314 174 0 0 0 0 0 0 18 0 1 0 297804970 5480448 229 18446744073709551615 4194304 4889804 548682069408 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/485/statm: 1338 229 192 169 0 49 0
[pid=488] ppid=485 vsize=5816 CPUtime=0.09
/proc/488/stat : 488 (xlisp) R 485 485 32277 0 -1 4194304 968 0 0 0 9 0 0 0 18 0 1 0 297804971 5955584 928 18446744073709551615 134512640 135322396 4294956864 18446744073709551615 134987072 0 0 4096 130 0 0 0 17 0 0 0
/proc/488/statm: 1454 928 241 197 0 694 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11168

Child status: 0
Real time (s): 0.108199
CPU time (s): 0.106983
CPU user time (s): 0.096985
CPU system time (s): 0.009998
CPU usage (%): 98.8762
Max. virtual memory (cumulated for all children) (KiB): 11168

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

runsolver used 0.002999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Mon Jan 22 19:28:16 UTC 2007


IDJOB= 287048
IDBENCH= 7021
IDSOLVER= 95
FILE ID= node9/287048-1169494094

PBS_JOBID= 3619573

Free space on /tmp= 66563 MiB

SOLVER NAME= Diarmuid-rndi 2007-01-22
BENCH NAME= HOME/pub/bench/CPAI06/blackHole/BH-4-7/BlackHole-4-7-e-5_ext.xml
COMMAND LINE= /tmp/evaluation/287048-1169494094/solver
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node9/convwatcher-287048-1169494094 -o ROOT/results/node9/conversion-287048-1169494094 -C 600 -M 900 /tmp/evaluation/287048-1169494094/conversion /tmp/evaluation/287048-1169494094/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-287048-1169494094 -o ROOT/results/node9/solver-287048-1169494094 -C 1800 -M 900  /tmp/evaluation/287048-1169494094/solver

META MD5SUM SOLVER= 765b919a98ff2c4c419956167ea5299a
MD5SUM BENCH=  4c58eb69aa8058c4fc80a5c46de30e6e

RANDOM SEED= 349678028

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.231
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.231
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:       1466848 kB
Buffers:         50772 kB
Cached:         402316 kB
SwapCached:        268 kB
Active:          96628 kB
Inactive:       407620 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1466848 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            1608 kB
Writeback:           0 kB
Mapped:          64412 kB
Slab:            69500 kB
Committed_AS:  9053512 kB
PageTables:       2324 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 node9 on Mon Jan 22 19:28:21 UTC 2007