Trace number 219783

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
Tramontane 2006-12-04UNSAT 0.308952 0.312644

General information on the benchmark

Nameehi/ehi-90/
ehi-90-315-91_ext.xml
MD5SUM4faafdaaba98c734fd516684ef4af7fe
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.308952
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables315
Number of constraints4377
Maximum constraint arity2
Maximum domain size7
Number of constraints which are defined in extension4377
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.19	c Allocating memory
0.19	c 
0.19	c time limit = -1
0.19	c heuristic = dom/wdeg
0.19	c restart policy = Geometric increment
0.19	c restart base = 209
0.19	c restart factor = 1.33
0.19	c 
0.19	c Solving
0.19	c
0.30	s UNSATISFIABLE
0.30	d        UNSAT       173 BTS       0.1 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/node51/watcher-219783-1168254919 -o ROOT/results/node51/solver-219783-1168254919 -C 1800 -M 900 /tmp/evaluation/219783-1168254919/tramontane/bin/solver /tmp/evaluation/219783-1168254919/unknown.xml -res geom -f 3 -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.85 0.80 0.88 4/68 21801
/proc/meminfo: memFree=1489352/2055920 swapFree=4192812/4192956
[pid=21800] ppid=21798 vsize=6792 CPUtime=0
/proc/21800/stat : 21800 (solver) R 21798 21800 21177 0 -1 4194304 288 0 0 0 0 0 0 0 18 0 1 0 173891188 6955008 269 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 2621528 0 0 4096 0 0 0 0 17 1 0 0
/proc/21800/statm: 1698 276 256 92 0 30 0

[startup+0.104557 s]
/proc/loadavg: 0.85 0.80 0.88 4/68 21801
/proc/meminfo: memFree=1489352/2055920 swapFree=4192812/4192956
[pid=21800] ppid=21798 vsize=7576 CPUtime=0.09
/proc/21800/stat : 21800 (solver) R 21798 21800 21177 0 -1 4194304 983 0 0 0 9 0 0 0 18 0 1 0 173891188 7757824 951 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 2735217 0 0 4096 0 0 0 0 17 1 0 0
/proc/21800/statm: 1894 951 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.312644
CPU time (s): 0.308952
CPU user time (s): 0.298954
CPU system time (s): 0.009998
CPU usage (%): 98.8191
Max. virtual memory (cumulated for all children) (KiB): 9436

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

runsolver used 0.004999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node51 on Mon Jan  8 11:15:24 UTC 2007


IDJOB= 219783
IDBENCH= 5325
FILE ID= node51/219783-1168254919

PBS_JOBID= 3482080

Free space on /tmp= 66560 MiB

BENCH NAME= HOME/pub/bench/CPAI06/ehi/ehi-90/ehi-90-315-91_ext.xml
COMMAND LINE= /tmp/evaluation/219783-1168254919/tramontane/bin/solver /tmp/evaluation/219783-1168254919/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node51/watcher-219783-1168254919 -o ROOT/results/node51/solver-219783-1168254919 -C 1800 -M 900  /tmp/evaluation/219783-1168254919/tramontane/bin/solver /tmp/evaluation/219783-1168254919/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  4faafdaaba98c734fd516684ef4af7fe

RANDOM SEED= 444871036

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.277
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.277
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:       1489896 kB
Buffers:         48124 kB
Cached:         444536 kB
SwapCached:          0 kB
Active:         165940 kB
Inactive:       346940 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1489896 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3876 kB
Writeback:           0 kB
Mapped:          30380 kB
Slab:            38892 kB
Committed_AS:  3814208 kB
PageTables:       1616 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= 66560 MiB



End job on node51 on Mon Jan  8 11:15:29 UTC 2007