Trace number 194215

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
Mistral 2006-12-04UNSAT 0.427934 0.431627

General information on the benchmark

Nameehi/ehi-85/
ehi-85-297-18_ext.xml
MD5SUM63acf96d707ae15bdb3b2fcf76cc15e8
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.225965
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables297
Number of constraints4120
Maximum constraint arity2
Maximum domain size7
Number of constraints which are defined in extension4120
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.01	c 	variables.............    0
0.01	c 	relations.............    0
0.02	c 	constraints........... 0.17
0.18	c Allocating memory
0.18	c 
0.18	c time limit = -1
0.18	c heuristic = dom/wdeg
0.18	c restart policy = No restart
0.18	c 
0.18	c Solving
0.18	c
0.42	s UNSATISFIABLE
0.42	d        UNSAT       177 BTS      0.23 s

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/node6/watcher-194215-1168099694 -o ROOT/results/node6/solver-194215-1168099694 -C 1800 -M 900 /tmp/evaluation/194215-1168099694/mistral/bin/solver /tmp/evaluation/194215-1168099694/unknown.xml -v 1 

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.09 0.31 0.83 4/81 17013
/proc/meminfo: memFree=1680016/2055924 swapFree=4165672/4192956
[pid=17012] ppid=17010 vsize=6792 CPUtime=0
/proc/17012/stat : 17012 (solver) R 17010 17012 16767 0 -1 4194304 421 0 0 0 0 0 0 0 18 0 1 0 158366334 6955008 400 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 2157432 0 0 4096 0 0 0 0 17 1 0 0
/proc/17012/statm: 1698 400 363 92 0 30 0

[startup+0.103765 s]
/proc/loadavg: 0.09 0.31 0.83 4/81 17013
/proc/meminfo: memFree=1680016/2055924 swapFree=4165672/4192956
[pid=17012] ppid=17010 vsize=7576 CPUtime=0.09
/proc/17012/stat : 17012 (solver) R 17010 17012 16767 0 -1 4194304 981 0 0 0 9 0 0 0 18 0 1 0 158366334 7757824 949 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134720127 0 0 4096 0 0 0 0 17 1 0 0
/proc/17012/statm: 1894 949 698 92 0 238 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7576

Child status: 0
Real time (s): 0.431627
CPU time (s): 0.427934
CPU user time (s): 0.421935
CPU system time (s): 0.005999
CPU usage (%): 99.1444
Max. virtual memory (cumulated for all children) (KiB): 9300

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.421935
system time used= 0.005999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1423
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= 14
involuntary context switches= 2

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node6 on Sat Jan  6 16:08:22 UTC 2007


IDJOB= 194215
IDBENCH= 3202
FILE ID= node6/194215-1168099694

PBS_JOBID= 3477033

Free space on /tmp= 66529 MiB

BENCH NAME= HOME/pub/bench/CPAI06/ehi/ehi-85/ehi-85-297-18_ext.xml
COMMAND LINE= /tmp/evaluation/194215-1168099694/mistral/bin/solver /tmp/evaluation/194215-1168099694/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-194215-1168099694 -o ROOT/results/node6/solver-194215-1168099694 -C 1800 -M 900  /tmp/evaluation/194215-1168099694/mistral/bin/solver /tmp/evaluation/194215-1168099694/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  63acf96d707ae15bdb3b2fcf76cc15e8

RANDOM SEED= 202173620

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:      2055924 kB
MemFree:       1680624 kB
Buffers:         40732 kB
Cached:         208664 kB
SwapCached:       2476 kB
Active:         128712 kB
Inactive:       157384 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1680624 kB
SwapTotal:     4192956 kB
SwapFree:      4165672 kB
Dirty:            3504 kB
Writeback:           0 kB
Mapped:          46380 kB
Slab:            74320 kB
Committed_AS:  4339392 kB
PageTables:       2196 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 node6 on Sat Jan  6 16:08:36 UTC 2007