Trace number 2685311

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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/CT 0.1 fixedUNSAT 0.555915 0.556898

General information on the benchmark

Name/DEC-SMALLINT-LIN/oliveras/
j90/normalized-j9015_10-unsat.opb
MD5SUM3100d2bbd53ff9fb7d8d8fc9cec6894e
Bench CategoryDEC-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.219966
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables14196
Total number of constraints44553
Number of constraints which are clauses44245
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints308
Minimum length of a constraint1
Maximum length of a constraint90
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 66
Number of bits of the biggest number in a constraint 7
Biggest sum of numbers in a constraint 565
Number of bits of the biggest sum of numbers10
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.00/0.00	c PB/CT 0.1.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.49/0.55	c constraints 308/0 clauses 40425/0 units 2381
0.49/0.55	c vars 14196
0.49/0.55	c solved in presolving
0.49/0.55	s UNSATISFIABLE

Verifier Data 

ERROR: no interpretation found !

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2685311-1278440550/watcher-2685311-1278440550 -o /tmp/evaluation-result-2685311-1278440550/solver-2685311-1278440550 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2685311-1278440550.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): 2000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.02 1.06 1.00 3/106 18466
/proc/meminfo: memFree=1392424/2059040 swapFree=4192956/4192956
[pid=18466] ppid=18464 vsize=2136 CPUtime=0
/proc/18466/stat : 18466 (pbct) R 18464 18466 17370 0 -1 4202496 249 0 0 0 0 0 0 0 18 0 1 0 12268066 2187264 168 1992294400 134512640 136421960 4288612656 18446744073709551615 135650311 0 0 4096 0 0 0 0 17 0 0 0 0
/proc/18466/statm: 534 168 144 467 0 65 0

[startup+0.040999 s]
/proc/loadavg: 1.02 1.06 1.00 3/106 18466
/proc/meminfo: memFree=1392424/2059040 swapFree=4192956/4192956
[pid=18466] ppid=18464 vsize=2268 CPUtime=0.03
/proc/18466/stat : 18466 (pbct) R 18464 18466 17370 0 -1 4202496 285 0 0 0 3 0 0 0 18 0 1 0 12268066 2322432 204 1992294400 134512640 136421960 4288612656 18446744073709551615 134531154 0 0 4096 0 0 0 0 17 0 0 0 0
/proc/18466/statm: 567 204 144 467 0 98 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 2268

[startup+0.100998 s]
/proc/loadavg: 1.02 1.06 1.00 3/106 18466
/proc/meminfo: memFree=1392424/2059040 swapFree=4192956/4192956
[pid=18466] ppid=18464 vsize=2532 CPUtime=0.09
/proc/18466/stat : 18466 (pbct) R 18464 18466 17370 0 -1 4202496 351 0 0 0 9 0 0 0 18 0 1 0 12268066 2592768 270 1992294400 134512640 136421960 4288612656 18446744073709551615 134533544 0 0 4096 0 0 0 0 17 0 0 0 0
/proc/18466/statm: 633 270 144 467 0 164 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2532

[startup+0.300995 s]
/proc/loadavg: 1.02 1.06 1.00 3/106 18466
/proc/meminfo: memFree=1392424/2059040 swapFree=4192956/4192956
[pid=18466] ppid=18464 vsize=3452 CPUtime=0.29
/proc/18466/stat : 18466 (pbct) R 18464 18466 17370 0 -1 4202496 588 0 0 0 29 0 0 0 18 0 1 0 12268066 3534848 474 1992294400 134512640 136421960 4288612656 18446744073709551615 135372671 0 0 4096 0 0 0 0 17 0 0 0 0
/proc/18466/statm: 863 474 144 467 0 394 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 3452

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

[startup+0.500991 s]
/proc/loadavg: 1.02 1.06 1.00 3/106 18466
/proc/meminfo: memFree=1392424/2059040 swapFree=4192956/4192956
[pid=18466] ppid=18464 vsize=5960 CPUtime=0.49
/proc/18466/stat : 18466 (pbct) R 18464 18466 17370 0 -1 4202496 1208 0 0 0 49 0 0 0 18 0 1 0 12268066 6103040 1094 1992294400 134512640 136421960 4288612656 18446744073709551615 135829965 0 0 4096 0 0 0 0 17 0 0 0 0
/proc/18466/statm: 1490 1094 145 467 0 1021 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 5960

Child status: 0
Real time (s): 0.556898
CPU time (s): 0.555915
CPU user time (s): 0.549916
CPU system time (s): 0.005999
CPU usage (%): 99.8235
Max. virtual memory (cumulated for all children) (KiB): 5960

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

runsolver used 0.003999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node012 at 2010-07-06 20:22:31
IDJOB=2685311
IDBENCH=75334
IDSOLVER=1192
FILE ID=node012/2685311-1278440550
PBS_JOBID= 11233459
Free space on /tmp= 62484 MiB

SOLVER NAME= PB/CT 0.1 fixed
BENCH NAME= PB10/normalized-PB10/DEC-SMALLINT-LIN/oliveras/j90/normalized-j9015_10-unsat.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2685311-1278440550/watcher-2685311-1278440550 -o /tmp/evaluation-result-2685311-1278440550/solver-2685311-1278440550 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2685311-1278440550.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 3100d2bbd53ff9fb7d8d8fc9cec6894e
RANDOM SEED=1920456258

node012.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.248
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.49
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.248
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.46
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1392944 kB
Buffers:        110644 kB
Cached:         416544 kB
SwapCached:          0 kB
Active:         243944 kB
Inactive:       343524 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1392944 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            3296 kB
Writeback:           0 kB
AnonPages:       60264 kB
Mapped:          14480 kB
Slab:            56848 kB
PageTables:       4148 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181708 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62480 MiB
End job on node012 at 2010-07-06 20:22:31