Trace number 252823

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
galac 1UNSAT 0.677895 0.760103

General information on the benchmark

Namecoloring/
queens-5-5-4-ext.xml
MD5SUM08303d0bc839b66a68c1b7bcc600d2e9
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.005998
SatisfiableNO
(Un)Satisfiability was proved
Number of variables25
Number of constraints160
Maximum constraint arity2
Maximum domain size4
Number of constraints which are defined in extension160
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.04	c --- Preproc Stats ---
0.53	c start processing
0.53	c start relation processing
0.53	c start cnf exporting
0.70	c parsing time : 0.354
0.70	c preprocessing time : 0.526
0.70	
0.70	c Nary constraints - conflicts : 0 supports : 0
0.70	c Binary constraints - conflicts : 160 supports :0
0.70	c max arity constraint : 2
0.70	c Max Tuples generated 0
0.70	c relations : 1
0.70	c relations BDD: 0
0.70	c vars : 101 - clauses :  815
0.70	
0.75	 
0.75	c --- Minisat Stats ---
0.75	 
0.75	c restarts              : 1
0.75	c conflicts             : 26             (26026 /sec)
0.75	c decisions             : 32             (0.00 % random) (32032 /sec)
0.75	c propagations          : 767            (767768 /sec)
0.75	c conflict literals     : 94             (11.32 % deleted)
0.75	c Memory used           : 1.73 MB
0.75	c CPU time              : 0.000999 s
0.75	
0.75	s UNSATISFIABLE

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/node2/watcher-252823-1168409628 -o ROOT/results/node2/solver-252823-1168409628 -C 1800 -M 900 /tmp/evaluation/252823-1168409628/galac.sh /tmp/evaluation/252823-1168409628/unknown.xml 

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.62 1.92 1.97 5/93 31595
/proc/meminfo: memFree=1495504/2055920 swapFree=4180528/4192956
[pid=31594] ppid=31592 vsize=8560 CPUtime=0
/proc/31594/stat : 31594 (galac.sh) R 31592 31594 31224 0 -1 4194304 308 0 0 0 0 0 0 0 21 0 1 0 189358714 8765440 253 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 206381500303 0 0 4096 8192 0 0 0 17 1 0 0
/proc/31594/statm: 2140 253 197 79 0 133 0

[startup+0.110376 s]
/proc/loadavg: 1.62 1.92 1.97 5/93 31595
/proc/meminfo: memFree=1495504/2055920 swapFree=4180528/4192956
[pid=31594] ppid=31592 vsize=47556 CPUtime=0.01
/proc/31594/stat : 31594 (galac.sh) S 31592 31594 31224 0 -1 4194304 762 1704 0 0 0 0 0 1 25 0 1 0 189358714 48697344 363 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 206380919642 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/31594/statm: 11889 363 245 79 0 218 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

[startup+0.518446 s]
/proc/loadavg: 1.62 1.92 1.97 5/93 31595
/proc/meminfo: memFree=1495504/2055920 swapFree=4180528/4192956
[pid=31594] ppid=31592 vsize=47556 CPUtime=0.01
/proc/31594/stat : 31594 (galac.sh) S 31592 31594 31224 0 -1 4194304 762 1704 0 0 0 0 0 1 25 0 1 0 189358714 48697344 363 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 206380919642 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/31594/statm: 11889 363 245 79 0 218 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

Child status: 0
Real time (s): 0.760103
CPU time (s): 0.677895
CPU user time (s): 0.578911
CPU system time (s): 0.098984
CPU usage (%): 89.1846
Max. virtual memory (cumulated for all children) (KiB): 47556

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.578911
system time used= 0.098984
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 11642
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 723
involuntary context switches= 721

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Wed Jan 10 06:13:49 UTC 2007


IDJOB= 252823
IDBENCH= 12968
FILE ID= node2/252823-1168409628

PBS_JOBID= 3523201

Free space on /tmp= 66529 MiB

BENCH NAME= HOME/pub/bench/CPAI06/coloring/queens-5-5-4-ext.xml
COMMAND LINE= /tmp/evaluation/252823-1168409628/galac.sh /tmp/evaluation/252823-1168409628/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-252823-1168409628 -o ROOT/results/node2/solver-252823-1168409628 -C 1800 -M 900  /tmp/evaluation/252823-1168409628/galac.sh /tmp/evaluation/252823-1168409628/unknown.xml

META MD5SUM SOLVER= d8bf20eb49fe33822f00bab08f33d7fc
MD5SUM BENCH=  08303d0bc839b66a68c1b7bcc600d2e9

RANDOM SEED= 17085364

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.259
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	: 5931.00
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.259
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:       1495984 kB
Buffers:         44860 kB
Cached:         281444 kB
SwapCached:        504 kB
Active:         370580 kB
Inactive:       134664 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1495984 kB
SwapTotal:     4192956 kB
SwapFree:      4180528 kB
Dirty:            3112 kB
Writeback:           0 kB
Mapped:         200088 kB
Slab:            38948 kB
Committed_AS:  6486016 kB
PageTables:       2684 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= 66529 MiB



End job on node2 on Wed Jan 10 06:13:54 UTC 2007