Trace number 40932

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
PBS 4.1LUNSAT 24.7042 24.7125

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1111227012.opb
MD5SUMf1ef73d71b7207a4f4673a4d36adcee2
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
Best result obtained on this benchmarkUNSAT
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark0.111982
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables169
Total number of constraints101
Number of constraints which are clauses30
Number of constraints which are cardinality constraints (but not clauses)70
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint169
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 38
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 1220
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00	c PBS v4 by Bashar Al-Rawi & Fadi Aloul
0.00	c Solving ROOT/tmp/node7/40932-1149212362/instance-40932-1149212362.opb ......
24.70	c done parsing opb.
24.70	s UNSATISFIABLE
24.70	c Total Run Time					24.6962

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node7/watcher-40932-1149212362 -o ROOT/results/node7/solver-40932-1149212362 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node7/40932-1149212362/instance-40932-1149212362.opb 363672497 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.65 0.87 0.88 2/64 793
/proc/meminfo: memFree=1511840/2055920 swapFree=4181500/4192956
[pid=793] ppid=791 vsize=1400 CPUtime=0
/proc/793/stat : 793 (PBS4L) R 791 793 748 0 -1 4194304 148 0 0 0 0 0 0 0 18 0 1 0 186898441 1433600 131 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 134526219 0 0 4096 0 0 0 0 17 1 0 0
/proc/793/statm: 350 131 100 232 0 115 0

[startup+10.0023 s]
/proc/loadavg: 0.71 0.87 0.88 2/64 793
/proc/meminfo: memFree=1503840/2055920 swapFree=4181500/4192956
[pid=793] ppid=791 vsize=12884 CPUtime=9.99
/proc/793/stat : 793 (PBS4L) R 791 793 748 0 -1 4194304 2465 0 0 0 994 5 0 0 25 0 1 0 186898441 13193216 2106 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 134552425 0 0 4096 0 0 0 0 17 1 0 0
/proc/793/statm: 3221 2106 105 232 0 2986 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 12884

[startup+20.0094 s]
/proc/loadavg: 0.75 0.88 0.88 2/64 793
/proc/meminfo: memFree=1500512/2055920 swapFree=4181500/4192956
[pid=793] ppid=791 vsize=15900 CPUtime=19.99
/proc/793/stat : 793 (PBS4L) R 791 793 748 0 -1 4194304 3683 0 0 0 1992 7 0 0 25 0 1 0 186898441 16281600 2939 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 134552226 0 0 4096 0 0 0 0 17 1 0 0
/proc/793/statm: 3975 2939 105 232 0 3740 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 15900

Child status: 0
Real time (s): 24.7125
CPU time (s): 24.7042
CPU user time (s): 24.6153
CPU system time (s): 0.088986
CPU usage (%): 99.9665
Max. virtual memory (cumulated for all children) (Kb): 15900

Launcher Data (download as text)

Begin job on node7 on Fri Jun  2 01:39:22 UTC 2006


FILE ID= 40932-1149212362

PBS_JOBID= 294279

BENCH NAME= ROOT/tmp/node7/40932-1149212362/instance-40932-1149212362.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node7/40932-1149212362/instance-40932-1149212362.opb 363672497
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node7/watcher-40932-1149212362 -o ROOT/results/node7/solver-40932-1149212362 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node7/40932-1149212362/instance-40932-1149212362.opb 363672497

MD5SUM SOLVER= ab46593c31a6a47b9d9920387a00d332
MD5SUM BENCH=  f1ef73d71b7207a4f4673a4d36adcee2

RANDOM SEED= 363672497


/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.232
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.232
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:       1512112 kB
Buffers:         31332 kB
Cached:         441104 kB
SwapCached:       3564 kB
Active:         189420 kB
Inactive:       292144 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1512112 kB
SwapTotal:     4192956 kB
SwapFree:      4181500 kB
Dirty:             188 kB
Writeback:           0 kB
Mapped:          14960 kB
Slab:            48232 kB
Committed_AS:   176552 kB
PageTables:       1480 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node7 on Fri Jun  2 01:39:47 UTC 2006