Trace number 283438

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.330948 0.344761

DiagnosticValue
CHECKS175469
NODES467

General information on the benchmark

Namecomposed/composed-25-1-25/
composed-25-1-25-0_ext.xml
MD5SUMf35314c55c71d7ece6e3141b56b33eb6
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.023995
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables33
Number of constraints247
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension247
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.34	s UNSATISFIABLE
0.34	d NODES 467
0.34	d CHECKS 175469
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/node70/watcher-283438-1169468847 -o ROOT/results/node70/solver-283438-1169468847 -C 1800 -M 900 /tmp/evaluation/283438-1169468847/solve /tmp/evaluation/283438-1169468847/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: 1.96 1.90 1.88 7/76 29998
/proc/meminfo: memFree=1718840/2055920 swapFree=4138760/4192956
[pid=29996] ppid=29994 vsize=5352 CPUtime=0
/proc/29996/stat : 29996 (solve) S 29994 29996 29115 0 -1 4194304 280 0 0 0 0 0 0 0 19 0 1 0 94381632 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 233402065732 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/29996/statm: 1338 229 192 169 0 49 0
[pid=29997] ppid=29996 vsize=5352 CPUtime=0
/proc/29997/stat : 29997 (solve) R 29996 29996 29115 0 -1 4194368 18 0 0 0 0 0 0 0 21 0 1 0 94381632 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 233402068263 0 0 4096 0 0 0 0 17 1 0 0
/proc/29997/statm: 1338 229 192 169 0 49 0

[startup+0.104886 s]
/proc/loadavg: 1.96 1.90 1.88 7/76 29998
/proc/meminfo: memFree=1718840/2055920 swapFree=4138760/4192956
[pid=29996] ppid=29994 vsize=5352 CPUtime=0
/proc/29996/stat : 29996 (solve) S 29994 29996 29115 0 -1 4194304 315 174 0 0 0 0 0 0 19 0 1 0 94381632 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 233402065732 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/29996/statm: 1338 229 192 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.344761
CPU time (s): 0.330948
CPU user time (s): 0.32295
CPU system time (s): 0.007998
CPU usage (%): 95.9935
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.32295
system time used= 0.007998
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= 15

runsolver used 0.003999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node70 on Mon Jan 22 12:27:27 UTC 2007


IDJOB= 283438
IDBENCH= 5101
IDSOLVER= 93
FILE ID= node70/283438-1169468847

PBS_JOBID= 3613837

Free space on /tmp= 66563 MiB

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

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node70/watcher-283438-1169468847 -o ROOT/results/node70/solver-283438-1169468847 -C 1800 -M 900  /tmp/evaluation/283438-1169468847/solve /tmp/evaluation/283438-1169468847/unknown 1800

META MD5SUM SOLVER= 4108942ff566d5523369442a8e3d06c4
MD5SUM BENCH=  f35314c55c71d7ece6e3141b56b33eb6

RANDOM SEED= 786327986

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.234
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.234
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:       1719392 kB
Buffers:          9440 kB
Cached:         232344 kB
SwapCached:      48644 kB
Active:         142688 kB
Inactive:       162700 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1719392 kB
SwapTotal:     4192956 kB
SwapFree:      4138760 kB
Dirty:             752 kB
Writeback:           0 kB
Mapped:          25064 kB
Slab:            16540 kB
Committed_AS:  1332392 kB
PageTables:       1776 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 node70 on Mon Jan 22 12:27:28 UTC 2007