Trace number 2065805

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.887865 0.898963

General information on the benchmark

Namecsp/os-taillard-15/
normalized-os-taillard-15-105-6.xml
MD5SUMf829c18ce0e367481ee4e26c04de1f99
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.289955
Satisfiable
(Un)Satisfiability was proved
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size978
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3150
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c bpsolver version 6.29.2009
0.00/0.02	c converting(HOME/instance-2065805-1247339140)
0.58/0.60	c Converted in 298 ms
0.69/0.70	c solving(HOME/instance-2065805-1247339140,1800000)
0.69/0.70	c solving(HOME/instance-2065805-1247339140,1800000)
0.79/0.89	c (ff_inout)
0.79/0.89	s SATISFIABLE
0.79/0.89	v 582 186 872 728 384 0 216 504 341 93 469 700 446 250 182 702 367 658 825 469 569 784 259 260 77 728 55 853 0 156 417 658 635 793 755 452 0 93 276 465 560 182 592 424 682 182 582 864 540 636 0 683 891 263 353 452 414 669 82 700 414 58 473 46 186 341 90 743 247 781 593 663 81 174 0 626 354 912 263 704 0 65 196 156 526 463 55 122 672 376 0 158 526 250 784 637 339 449 566 685 81 154 424 593 737 191 737 454 171 245 663 90 891 178 288 257 559 0 637 379 384 669 84 593 546 263 46 454 516 262 122 0 174 737 840 350 260 93 407 144 691 379 479 781 262 752 860 0 593 203 762 528 276 662 473 788 376 601 0 379 872 78 152 417 247 192 90 82 270 635 531 754 665 679 451 0 91 354 851 795 346 540 407 99 566 672 714 64 775 903 0 938 479 192 708 93 815 685 0 158 733 517 642 913 182 350 279 864 565 451 0 812 775 642 531 691 196 859 840 469 99 592 737 288 379 
0.79/0.89	
0.79/0.89	c Time=280 ms Backtracks=0
0.79/0.89

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-2065805-1247339140/watcher-2065805-1247339140 -o /tmp/evaluation-result-2065805-1247339140/solver-2065805-1247339140 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2065805-1247339140 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: 1.92 2.00 2.08 4/74 15094
/proc/meminfo: memFree=1885312/2055920 swapFree=4192812/4192956
[pid=15094] ppid=15092 vsize=5356 CPUtime=0
/proc/15094/stat : 15094 (sh) R 15092 15094 14081 0 -1 4194304 265 0 0 0 0 0 0 0 20 0 1 0 20976625 5484544 232 996147200 4194304 4889804 548682068864 18446744073709551615 4488656 0 0 4100 65536 0 0 0 17 1 0 0
/proc/15094/statm: 1339 232 193 169 0 50 0

[startup+0.0465171 s]
/proc/loadavg: 1.92 2.00 2.08 4/74 15094
/proc/meminfo: memFree=1885312/2055920 swapFree=4192812/4192956
[pid=15094] ppid=15092 vsize=62208 CPUtime=0.03
/proc/15094/stat : 15094 (bprolog) R 15092 15094 14081 0 -1 4194304 1104 0 0 0 2 1 0 0 20 0 1 0 20976625 63700992 817 996147200 134512640 135105188 4294956096 18446744073709551615 134574314 0 0 4096 2 0 0 0 17 1 0 0
/proc/15094/statm: 15552 817 174 144 0 15036 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 62208

[startup+0.101522 s]
/proc/loadavg: 1.92 2.00 2.08 4/74 15094
/proc/meminfo: memFree=1885312/2055920 swapFree=4192812/4192956
[pid=15094] ppid=15092 vsize=62208 CPUtime=0.09
/proc/15094/stat : 15094 (bprolog) R 15092 15094 14081 0 -1 4194304 1124 0 0 0 4 5 0 0 20 0 1 0 20976625 63700992 837 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/15094/statm: 15552 837 177 144 0 15036 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 62208

[startup+0.301541 s]
/proc/loadavg: 1.92 2.00 2.08 4/74 15094
/proc/meminfo: memFree=1885312/2055920 swapFree=4192812/4192956
[pid=15094] ppid=15092 vsize=62208 CPUtime=0.29
/proc/15094/stat : 15094 (bprolog) R 15092 15094 14081 0 -1 4194304 1128 0 0 0 14 15 0 0 21 0 1 0 20976625 63700992 841 996147200 134512640 135105188 4294956096 18446744073709551615 8786115 0 0 4096 2 0 0 0 17 1 0 0
/proc/15094/statm: 15552 841 177 144 0 15036 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 62208

[startup+0.701592 s]
/proc/loadavg: 1.92 2.00 2.08 4/74 15094
/proc/meminfo: memFree=1885312/2055920 swapFree=4192812/4192956
[pid=15094] ppid=15092 vsize=70316 CPUtime=0.69
/proc/15094/stat : 15094 (bprolog) R 15092 15094 14081 0 -1 4194304 2049 0 0 0 40 29 0 0 25 0 1 0 20976625 72003584 1759 996147200 134512640 135105188 4294956096 18446744073709551615 135072360 0 0 4096 2 0 0 0 17 1 0 0
/proc/15094/statm: 17579 1759 181 144 0 17063 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 70316

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

[startup+0.802596 s]
/proc/loadavg: 1.92 2.00 2.08 4/74 15094
/proc/meminfo: memFree=1885312/2055920 swapFree=4192812/4192956
[pid=15094] ppid=15092 vsize=70316 CPUtime=0.79
/proc/15094/stat : 15094 (bprolog) R 15092 15094 14081 0 -1 4194304 2063 0 0 0 50 29 0 0 25 0 1 0 20976625 72003584 1773 996147200 134512640 135105188 4294956096 18446744073709551615 134670853 0 0 4096 2 0 0 0 17 1 0 0
/proc/15094/statm: 17579 1773 184 144 0 17063 0
Current children cumulated CPU time (s) 0.79
Current children cumulated vsize (KiB) 70316

Child status: 0
Real time (s): 0.898963
CPU time (s): 0.887865
CPU user time (s): 0.59191
CPU system time (s): 0.295955
CPU usage (%): 98.7655
Max. virtual memory (cumulated for all children) (KiB): 70316

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.59191
system time used= 0.295955
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2266
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= 267

runsolver used 0.004999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node70 at 2009-07-11 21:05:40
IDJOB=2065805
IDBENCH=54426
IDSOLVER=770
FILE ID=node70/2065805-1247339140
PBS_JOBID= 9506668
Free space on /tmp= 66412 MiB

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

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

MD5SUM BENCH= f829c18ce0e367481ee4e26c04de1f99
RANDOM SEED=1585951470

node70.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.214
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.214
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:       1885856 kB
Buffers:         14276 kB
Cached:          70112 kB
SwapCached:          0 kB
Active:          91292 kB
Inactive:        32672 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1885856 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1812 kB
Writeback:           0 kB
Mapped:          50820 kB
Slab:            31412 kB
Committed_AS:   163928 kB
PageTables:       1820 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= 66412 MiB
End job on node70 at 2009-07-11 21:05:41