Trace number 361491

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
bsolo 3.0.16UNSAT 0.203968 0.20578

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-cache.inv10.ucl.opb
MD5SUM449faf6379a77b0035cc1474243ef90a
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.203968
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables8937
Total number of constraints26319
Number of constraints which are clauses26047
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints272
Minimum length of a constraint1
Maximum length of a constraint9
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 17
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 62
Number of bits of the biggest sum of numbers6
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.00	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.00	c Developed by Vasco Manquinho IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/361491-1176983301/instance-361491-1176983301.opb
0.00/0.00	c File size is 746606 bytes.
0.09/0.13	c Highest Coefficient sum: 62
0.09/0.13	c Parsing was ok!!
0.09/0.13	c Total parsing time: 0.129 s
0.09/0.14	c Var: 8937 Constr: 26319 26047/0/272 Lit: 63089 Watch. Lit: 52909
0.09/0.14	c Obj. Vars: 0 (0 % of total variables)
0.19/0.20	c CONFLICT DETECTED at PROBING!!!
0.19/0.20	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.19/0.20	c    0        0      0        0    26319    63089      0      0 0.20
0.19/0.20	s UNSATISFIABLE
0.19/0.20	c Total time: 0.199 s

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node45/watcher-361491-1176983301 -o ROOT/results/node45/solver-361491-1176983301 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361491-1176983301/instance-361491-1176983301.opb 

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.80 0.95 0.95 3/77 30727
/proc/meminfo: memFree=1770312/2055920 swapFree=4157496/4192956
[pid=30727] ppid=30725 vsize=12468 CPUtime=0
/proc/30727/stat : 30727 (bsolo3.0.16) R 30725 30727 30667 0 -1 4194304 370 0 0 0 0 0 0 0 18 0 1 0 53175696 12767232 338 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 5161394 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30727/statm: 3117 338 283 324 0 2003 0

[startup+0.062539 s]
/proc/loadavg: 0.80 0.95 0.95 3/77 30727
/proc/meminfo: memFree=1770312/2055920 swapFree=4157496/4192956
[pid=30727] ppid=30725 vsize=6172 CPUtime=0.05
/proc/30727/stat : 30727 (bsolo3.0.16) R 30725 30727 30667 0 -1 4194304 827 0 0 0 5 0 0 0 18 0 1 0 53175696 6320128 795 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 5162619 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30727/statm: 1543 795 366 324 0 429 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 6172

[startup+0.101542 s]
/proc/loadavg: 0.80 0.95 0.95 3/77 30727
/proc/meminfo: memFree=1770312/2055920 swapFree=4157496/4192956
[pid=30727] ppid=30725 vsize=7132 CPUtime=0.09
/proc/30727/stat : 30727 (bsolo3.0.16) R 30725 30727 30667 0 -1 4194304 1122 0 0 0 9 0 0 0 18 0 1 0 53175696 7303168 1090 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 5162619 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30727/statm: 1783 1090 420 324 0 669 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7132

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

[startup+0.201554 s]
/proc/loadavg: 0.80 0.95 0.95 3/77 30727
/proc/meminfo: memFree=1770312/2055920 swapFree=4157496/4192956
[pid=30727] ppid=30725 vsize=9288 CPUtime=0.19
/proc/30727/stat : 30727 (bsolo3.0.16) R 30725 30727 30667 0 -1 4194304 1896 0 0 0 19 0 0 0 18 0 1 0 53175696 9510912 1681 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30727/statm: 2322 1681 306 324 0 1391 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 9288

Child status: 0
Real time (s): 0.20578
CPU time (s): 0.203968
CPU user time (s): 0.19297
CPU system time (s): 0.010998
CPU usage (%): 99.1194
Max. virtual memory (cumulated for all children) (KiB): 9288

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node45 on Thu Apr 19 11:48:21 UTC 2007

IDJOB= 361491
IDBENCH= 1446
IDSOLVER= 163
FILE ID= node45/361491-1176983301

PBS_JOBID= 4630416

Free space on /tmp= 66442 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/web/uclid_pb_benchmarks/normalized-cache.inv10.ucl.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361491-1176983301/instance-361491-1176983301.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node45/watcher-361491-1176983301 -o ROOT/results/node45/solver-361491-1176983301 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361491-1176983301/instance-361491-1176983301.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  449faf6379a77b0035cc1474243ef90a

RANDOM SEED= 92363813

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node45.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.218
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.218
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:       1770912 kB
Buffers:         36704 kB
Cached:         182116 kB
SwapCached:      15576 kB
Active:         126240 kB
Inactive:       117008 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1770912 kB
SwapTotal:     4192956 kB
SwapFree:      4157496 kB
Dirty:            5320 kB
Writeback:           0 kB
Mapped:          31568 kB
Slab:            27332 kB
Committed_AS:  1167572 kB
PageTables:       1732 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= 66442 MiB

End job on node45 on Thu Apr 19 11:48:21 UTC 2007