Trace number 361327

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
PB-clasp 2007-04-10SAT 0.309952 0.280857

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga30_30_sat_pb.cnf.cr.opb
MD5SUM09dd38397cb073c3f8ce1c2b987fae03
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.023995
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables1350
Total number of constraints990
Number of constraints which are clauses930
Number of constraints which are cardinality constraints (but not clauses)60
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint15
Maximum length of a constraint30
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 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 31
Number of bits of the biggest sum of numbers5
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/0.27	s SATISFIABLE
0.00/0.27	v x30 x56 x71 x102 x148 x166 x209 x237 x265 x294 x323 x352 x381 x410 x439 x468 x497 x525 x554 x583 x610 x639 x668 x697 x726 x755
0.00/0.27	v x784 x813 x842 x871 x913 x927 x941 x955 x969 x983 x997 x1011 x1025 x1039 x1065 x1079 x1083 x1097 x1111 x1140 x1154 x1168 x1182
0.00/0.27	v x1196 x1210 x1224 x1238 x1252 x1266 x1280 x1294 x1308 x1322 x1336

Verifier Data (download as text)

OK	0

Conversion Script Data (download as text)

/tmp/evaluation/361327-1176982139/instance-361327-1176982139.opb is already a linear file

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node14/watcher-361327-1176982139 -o ROOT/results/node14/solver-361327-1176982139 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-361327-1176982139.opb /tmp/evaluation/361327-1176982139/temp 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.88 0.97 0.99 3/77 15948
/proc/meminfo: memFree=1731632/2055920 swapFree=4148736/4192956
[pid=15948] ppid=15946 vsize=12268 CPUtime=0
/proc/15948/stat : 15948 (pbclasp) R 15946 15948 15865 0 -1 4194304 397 0 0 0 0 0 0 0 18 0 1 0 146131710 12562432 363 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 212247785789 0 0 4224 0 0 0 0 17 1 0 0
/proc/15948/statm: 3067 364 276 3 0 167 0

[startup+0.106845 s]
/proc/loadavg: 0.88 0.97 0.99 3/77 15948
/proc/meminfo: memFree=1731632/2055920 swapFree=4148736/4192956
[pid=15948] ppid=15946 vsize=12400 CPUtime=0
/proc/15948/stat : 15948 (pbclasp) S 15946 15948 15865 0 -1 4194304 498 0 0 0 0 0 0 0 16 0 1 0 146131710 12697600 446 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 212243361890 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/15948/statm: 3100 446 320 3 0 200 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12400

[startup+0.202849 s]
/proc/loadavg: 0.88 0.97 0.99 3/77 15948
/proc/meminfo: memFree=1731632/2055920 swapFree=4148736/4192956
[pid=15948] ppid=15946 vsize=12400 CPUtime=0
/proc/15948/stat : 15948 (pbclasp) S 15946 15948 15865 0 -1 4194304 498 0 0 0 0 0 0 0 16 0 1 0 146131710 12697600 446 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 212243361890 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/15948/statm: 3100 446 320 3 0 200 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12400

Solver just ended. Dumping a history of the last processes samples

Child status: 0
Real time (s): 0.280857
CPU time (s): 0.309952
CPU user time (s): 0.292955
CPU system time (s): 0.016997
CPU usage (%): 110.359
Max. virtual memory (cumulated for all children) (KiB): 12400

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.292955
system time used= 0.016997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2467
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= 77
involuntary context switches= 19

runsolver used 0.004999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node14 on Thu Apr 19 11:29:00 UTC 2007

IDJOB= 361327
IDBENCH= 1434
IDSOLVER= 167
FILE ID= node14/361327-1176982139

PBS_JOBID= 4630413

Free space on /tmp= 66207 MiB

SOLVER NAME= PB-clasp 2007-03-23
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-fpga30_30_sat_pb.cnf.cr.opb
COMMAND LINE= pbclasp instance-361327-1176982139.opb /tmp/evaluation/361327-1176982139/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node14/convwatcher-361327-1176982139 -o ROOT/results/node14/conversion-361327-1176982139 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/361327-1176982139/instance-361327-1176982139.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node14/watcher-361327-1176982139 -o ROOT/results/node14/solver-361327-1176982139 -C 1800 -W 3600 -M 1800 --output-limit 1,15  pbclasp instance-361327-1176982139.opb /tmp/evaluation/361327-1176982139/temp

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  09dd38397cb073c3f8ce1c2b987fae03

RANDOM SEED= 886114350

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node14.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.227
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.227
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:       1732104 kB
Buffers:         35612 kB
Cached:         225188 kB
SwapCached:      11472 kB
Active:         123912 kB
Inactive:       159532 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1732104 kB
SwapTotal:     4192956 kB
SwapFree:      4148736 kB
Dirty:             824 kB
Writeback:           0 kB
Mapped:          29604 kB
Slab:            25944 kB
Committed_AS:  6647232 kB
PageTables:       1784 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= 66207 MiB

End job on node14 on Thu Apr 19 11:29:00 UTC 2007