Trace number 253165

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
buggy_2_5 2007-01-08UNSAT 0.070988 0.0755061

General information on the benchmark

Namecoloring/
geom-30a-5-ext.xml
MD5SUM162106a1ffe1b0fbdc628fd119f2c399
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.004998
SatisfiableNO
(Un)Satisfiability was proved
Number of variables30
Number of constraints81
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension81
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

UNSAT

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/node10/watcher-253165-1168383645 -o ROOT/results/node10/solver-253165-1168383645 -C 1800 -M 900 /tmp/evaluation/253165-1168383645/solver /tmp/evaluation/253165-1168383645/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.76 1.01 1.05 4/81 21863
/proc/meminfo: memFree=1864016/2055920 swapFree=4178216/4192956
[pid=21862] ppid=21860 vsize=5352 CPUtime=0
/proc/21862/stat : 21862 (solver) S 21860 21862 19963 0 -1 4194304 295 26 0 0 0 0 0 0 19 0 1 0 186759853 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 214919865156 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/21862/statm: 1338 232 194 169 0 49 0

Child status: 0
Real time (s): 0.0755061
CPU time (s): 0.070988
CPU user time (s): 0.027995
CPU system time (s): 0.042993
CPU usage (%): 94.0163
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.027995
system time used= 0.042993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3245
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= 73
involuntary context switches= 16

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan  9 23:00:47 UTC 2007


IDJOB= 253165
IDBENCH= 12981
FILE ID= node10/253165-1168383645

PBS_JOBID= 3522523

Free space on /tmp= 66552 MiB

BENCH NAME= HOME/pub/bench/CPAI06/coloring/geom-30a-5-ext.xml
COMMAND LINE= /tmp/evaluation/253165-1168383645/solver /tmp/evaluation/253165-1168383645/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-253165-1168383645 -o ROOT/results/node10/solver-253165-1168383645 -C 1800 -M 900  /tmp/evaluation/253165-1168383645/solver /tmp/evaluation/253165-1168383645/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  162106a1ffe1b0fbdc628fd119f2c399

RANDOM SEED= 527950384

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.232
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.232
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:       1864432 kB
Buffers:         23280 kB
Cached:          81888 kB
SwapCached:       1864 kB
Active:          97872 kB
Inactive:        41236 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1864432 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:           11580 kB
Writeback:           0 kB
Mapped:          43760 kB
Slab:            37564 kB
Committed_AS:  5424696 kB
PageTables:       2064 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= 66553 MiB



End job on node10 on Tue Jan  9 23:00:47 UTC 2007