Trace number 252397

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
BPrologCSPSolver70a 2006-12-13UNSAT 2.58261 2.61709

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)

2.60	
2.60	Time: 2474
2.60	
c 
c 
c 
c solution file
c 
c 

UNSAT

c 
c 
c 
c conversion script
c 
c 

converting(/tmp/evaluation/252397-1168407308/unknown)

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/node9/watcher-252397-1168407308 -o ROOT/results/node9/solver-252397-1168407308 -C 1800 -M 900 /tmp/evaluation/252397-1168407308/Complete/Ordinary/solver /tmp/evaluation/252397-1168407308/unknown 1800 

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.12 2.04 2.01 5/94 16652
/proc/meminfo: memFree=1533768/2055920 swapFree=4191880/4192956
[pid=16651] ppid=16649 vsize=5352 CPUtime=0
/proc/16651/stat : 16651 (sh) R 16649 16651 15607 0 -1 4194304 266 0 0 0 0 0 0 0 21 0 1 0 189128857 5480448 233 18446744073709551615 4194304 4889804 548682069344 18446744073709551615 4376579 0 0 4100 65536 0 0 0 17 1 0 0
/proc/16651/statm: 1338 233 196 169 0 49 0

[startup+0.103297 s]
/proc/loadavg: 2.12 2.04 2.01 5/94 16652
/proc/meminfo: memFree=1533768/2055920 swapFree=4191880/4192956
[pid=16651] ppid=16649 vsize=61640 CPUtime=0.08
/proc/16651/stat : 16651 (bprolog) R 16649 16651 15607 0 -1 4194304 2111 0 0 0 8 0 0 0 21 0 1 0 189128857 63119360 1827 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134555972 0 0 4096 2 0 0 0 17 1 0 0
/proc/16651/statm: 15410 1827 158 90 0 14948 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 61640

[startup+0.511341 s]
/proc/loadavg: 2.12 2.04 2.01 5/94 16652
/proc/meminfo: memFree=1533768/2055920 swapFree=4191880/4192956
[pid=16651] ppid=16649 vsize=61640 CPUtime=0.49
/proc/16651/stat : 16651 (bprolog) R 16649 16651 15607 0 -1 4194304 8428 0 0 0 46 3 0 0 24 0 1 0 189128857 63119360 8144 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 9063420 0 0 4096 2 0 0 0 17 1 0 0
/proc/16651/statm: 15410 8144 158 90 0 14948 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 61640

[startup+1.33243 s]
/proc/loadavg: 2.12 2.04 2.01 3/94 16652
/proc/meminfo: memFree=1469512/2055920 swapFree=4191880/4192956
[pid=16651] ppid=16649 vsize=81832 CPUtime=1.3
/proc/16651/stat : 16651 (bprolog) R 16649 16651 15607 0 -1 4194304 16624 0 0 0 123 7 0 0 25 0 1 0 189128857 83795968 16192 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134607469 0 0 4096 2 0 0 0 17 1 0 0
/proc/16651/statm: 20458 16192 158 90 0 19996 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 81832

Child status: 0
Real time (s): 2.61709
CPU time (s): 2.58261
CPU user time (s): 2.49062
CPU system time (s): 0.091986
CPU usage (%): 98.6826
Max. virtual memory (cumulated for all children) (KiB): 84332

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.49062
system time used= 0.091986
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 18674
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= 9
involuntary context switches= 114

runsolver used 0.005999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Wed Jan 10 05:35:09 UTC 2007


IDJOB= 252397
IDBENCH= 12933
FILE ID= node9/252397-1168407308

PBS_JOBID= 3523065

Free space on /tmp= 66540 MiB

BENCH NAME= HOME/pub/bench/CPAI06/bmc/bmc-ibm-07-16.xml
COMMAND LINE= /tmp/evaluation/252397-1168407308/Complete/Ordinary/solver /tmp/evaluation/252397-1168407308/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node9/convwatcher-252397-1168407308 -o ROOT/results/node9/conversion-252397-1168407308 -C 600 -M 900 /tmp/evaluation/252397-1168407308/Complete/Ordinary/conversion /tmp/evaluation/252397-1168407308/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-252397-1168407308 -o ROOT/results/node9/solver-252397-1168407308 -C 1800 -M 900  /tmp/evaluation/252397-1168407308/Complete/Ordinary/solver /tmp/evaluation/252397-1168407308/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  53b837829140318714be73b2cc81c743

RANDOM SEED= 799239430

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.231
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.231
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:       1534184 kB
Buffers:         60172 kB
Cached:         318316 kB
SwapCached:        408 kB
Active:         315156 kB
Inactive:       155140 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1534184 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:           11616 kB
Writeback:           0 kB
Mapped:         112312 kB
Slab:            35800 kB
Committed_AS:  7234072 kB
PageTables:       2488 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= 66536 MiB



End job on node9 on Wed Jan 10 05:35:40 UTC 2007