Trace number 2087574

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
bpsolver 09SAT 0.308952 0.317704

General information on the benchmark

Namecsp/os-taillard-10/
normalized-os-taillard-10-105-5.xml
MD5SUMfbb6506a8ee0a1011f326a71c66351cb
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.308952
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints900
Maximum constraint arity2
Maximum domain size565
Number of constraints which are defined in extension0
Number of constraints which are defined in intension900
Global constraints used (with number of constraints)

Solver Data 

0.00/0.03	c bpsolver version 6.29.2009
0.00/0.03	c converting(HOME/instance-2087574-1247386378)
0.00/0.20	c Converted in 82 ms
0.19/0.23	c solving(HOME/instance-2087574-1247386378,1800000)
0.19/0.23	c solving(HOME/instance-2087574-1247386378,1800000)
0.28/0.31	c (ff_inout)
0.28/0.31	s SATISFIABLE
0.28/0.31	v 99 378 448 393 0 127 302 265 526 183 474 280 80 349 0 448 541 136 403 495 327 509 302 136 82 49 479 0 357 237 343 194 265 0 459 332 497 99 427 235 459 357 99 0 479 437 400 90 193 280 190 274 164 347 497 144 428 75 0 522 333 235 350 75 127 541 0 299 448 194 500 82 433 264 127 0 368 348 238 170 106 144 49 495 0 403 343 238 92 368 0 393 531 349 265 170 428 479 80 193 
0.28/0.31	
0.28/0.31	c Time=105 ms Backtracks=554
0.28/0.31

Verifier Data 

OK

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2087574-1247386378/watcher-2087574-1247386378 -o /tmp/evaluation-result-2087574-1247386378/solver-2087574-1247386378 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2087574-1247386378 1800 

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): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.00 2.02 2.00 4/81 27196
/proc/meminfo: memFree=1858696/2055920 swapFree=4191900/4192956
[pid=27196] ppid=27194 vsize=7000 CPUtime=0
/proc/27196/stat : 27196 (bprolog) R 27194 27196 25230 0 -1 4194304 551 0 0 0 0 0 0 0 20 0 1 0 25704660 7168000 269 996147200 134512640 135105188 4294956096 18446744073709551615 134530912 0 0 4096 0 0 0 0 17 1 0 0
/proc/27196/statm: 1750 269 72 144 0 1234 0

[startup+0.21098 s]
/proc/loadavg: 2.00 2.02 2.00 4/81 27196
/proc/meminfo: memFree=1858696/2055920 swapFree=4191900/4192956
[pid=27196] ppid=27194 vsize=62204 CPUtime=0.19
/proc/27196/stat : 27196 (bprolog) R 27194 27196 25230 0 -1 4194304 1176 0 0 0 10 9 0 0 21 0 1 0 25704660 63696896 887 996147200 134512640 135105188 4294956096 18446744073709551615 7912397 0 0 4096 2 0 0 0 17 1 0 0
/proc/27196/statm: 15551 887 179 144 0 15035 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 62204

[startup+0.302991 s]
/proc/loadavg: 2.00 2.02 2.00 4/81 27196
/proc/meminfo: memFree=1858696/2055920 swapFree=4191900/4192956
[pid=27196] ppid=27194 vsize=80260 CPUtime=0.28
/proc/27196/stat : 27196 (bprolog) R 27194 27196 25230 0 -1 4194304 1553 0 0 0 19 9 0 0 23 0 2 0 25704660 82186240 1263 996147200 134512640 135105188 4294956096 18446744073709551615 134727730 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/27196/statm: 20065 1263 198 144 0 19549 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 80260

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

Child status: 0
Real time (s): 0.317704
CPU time (s): 0.308952
CPU user time (s): 0.206968
CPU system time (s): 0.101984
CPU usage (%): 97.2452
Max. virtual memory (cumulated for all children) (KiB): 80260

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

runsolver used 0.002999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node15 at 2009-07-12 10:12:58
IDJOB=2087574
IDBENCH=58743
IDSOLVER=770
FILE ID=node15/2087574-1247386378
PBS_JOBID= 9507175
Free space on /tmp= 66376 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/os-taillard-10/normalized-os-taillard-10-105-5.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2087574-1247386378/watcher-2087574-1247386378 -o /tmp/evaluation-result-2087574-1247386378/solver-2087574-1247386378 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2087574-1247386378 1800

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

MD5SUM BENCH= fbb6506a8ee0a1011f326a71c66351cb
RANDOM SEED=2034259895

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

/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.220
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.220
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:       1859176 kB
Buffers:         16600 kB
Cached:          68596 kB
SwapCached:        416 kB
Active:         114860 kB
Inactive:        28688 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1859176 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            1436 kB
Writeback:           0 kB
Mapped:          78108 kB
Slab:            38116 kB
Committed_AS:   254068 kB
PageTables:       2032 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= 66372 MiB
End job on node15 at 2009-07-12 10:12:59