Trace number 252328

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-04? (problem) 0.692893 0.696332

General information on the benchmark

Namebmc/
bmc-ibm-04-04.xml
MD5SUMa548ecc66839648c6a54820f84f1d686
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Satisfiable
(Un)Satisfiability was proved
Number of variables28161
Number of constraints167877
Maximum constraint arity26
Maximum domain size4
Number of constraints which are defined in extension0
Number of constraints which are defined in intension167877
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.61
0.62	c 	predicates............ 0.07
0.69	c 	constraints.unknown operator: neg

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/node40/watcher-252328-1168407045 -o ROOT/results/node40/solver-252328-1168407045 -C 1800 -M 900 /tmp/evaluation/252328-1168407045/mistral/bin/solver /tmp/evaluation/252328-1168407045/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: 1.21 1.22 1.15 4/65 2084
/proc/meminfo: memFree=1514672/2055920 swapFree=4192812/4192956
[pid=2083] ppid=2080 vsize=6792 CPUtime=0
/proc/2083/stat : 2083 (solver) R 2080 2083 821 0 -1 4194304 400 0 0 0 0 0 0 0 18 0 1 0 189103927 6955008 380 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 6880120 0 0 4096 0 0 0 0 17 1 0 0
/proc/2083/statm: 1698 385 358 92 0 30 0

[startup+0.106993 s]
/proc/loadavg: 1.21 1.22 1.15 4/65 2084
/proc/meminfo: memFree=1514672/2055920 swapFree=4192812/4192956
[pid=2083] ppid=2080 vsize=8684 CPUtime=0.1
/proc/2083/stat : 2083 (solver) R 2080 2083 821 0 -1 4194304 1203 0 0 0 10 0 0 0 18 0 1 0 189103927 8892416 1171 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7345787 0 0 4096 0 0 0 0 17 1 0 0
/proc/2083/statm: 2171 1171 692 92 0 515 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 8684

[startup+0.515045 s]
/proc/loadavg: 1.21 1.22 1.15 4/65 2084
/proc/meminfo: memFree=1514672/2055920 swapFree=4192812/4192956
[pid=2083] ppid=2080 vsize=14692 CPUtime=0.5
/proc/2083/stat : 2083 (solver) R 2080 2083 821 0 -1 4194304 2730 0 0 0 50 0 0 0 21 0 1 0 189103927 15044608 2698 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7345787 0 0 4096 0 0 0 0 17 1 0 0
/proc/2083/statm: 3673 2698 692 92 0 2017 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 14692

Child status: 0
Real time (s): 0.696332
CPU time (s): 0.692893
CPU user time (s): 0.678896
CPU system time (s): 0.013997
CPU usage (%): 99.5061
Max. virtual memory (cumulated for all children) (KiB): 16168

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.678896
system time used= 0.013997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3252
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= 4

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node40 on Wed Jan 10 05:30:46 UTC 2007


IDJOB= 252328
IDBENCH= 12925
FILE ID= node40/252328-1168407045

PBS_JOBID= 3523414

Free space on /tmp= 66532 MiB

BENCH NAME= HOME/pub/bench/CPAI06/bmc/bmc-ibm-04-04.xml
COMMAND LINE= /tmp/evaluation/252328-1168407045/mistral/bin/solver /tmp/evaluation/252328-1168407045/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node40/watcher-252328-1168407045 -o ROOT/results/node40/solver-252328-1168407045 -C 1800 -M 900  /tmp/evaluation/252328-1168407045/mistral/bin/solver /tmp/evaluation/252328-1168407045/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  a548ecc66839648c6a54820f84f1d686

RANDOM SEED= 622361847

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.239
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.239
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:       1515152 kB
Buffers:         52260 kB
Cached:         408780 kB
SwapCached:          0 kB
Active:         238916 kB
Inactive:       237488 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1515152 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           26444 kB
Writeback:           0 kB
Mapped:          25536 kB
Slab:            50444 kB
Committed_AS:  4196060 kB
PageTables:       1412 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= 66532 MiB



End job on node40 on Wed Jan 10 05:30:47 UTC 2007