Trace number 287256

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 21.0568 21.2826

General information on the benchmark

Namelard/
lard-83-83.xml
MD5SUMee46835fd00d02a10e04381bf08a6075
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark17.1344
SatisfiableYES
(Un)Satisfiability was proved
Number of variables83
Number of constraints3403
Maximum constraint arity2
Maximum domain size84
Number of constraints which are defined in extension3403
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.10	c 
0.10	c Parsing xml file
0.10	c 	domains...............    0
0.10	c 	variables.............    0
0.10	c 	relations............. 19.4
19.58	c 	constraints........... 1.25
20.84	c Allocating memory
21.07	c 
21.07	c time limit = -1
21.07	c heuristic = dom/wdeg
21.07	c restart policy = Geometric increment
21.07	c restart base = 54
21.07	c restart factor = 1.33
21.07	c 
21.07	c Solving
21.07	c
21.18	s SATISFIABLE
21.18	v 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
21.18	d          SAT         0 BTS      0.06 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/node13/watcher-287256-1170112761 -o ROOT/results/node13/solver-287256-1170112761 -C 1800 -M 900 /tmp/evaluation/287256-1170112761/tramontane/bin/solver /tmp/evaluation/287256-1170112761/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: 2.06 2.11 2.15 5/86 29929
/proc/meminfo: memFree=1364416/2055920 swapFree=4192812/4192956
[pid=29928] ppid=29926 vsize=18540 CPUtime=0
/proc/29928/stat : 29928 (runsolver) R 29926 29928 29071 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 31230675 18984960 279 18446744073709551615 4194304 4267372 548682068992 18446744073709551615 269757246759 0 0 4096 24578 0 0 0 17 1 0 0
/proc/29928/statm: 4635 279 244 17 0 2626 0

[startup+0.108064 s]
/proc/loadavg: 2.06 2.11 2.15 5/86 29929
/proc/meminfo: memFree=1364416/2055920 swapFree=4192812/4192956
[pid=29928] ppid=29926 vsize=8660 CPUtime=0.09
/proc/29928/stat : 29928 (solver) R 29926 29928 29071 0 -1 4194304 1199 0 0 0 9 0 0 0 20 0 1 0 31230675 8867840 1167 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 4159426480 0 0 4096 0 0 0 0 17 1 0 0
/proc/29928/statm: 2165 1167 702 92 0 477 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8660

[startup+0.516121 s]
/proc/loadavg: 2.06 2.11 2.15 5/86 29929
/proc/meminfo: memFree=1364416/2055920 swapFree=4192812/4192956
[pid=29928] ppid=29926 vsize=13376 CPUtime=0.49
/proc/29928/stat : 29928 (solver) R 29926 29928 29071 0 -1 4194304 2379 0 0 0 49 0 0 0 24 0 1 0 31230675 13697024 2347 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 4157911357 0 0 4096 0 0 0 0 17 1 0 0
/proc/29928/statm: 3344 2347 702 92 0 1656 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 13376

[startup+1.33723 s]
/proc/loadavg: 2.06 2.11 2.15 3/86 29929
/proc/meminfo: memFree=1350528/2055920 swapFree=4192812/4192956
[pid=29928] ppid=29926 vsize=22940 CPUtime=1.31
/proc/29928/stat : 29928 (solver) R 29926 29928 29071 0 -1 4194304 4786 0 0 0 129 2 0 0 25 0 1 0 31230675 23490560 4754 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 12015011 0 0 4096 0 0 0 0 17 1 0 0
/proc/29928/statm: 5735 4754 702 92 0 4047 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 22940

[startup+2.97445 s]
/proc/loadavg: 2.06 2.11 2.15 3/86 29929
/proc/meminfo: memFree=1335424/2055920 swapFree=4192812/4192956
[pid=29928] ppid=29926 vsize=41800 CPUtime=2.9
/proc/29928/stat : 29928 (solver) R 29926 29928 29071 0 -1 4194304 9485 0 0 0 287 3 0 0 25 0 1 0 31230675 42803200 9453 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 12312322 0 0 4096 0 0 0 0 17 1 0 0
/proc/29928/statm: 10450 9453 702 92 0 8762 0
Current children cumulated CPU time (s) 2.9
Current children cumulated vsize (KiB) 41800

[startup+6.25388 s]
/proc/loadavg: 2.14 2.13 2.15 3/86 29929
/proc/meminfo: memFree=1299136/2055920 swapFree=4192812/4192956
[pid=29928] ppid=29926 vsize=80192 CPUtime=6.16
/proc/29928/stat : 29928 (solver) R 29926 29928 29071 0 -1 4194304 19086 0 0 0 608 8 0 0 25 0 1 0 31230675 82116608 19054 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134598624 0 0 4096 0 0 0 0 17 1 0 0
/proc/29928/statm: 20048 19054 702 92 0 18360 0
Current children cumulated CPU time (s) 6.16
Current children cumulated vsize (KiB) 80192

[startup+12.7188 s]
/proc/loadavg: 2.13 2.12 2.15 3/86 29929
/proc/meminfo: memFree=1219776/2055920 swapFree=4192812/4192956
[pid=29928] ppid=29926 vsize=156040 CPUtime=12.56
/proc/29928/stat : 29928 (solver) R 29926 29928 29071 0 -1 4194304 38052 0 0 0 1240 16 0 0 25 0 1 0 31230675 159784960 38020 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 12015205 0 0 4096 0 0 0 0 17 1 0 0
/proc/29928/statm: 39010 38020 702 92 0 37322 0
Current children cumulated CPU time (s) 12.56
Current children cumulated vsize (KiB) 156040

Child status: 0
Real time (s): 21.2826
CPU time (s): 21.0568
CPU user time (s): 20.7428
CPU system time (s): 0.313952
CPU usage (%): 98.939
Max. virtual memory (cumulated for all children) (KiB): 240556

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 20.7428
system time used= 0.313952
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 59205
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= 17
involuntary context switches= 851

runsolver used 0.024996 s user time and 0.074988 s system time

The end

Launcher Data (download as text)

Begin job on node13 on Mon Jan 29 23:19:22 UTC 2007


IDJOB= 287256
IDBENCH= 19810
IDSOLVER= 85
FILE ID= node13/287256-1170112761

PBS_JOBID= 3690019

Free space on /tmp= 66410 MiB

SOLVER NAME= Tramontane 2006-12-04
BENCH NAME= HOME/pub/bench/CPAI06/lard/lard-83-83.xml
COMMAND LINE= /tmp/evaluation/287256-1170112761/tramontane/bin/solver /tmp/evaluation/287256-1170112761/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node13/watcher-287256-1170112761 -o ROOT/results/node13/solver-287256-1170112761 -C 1800 -M 900  /tmp/evaluation/287256-1170112761/tramontane/bin/solver /tmp/evaluation/287256-1170112761/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  ee46835fd00d02a10e04381bf08a6075

RANDOM SEED= 166577457

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.236
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.236
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:       1364896 kB
Buffers:         18696 kB
Cached:         354964 kB
SwapCached:          0 kB
Active:         367384 kB
Inactive:       269088 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1364896 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           68808 kB
Writeback:           0 kB
Mapped:         282360 kB
Slab:            38728 kB
Committed_AS:   823984 kB
PageTables:       2712 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= 66410 MiB



End job on node13 on Mon Jan 29 23:19:43 UTC 2007