Trace number 283481

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
rjw-solver 2007-01-21UNSAT 0.310952 0.318458

DiagnosticValue
CHECKS142223
NODES547

General information on the benchmark

Namecomposed/composed-25-1-2/
composed-25-1-2-5_ext.xml
MD5SUMb3956eedef1d3ae0ff181403ff3b6e4e
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.021995
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables33
Number of constraints224
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension224
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.31	s UNSATISFIABLE
0.31	d NODES 547
0.31	d CHECKS 142223
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/node6/watcher-283481-1169469669 -o ROOT/results/node6/solver-283481-1169469669 -C 1800 -M 900 /tmp/evaluation/283481-1169469669/solve /tmp/evaluation/283481-1169469669/unknown 1800 

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.66 0.97 1.23 3/81 15263
/proc/meminfo: memFree=1243216/2055924 swapFree=4165736/4192956
[pid=15262] ppid=15260 vsize=5352 CPUtime=0
/proc/15262/stat : 15262 (solve) R 15260 15262 14780 0 -1 4194304 283 174 0 0 0 0 0 0 18 0 1 0 295362441 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 268582840991 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/15262/statm: 1338 229 192 169 0 49 0
[pid=15265] ppid=15262 vsize=5352 CPUtime=0
/proc/15265/stat : 15265 (solve) R 15262 15262 14780 0 -1 4194368 18 0 0 0 0 0 0 0 18 0 1 0 295362442 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 4542830 0 0 4100 65536 0 0 0 17 1 0 0
/proc/15265/statm: 1338 229 192 169 0 49 0

[startup+0.106677 s]
/proc/loadavg: 0.66 0.97 1.23 3/81 15263
/proc/meminfo: memFree=1243216/2055924 swapFree=4165736/4192956
[pid=15262] ppid=15260 vsize=5352 CPUtime=0
/proc/15262/stat : 15262 (solve) S 15260 15262 14780 0 -1 4194304 315 174 0 0 0 0 0 0 18 0 1 0 295362441 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 268582839108 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/15262/statm: 1338 229 192 169 0 49 0
[pid=15265] ppid=15262 vsize=4200 CPUtime=0.09
/proc/15265/stat : 15265 (xlisp) R 15262 15262 14780 0 -1 4194304 551 0 0 0 9 0 0 0 19 0 1 0 295362442 4300800 509 18446744073709551615 134512640 135322396 4294956848 18446744073709551615 134877159 0 0 4096 130 0 0 0 17 1 0 0
/proc/15265/statm: 1050 509 243 197 0 290 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9552

Child status: 0
Real time (s): 0.318458
CPU time (s): 0.310952
CPU user time (s): 0.301954
CPU system time (s): 0.008998
CPU usage (%): 97.643
Max. virtual memory (cumulated for all children) (KiB): 9552

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.301954
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1238
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= 16

runsolver used 0.001999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node6 on Mon Jan 22 12:41:09 UTC 2007


IDJOB= 283481
IDBENCH= 5244
IDSOLVER= 93
FILE ID= node6/283481-1169469669

PBS_JOBID= 3613635

Free space on /tmp= 66564 MiB

SOLVER NAME= rjw-solver 2007-01-21
BENCH NAME= HOME/pub/bench/CPAI06/composed/composed-25-1-2/composed-25-1-2-5_ext.xml
COMMAND LINE= /tmp/evaluation/283481-1169469669/solve /tmp/evaluation/283481-1169469669/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node6/convwatcher-283481-1169469669 -o ROOT/results/node6/conversion-283481-1169469669 -C 600 -M 900 /tmp/evaluation/283481-1169469669/conversion /tmp/evaluation/283481-1169469669/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-283481-1169469669 -o ROOT/results/node6/solver-283481-1169469669 -C 1800 -M 900  /tmp/evaluation/283481-1169469669/solve /tmp/evaluation/283481-1169469669/unknown 1800

META MD5SUM SOLVER= 4108942ff566d5523369442a8e3d06c4
MD5SUM BENCH=  b3956eedef1d3ae0ff181403ff3b6e4e

RANDOM SEED= 803977734

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.240
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.240
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:      2055924 kB
MemFree:       1243696 kB
Buffers:         67428 kB
Cached:         622480 kB
SwapCached:       2944 kB
Active:         348808 kB
Inactive:       378360 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1243696 kB
SwapTotal:     4192956 kB
SwapFree:      4165736 kB
Dirty:             980 kB
Writeback:           0 kB
Mapped:          46660 kB
Slab:            70132 kB
Committed_AS:  9298504 kB
PageTables:       2196 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 node6 on Mon Jan 22 12:41:10 UTC 2007