Trace number 350186

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 NameAnswerObjective functionCPU timeWall clock time
bsolo 3.0.16? 0.003998 0.01254

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=440-sizeP=221-sizeQ=440-24744542-max.opb
MD5SUM33ae5939d1aa58a75a945a9faf3c230f
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmark
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables97901
Total number of constraints291721
Number of constraints which are clauses291720
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint97240
Number of terms in the objective function 221
Biggest coefficient in the objective function 1684996666696914987166688442938726917102321526408785780068975640576
Number of bits for the biggest coefficient in the objective function 221
Sum of the numbers in the objective function 3369993333393829974333376885877453834204643052817571560137951281151
Number of bits of the sum of numbers in the objective function 221
Biggest number in a constraint 2392032866531905486790942578809394338145620987608332988883503686824375178865503049616412016019962016447144819201720664620106359620960485637227891297994520232330261783830994590149049944504587400511488
Number of bits of the biggest number in a constraint 660
Biggest sum of numbers in a constraint 9568131466127621947163770315237577352582483950433331955534014747295056327361266164339146628902122677827758102544855227960862917226867090540237477036791666445280390686216944035782177068059758137897567
Number of bits of the biggest sum of numbers661
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.01	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.01	c Developed by Vasco Manquinho IST/UTL - INESC-ID
0.00/0.01	c type "bsolo -h" for help
0.00/0.01	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.01	c Time Limit set to 1800
0.00/0.01	c Memory Limit set to 1800 MB
0.00/0.01	c Instance file /tmp/evaluation/350186-1176802524/instance-350186-1176802524.opb
0.00/0.01	c File size is 18612537 bytes.
0.00/0.01	c Integer values too big to handle... 
0.00/0.01	c Parse Error 9
0.00/0.01	c Line: 7
0.00/0.01	c Unable to parse file /tmp/evaluation/350186-1176802524/instance-350186-1176802524.opb
0.00/0.01	c Caught signal: 1
0.00/0.01	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.01	c    0        0      0        0        0        0      0 -2147483648 0.00
0.00/0.01	s UNKNOWN
0.00/0.01	c Total time: 0 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/node17/watcher-350186-1176802524 -o ROOT/results/node17/solver-350186-1176802524 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350186-1176802524/instance-350186-1176802524.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: 1.08 1.02 1.01 3/77 14152
/proc/meminfo: memFree=1368568/2055920 swapFree=4074944/4192956
[pid=14152] ppid=14150 vsize=3780 CPUtime=0
/proc/14152/stat : 14152 (bsolo3.0.16) D 14150 14152 13306 0 -1 4194304 185 0 2 0 0 0 0 0 18 0 1 0 128169920 3870720 155 18446744073709551615 134512640 135841103 4294956640 18446744073709551615 4160395582 0 0 4096 0 18446744071563479169 0 0 17 1 0 0
/proc/14152/statm: 945 155 129 324 0 14 0

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

Child status: 1
Real time (s): 0.01254
CPU time (s): 0.003998
CPU user time (s): 0.001999
CPU system time (s): 0.001999
CPU usage (%): 31.882
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.001999
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 382
page faults= 3
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 15
involuntary context switches= 0

runsolver used 0.001999 second user time and 0.009998 second system time

The end

Launcher Data (download as text)

Begin job on node17 on Tue Apr 17 09:35:24 UTC 2007

IDJOB= 350186
IDBENCH= 3019
IDSOLVER= 163
FILE ID= node17/350186-1176802524

PBS_JOBID= 4586218

Free space on /tmp= 66483 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=440-sizeP=221-sizeQ=440-24744542-max.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350186-1176802524/instance-350186-1176802524.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-350186-1176802524 -o ROOT/results/node17/solver-350186-1176802524 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350186-1176802524/instance-350186-1176802524.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  33ae5939d1aa58a75a945a9faf3c230f

RANDOM SEED= 338395650

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node17.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.240
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.240
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:       1369104 kB
Buffers:         44092 kB
Cached:         383268 kB
SwapCached:      79308 kB
Active:         331496 kB
Inactive:       286324 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1369104 kB
SwapTotal:     4192956 kB
SwapFree:      4074944 kB
Dirty:           22564 kB
Writeback:           0 kB
Mapped:         139716 kB
Slab:            54228 kB
Committed_AS:  7144608 kB
PageTables:       2036 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= 66483 MiB

End job on node17 on Tue Apr 17 09:35:24 UTC 2007