Trace number 252701

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.600908 0.64827

General information on the benchmark

Namecoloring/
geom-40-3-ext.xml
MD5SUMd54325db3282ef19b94f41e995b8132d
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.003998
SatisfiableNO
(Un)Satisfiability was proved
Number of variables40
Number of constraints78
Maximum constraint arity2
Maximum domain size3
Number of constraints which are defined in extension78
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.03	c --- Preproc Stats ---
0.49	c start processing
0.49	c start relation processing
0.49	c start cnf exporting
0.60	c parsing time : 0.322
0.60	c preprocessing time : 0.439
0.60	
0.60	c Nary constraints - conflicts : 0 supports : 0
0.60	c Binary constraints - conflicts : 78 supports :0
0.60	c max arity constraint : 2
0.60	c Max Tuples generated 0
0.60	c relations : 1
0.60	c relations BDD: 0
0.60	c vars : 121 - clauses :  394
0.60	
0.64	 
0.64	c --- Minisat Stats ---
0.64	 
0.64	c restarts              : 1
0.64	c conflicts             : 8              (inf /sec)
0.64	c decisions             : 29             (0.00 % random) (inf /sec)
0.64	c propagations          : 181            (inf /sec)
0.64	c conflict literals     : 18             (0.00 % deleted)
0.64	c Memory used           : 1.73 MB
0.64	c CPU time              : 0 s
0.64	
0.64	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/node5/watcher-252701-1168409555 -o ROOT/results/node5/solver-252701-1168409555 -C 1800 -M 900 /tmp/evaluation/252701-1168409555/galac.sh /tmp/evaluation/252701-1168409555/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: 2.03 2.03 2.00 5/88 2352
/proc/meminfo: memFree=1165216/2055920 swapFree=4192812/4192956
[pid=2351] ppid=2349 vsize=8560 CPUtime=0
/proc/2351/stat : 2351 (galac.sh) R 2349 2351 2064 0 -1 4194304 308 0 0 0 0 0 0 0 21 0 1 0 169569958 8765440 253 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913666959 0 0 4096 8192 0 0 0 17 1 0 0
/proc/2351/statm: 2140 253 197 79 0 133 0

[startup+0.107324 s]
/proc/loadavg: 2.03 2.03 2.00 5/88 2352
/proc/meminfo: memFree=1165216/2055920 swapFree=4192812/4192956
[pid=2351] ppid=2349 vsize=47560 CPUtime=0.01
/proc/2351/stat : 2351 (galac.sh) S 2349 2351 2064 0 -1 4194304 761 1704 0 0 0 0 0 1 25 0 1 0 169569958 48701440 363 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/2351/statm: 11890 363 245 79 0 218 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47560

[startup+0.515367 s]
/proc/loadavg: 2.03 2.03 2.00 5/88 2352
/proc/meminfo: memFree=1165216/2055920 swapFree=4192812/4192956
[pid=2351] ppid=2349 vsize=47560 CPUtime=0.01
/proc/2351/stat : 2351 (galac.sh) S 2349 2351 2064 0 -1 4194304 761 1704 0 0 0 0 0 1 25 0 1 0 169569958 48701440 363 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/2351/statm: 11890 363 245 79 0 218 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47560

Child status: 0
Real time (s): 0.64827
CPU time (s): 0.600908
CPU user time (s): 0.512922
CPU system time (s): 0.087986
CPU usage (%): 92.6941
Max. virtual memory (cumulated for all children) (KiB): 47560

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.512922
system time used= 0.087986
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 11390
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= 400
involuntary context switches= 375

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Wed Jan 10 06:12:35 UTC 2007


IDJOB= 252701
IDBENCH= 12963
FILE ID= node5/252701-1168409555

PBS_JOBID= 3523199

Free space on /tmp= 66550 MiB

BENCH NAME= HOME/pub/bench/CPAI06/coloring/geom-40-3-ext.xml
COMMAND LINE= /tmp/evaluation/252701-1168409555/galac.sh /tmp/evaluation/252701-1168409555/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-252701-1168409555 -o ROOT/results/node5/solver-252701-1168409555 -C 1800 -M 900  /tmp/evaluation/252701-1168409555/galac.sh /tmp/evaluation/252701-1168409555/unknown.xml

META MD5SUM SOLVER= d8bf20eb49fe33822f00bab08f33d7fc
MD5SUM BENCH=  d54325db3282ef19b94f41e995b8132d

RANDOM SEED= 950306083

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:      2055920 kB
MemFree:       1165632 kB
Buffers:         60432 kB
Cached:         496964 kB
SwapCached:          0 kB
Active:         621692 kB
Inactive:       209524 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1165632 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3220 kB
Writeback:           0 kB
Mapped:         293628 kB
Slab:            43496 kB
Committed_AS:  5571348 kB
PageTables:       2624 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= 66550 MiB



End job on node5 on Wed Jan 10 06:12:36 UTC 2007