Trace number 252407

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-04? (problem) 0.223965 0.232789

General information on the benchmark

Namebmc/
bmc-ibm-07-16.xml
MD5SUM53b837829140318714be73b2cc81c743
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark2.58261
SatisfiableNO
(Un)Satisfiability was proved
Number of variables8710
Number of constraints48484
Maximum constraint arity33
Maximum domain size16
Number of constraints which are defined in extension0
Number of constraints which are defined in intension48484
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.19
0.20	c 	predicates............ 0.02
0.23	c 	constraints.this top level constraint is not implemented

Verifier Data (download as text)

ERROR: Unexpected answer ! (SAT/UNSAT expected)
Got answer:

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node2/watcher-252407-1168407342 -o ROOT/results/node2/solver-252407-1168407342 -C 1800 -M 900 /tmp/evaluation/252407-1168407342/tramontane/bin/solver /tmp/evaluation/252407-1168407342/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.17 2.04 2.01 2/94 30095
/proc/meminfo: memFree=1628544/2055920 swapFree=4180528/4192956
[pid=30094] ppid=30092 vsize=540 CPUtime=0
/proc/30094/stat : 30094 (solver) R 30092 30094 29553 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 189129911 552960 26 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 10535716 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/30094/statm: 135 26 21 92 0 18 0

[startup+0.103499 s]
/proc/loadavg: 2.17 2.04 2.01 2/94 30095
/proc/meminfo: memFree=1628544/2055920 swapFree=4180528/4192956
[pid=30094] ppid=30092 vsize=8764 CPUtime=0.09
/proc/30094/stat : 30094 (solver) R 30092 30094 29553 0 -1 4194304 1258 0 0 0 9 0 0 0 20 0 1 0 189129911 8974336 1226 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134577261 0 0 4096 0 0 0 0 17 1 0 0
/proc/30094/statm: 2191 1226 692 92 0 535 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8764

Child status: 0
Real time (s): 0.232789
CPU time (s): 0.223965
CPU user time (s): 0.217966
CPU system time (s): 0.005999
CPU usage (%): 96.2094
Max. virtual memory (cumulated for all children) (KiB): 10744

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.217966
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= 1800
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= 35

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Wed Jan 10 05:35:43 UTC 2007


IDJOB= 252407
IDBENCH= 12933
FILE ID= node2/252407-1168407342

PBS_JOBID= 3523178

Free space on /tmp= 66525 MiB

BENCH NAME= HOME/pub/bench/CPAI06/bmc/bmc-ibm-07-16.xml
COMMAND LINE= /tmp/evaluation/252407-1168407342/tramontane/bin/solver /tmp/evaluation/252407-1168407342/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-252407-1168407342 -o ROOT/results/node2/solver-252407-1168407342 -C 1800 -M 900  /tmp/evaluation/252407-1168407342/tramontane/bin/solver /tmp/evaluation/252407-1168407342/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  53b837829140318714be73b2cc81c743

RANDOM SEED= 127187506

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.259
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	: 5931.00
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.259
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:       1629024 kB
Buffers:         42556 kB
Cached:         235876 kB
SwapCached:        504 kB
Active:         246844 kB
Inactive:       125616 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1629024 kB
SwapTotal:     4192956 kB
SwapFree:      4180528 kB
Dirty:            9704 kB
Writeback:           0 kB
Mapped:         114080 kB
Slab:            38836 kB
Committed_AS:  6401188 kB
PageTables:       2580 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= 66525 MiB



End job on node2 on Wed Jan 10 05:35:43 UTC 2007