Trace number 252761

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 2006-12-09SAT 0.491925 0.495583

DiagnosticValue
CHECKS64480
NODES252

General information on the benchmark

Namecoloring/
dsjc-125-1-5-ext.xml
MD5SUMb5b06de4e97ce0cff637b76e26edc390
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.05599
SatisfiableYES
(Un)Satisfiability was proved
Number of variables125
Number of constraints736
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension736
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.49	v 0 1 3 1 2 2 3 0 3 0 4 3 3 4 1 2 3 1 1 0 4 1 1 2 2 3 0 4 4 0 2 0 4 4 0 3 2 0 0 4 4 4 2 2 0 4 1 3 1 3 2 2 3 2 0 1 1 4 3 3 0 4 1 2 1 0 3 4 0 1 0 2 0 1 3 3 1 3 2 1 1 0 1 0 3 2 1 1 3 0 0 3 2 2 4 2 3 4 2 1 2 1 2 0 4 3 3 3 1 2 1 1 4 3 0 2 4 3 1 3 0 1 4 3 0 
0.49	s SATISFIABLE
0.49	d NODES 252
0.49	d CHECKS 64480
c 
c 
c 
c conversion script
c 
c

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node14/watcher-252761-1168383480 -o ROOT/results/node14/solver-252761-1168383480 -C 1800 -M 900 /tmp/evaluation/252761-1168383480/solve /tmp/evaluation/252761-1168383480/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.20 0.65 0.85 2/81 14300
/proc/meminfo: memFree=1744736/2055920 swapFree=4158768/4192956
[pid=14299] ppid=14297 vsize=5352 CPUtime=0
/proc/14299/stat : 14299 (solve) R 14297 14299 14130 0 -1 4194304 283 174 0 0 0 0 0 0 18 0 1 0 186743169 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 212234463903 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/14299/statm: 1338 229 192 169 0 49 0
[pid=14302] ppid=14299 vsize=5352 CPUtime=0
/proc/14302/stat : 14302 (solve) D 14299 14299 14130 0 -1 4194368 19 0 0 0 0 0 0 0 18 0 1 0 186743170 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 212234631781 0 2147483391 4100 65536 18446744072099781622 0 0 17 1 0 0
/proc/14302/statm: 1338 229 192 169 0 49 0

[startup+0.103109 s]
/proc/loadavg: 0.20 0.65 0.85 2/81 14300
/proc/meminfo: memFree=1744736/2055920 swapFree=4158768/4192956
[pid=14299] ppid=14297 vsize=5352 CPUtime=0
/proc/14299/stat : 14299 (solve) S 14297 14299 14130 0 -1 4194304 315 174 0 0 0 0 0 0 18 0 1 0 186743169 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 212234462020 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/14299/statm: 1338 229 192 169 0 49 0
[pid=14302] ppid=14299 vsize=4364 CPUtime=0.09
/proc/14302/stat : 14302 (xlisp) R 14299 14299 14130 0 -1 4194304 599 0 0 0 9 0 0 0 18 0 1 0 186743170 4468736 557 18446744073709551615 134512640 135322396 4294956848 18446744073709551615 134684902 0 0 4096 130 0 0 0 17 1 0 0
/proc/14302/statm: 1091 557 242 197 0 331 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9716

Child status: 0
Real time (s): 0.495583
CPU time (s): 0.491925
CPU user time (s): 0.479927
CPU system time (s): 0.011998
CPU usage (%): 99.2619
Max. virtual memory (cumulated for all children) (KiB): 10340

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.479927
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1747
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= 39
involuntary context switches= 13

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node14 on Tue Jan  9 22:58:00 UTC 2007


IDJOB= 252761
IDBENCH= 12966
FILE ID= node14/252761-1168383480

PBS_JOBID= 3522505

Free space on /tmp= 66562 MiB

BENCH NAME= HOME/pub/bench/CPAI06/coloring/dsjc-125-1-5-ext.xml
COMMAND LINE= /tmp/evaluation/252761-1168383480/solve /tmp/evaluation/252761-1168383480/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node14/convwatcher-252761-1168383480 -o ROOT/results/node14/conversion-252761-1168383480 -C 600 -M 900 /tmp/evaluation/252761-1168383480/conversion /tmp/evaluation/252761-1168383480/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node14/watcher-252761-1168383480 -o ROOT/results/node14/solver-252761-1168383480 -C 1800 -M 900  /tmp/evaluation/252761-1168383480/solve /tmp/evaluation/252761-1168383480/unknown 1800

META MD5SUM SOLVER= 91bbaf997669a18b91ccd2f734d8d9ca
MD5SUM BENCH=  b5b06de4e97ce0cff637b76e26edc390

RANDOM SEED= 897741967

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.227
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.227
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:       1745216 kB
Buffers:         50248 kB
Cached:         175944 kB
SwapCached:       3240 kB
Active:         148300 kB
Inactive:       106432 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1745216 kB
SwapTotal:     4192956 kB
SwapFree:      4158768 kB
Dirty:            1092 kB
Writeback:           0 kB
Mapped:          35324 kB
Slab:            41156 kB
Committed_AS:  6660072 kB
PageTables:       2016 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 node14 on Tue Jan  9 22:58:04 UTC 2007