Trace number 192100

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-04SAT 4.35734 4.3627

General information on the benchmark

Namequeens/
queens-180.xml
MD5SUMc796a276961c748e1ef388ea91350f5c
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark4.35734
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables180
Number of constraints16110
Maximum constraint arity2
Maximum domain size180
Number of constraints which are defined in extension0
Number of constraints which are defined in intension16110
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 	predicates............    0
0.01	c 	constraints........... 1.08
1.10	c Allocating memory
1.10	c 
1.10	c time limit = -1
1.10	c heuristic = dom/wdeg
1.10	c restart policy = Geometric increment
1.10	c restart base = 119
1.10	c restart factor = 1.33
1.10	c 
1.10	c Solving
1.10	c
4.33	s SATISFIABLE
4.33	v 110 113 106 117 107 102 41 114 116 108 126 112 131 133 120 115 129 33 147 161 118 104 165 170 168 163 128 18 167 157 160 26 12 6 1 98 169 111 143 150 2 136 32 13 134 138 20 5 7 125 135 122 130 35 64 30 53 38 73 105 96 29 100 24 76 74 97 86 101 14 16 34 44 99 78 95 25 4 28 119 121 123 109 21 132 83 85 164 152 90 127 93 158 162 124 81 151 155 63 159 94 65 11 72 156 166 23 8 140 3 144 31 47 9 36 22 42 40 10 173 15 75 19 37 43 172 179 177 27 178 17 175 171 146 142 153 139 154 149 67 145 141 148 103 137 69 62 84 87 92 60 91 176 174 66 180 88 82 79 52 89 51 70 61 39 80 77 71 68 46 55 50 58 56 54 59 57 49 45 48
4.33	d          SAT       796 BTS       3.2 s

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node15/watcher-192100-1168096617 -o ROOT/results/node15/solver-192100-1168096617 -C 1800 -M 900 /tmp/evaluation/192100-1168096617/tramontane/bin/solver /tmp/evaluation/192100-1168096617/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: 1.00 1.25 1.58 4/86 22020
/proc/meminfo: memFree=1701592/2055920 swapFree=4174172/4192956
[pid=22019] ppid=22017 vsize=6792 CPUtime=0
/proc/22019/stat : 22019 (solver) R 22017 22019 21549 0 -1 4194304 399 0 0 0 0 0 0 0 18 0 1 0 158057825 6955008 380 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 7482232 0 0 4096 0 0 0 0 17 1 0 0
/proc/22019/statm: 1698 380 356 92 0 30 0

[startup+0.107668 s]
/proc/loadavg: 1.00 1.25 1.58 4/86 22020
/proc/meminfo: memFree=1701592/2055920 swapFree=4174172/4192956
[pid=22019] ppid=22017 vsize=7460 CPUtime=0.1
/proc/22019/stat : 22019 (solver) R 22017 22019 21549 0 -1 4194304 953 0 0 0 10 0 0 0 18 0 1 0 158057825 7639040 921 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 4158769646 0 0 4096 0 0 0 0 17 1 0 0
/proc/22019/statm: 1865 921 706 92 0 209 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 7460

[startup+0.515739 s]
/proc/loadavg: 1.00 1.25 1.58 4/86 22020
/proc/meminfo: memFree=1701592/2055920 swapFree=4174172/4192956
[pid=22019] ppid=22017 vsize=9180 CPUtime=0.5
/proc/22019/stat : 22019 (solver) R 22017 22019 21549 0 -1 4194304 1374 0 0 0 50 0 0 0 22 0 1 0 158057825 9400320 1342 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 7947899 0 0 4096 0 0 0 0 17 1 0 0
/proc/22019/statm: 2295 1342 706 92 0 639 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 9180

[startup+1.33688 s]
/proc/loadavg: 1.08 1.26 1.58 3/86 22020
/proc/meminfo: memFree=1694872/2055920 swapFree=4174172/4192956
[pid=22019] ppid=22017 vsize=13388 CPUtime=1.32
/proc/22019/stat : 22019 (solver) R 22017 22019 21549 0 -1 4194304 2398 0 0 0 132 0 0 0 25 0 1 0 158057825 13709312 2366 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134708400 0 0 4096 0 0 0 0 17 1 0 0
/proc/22019/statm: 3347 2366 716 92 0 1691 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 13388

[startup+2.97416 s]
/proc/loadavg: 1.08 1.26 1.58 3/86 22020
/proc/meminfo: memFree=1694744/2055920 swapFree=4174172/4192956
[pid=22019] ppid=22017 vsize=13392 CPUtime=2.96
/proc/22019/stat : 22019 (solver) R 22017 22019 21549 0 -1 4194304 2399 0 0 0 296 0 0 0 25 0 1 0 158057825 13713408 2367 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134655177 0 0 4096 0 0 0 0 17 1 0 0
/proc/22019/statm: 3348 2367 716 92 0 1692 0
Current children cumulated CPU time (s) 2.96
Current children cumulated vsize (KiB) 13392

Child status: 0
Real time (s): 4.3627
CPU time (s): 4.35734
CPU user time (s): 4.34634
CPU system time (s): 0.010998
CPU usage (%): 99.877
Max. virtual memory (cumulated for all children) (KiB): 13392

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 4.34634
system time used= 0.010998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2407
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= 12
involuntary context switches= 144

runsolver used 0.006998 s user time and 0.015997 s system time

The end

Launcher Data (download as text)

Begin job on node15 on Sat Jan  6 15:17:00 UTC 2007


IDJOB= 192100
IDBENCH= 3090
FILE ID= node15/192100-1168096617

PBS_JOBID= 3476490

Free space on /tmp= 66280 MiB

BENCH NAME= HOME/pub/bench/CPAI06/queens/queens-180.xml
COMMAND LINE= /tmp/evaluation/192100-1168096617/tramontane/bin/solver /tmp/evaluation/192100-1168096617/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node15/watcher-192100-1168096617 -o ROOT/results/node15/solver-192100-1168096617 -C 1800 -M 900  /tmp/evaluation/192100-1168096617/tramontane/bin/solver /tmp/evaluation/192100-1168096617/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  c796a276961c748e1ef388ea91350f5c

RANDOM SEED= 850826634

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.276
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.276
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:       1703400 kB
Buffers:         13344 kB
Cached:         172356 kB
SwapCached:       6400 kB
Active:         166968 kB
Inactive:       134112 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1703400 kB
SwapTotal:     4192956 kB
SwapFree:      4174172 kB
Dirty:            5116 kB
Writeback:           0 kB
Mapped:         128200 kB
Slab:            36052 kB
Committed_AS:  4346888 kB
PageTables:       2508 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= 66280 MiB



End job on node15 on Sat Jan  6 15:17:18 UTC 2007