Trace number 40880

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 20.2649 20.276

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1111224255.opb
MD5SUM907b081b964ca265d29825e5079e97bd
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.58491
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 1217
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/node63/40880-1149208638/instance-40880-1149208638.opb ......
20.27	c done parsing opb.
20.27	s UNSATISFIABLE
20.27	c Total Run Time					20.2589

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/node63/watcher-40880-1149208638 -o ROOT/results/node63/solver-40880-1149208638 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node63/40880-1149208638/instance-40880-1149208638.opb 831070374 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.65 0.87 0.88 4/64 6559
/proc/meminfo: memFree=1497040/2055920 swapFree=4182328/4192956
[pid=6559] ppid=6557 vsize=1368 CPUtime=0
/proc/6559/stat : 6559 (PBS4L) R 6557 6559 6514 0 -1 4194304 111 0 0 0 0 0 0 0 19 0 1 0 186430935 1400832 95 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 135132864 0 0 4096 0 0 0 0 17 1 0 0
/proc/6559/statm: 342 95 84 232 0 107 0

[startup+10.0023 s]
/proc/loadavg: 0.70 0.87 0.88 2/64 6559
/proc/meminfo: memFree=1489240/2055920 swapFree=4182328/4192956
[pid=6559] ppid=6557 vsize=12896 CPUtime=9.99
/proc/6559/stat : 6559 (PBS4L) R 6557 6559 6514 0 -1 4194304 2415 0 0 0 993 6 0 0 25 0 1 0 186430935 13205504 2056 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 135140097 0 0 4096 0 0 0 0 17 1 0 0
/proc/6559/statm: 3224 2056 105 232 0 2989 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 12896

[startup+20.0093 s]
/proc/loadavg: 0.75 0.88 0.88 2/64 6559
/proc/meminfo: memFree=1486616/2055920 swapFree=4182328/4192956
[pid=6559] ppid=6557 vsize=15748 CPUtime=19.99
/proc/6559/stat : 6559 (PBS4L) R 6557 6559 6514 0 -1 4194304 3445 0 0 0 1989 10 0 0 25 0 1 0 186430935 16125952 2701 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 134552182 0 0 4096 0 0 0 0 17 1 0 0
/proc/6559/statm: 3937 2701 105 232 0 3702 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 15748

Child status: 0
Real time (s): 20.276
CPU time (s): 20.2649
CPU user time (s): 20.1569
CPU system time (s): 0.107983
CPU usage (%): 99.9452
Max. virtual memory (cumulated for all children) (Kb): 15748

Launcher Data (download as text)

Begin job on node63 on Fri Jun  2 00:37:18 UTC 2006


FILE ID= 40880-1149208638

PBS_JOBID= 293603

BENCH NAME= ROOT/tmp/node63/40880-1149208638/instance-40880-1149208638.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node63/40880-1149208638/instance-40880-1149208638.opb 831070374
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node63/watcher-40880-1149208638 -o ROOT/results/node63/solver-40880-1149208638 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node63/40880-1149208638/instance-40880-1149208638.opb 831070374

MD5SUM SOLVER= ab46593c31a6a47b9d9920387a00d332
MD5SUM BENCH=  907b081b964ca265d29825e5079e97bd

RANDOM SEED= 831070374


/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.228
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.228
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:       1497248 kB
Buffers:         32964 kB
Cached:         450888 kB
SwapCached:       2824 kB
Active:         106164 kB
Inactive:       386832 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1497248 kB
SwapTotal:     4192956 kB
SwapFree:      4182328 kB
Dirty:             316 kB
Writeback:           0 kB
Mapped:          15864 kB
Slab:            51644 kB
Committed_AS:   177624 kB
PageTables:       1476 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node63 on Fri Jun  2 00:37:38 UTC 2006