Trace number 2058083

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.722889 0.733819

General information on the benchmark

Namecsp/QWH-15/
normalized-qwh-15-106-2_ext.xml
MD5SUMe3b634eccb187062dda6e11401c04d1c
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.067988
Satisfiable
(Un)Satisfiability was proved
Number of variables225
Number of constraints2324
Maximum constraint arity2
Maximum domain size15
Number of constraints which are defined in extension2324
Number of constraints which are defined in intension0
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-2058083-1247320188)
0.20/0.23	c Converted in 84 ms
0.20/0.25	c solving(HOME/instance-2058083-1247320188,1800000)
0.20/0.25	c solving(HOME/instance-2058083-1247320188,1800000)
0.69/0.72	c (ffc_inout)
0.69/0.72	s SATISFIABLE
0.69/0.72	v 1 14 9 0 5 13 7 10 2 12 8 4 11 3 6 5 10 6 11 3 2 9 12 1 7 4 14 13 0 8 14 5 0 10 12 7 2 3 9 4 6 13 8 11 1 2 11 10 13 7 5 1 0 3 6 14 8 9 4 12 7 9 11 14 10 4 13 8 12 0 3 1 6 5 2 9 12 2 8 1 3 6 5 10 13 11 0 14 7 4 11 4 1 5 9 10 14 13 0 8 2 12 7 6 3 13 3 12 4 0 14 5 6 8 11 1 7 2 9 10 12 7 13 9 2 1 0 4 11 14 10 6 3 8 5 3 2 7 6 13 8 11 1 5 10 12 9 4 14 0 4 6 14 1 8 9 3 7 13 5 0 2 12 10 11 0 8 3 2 4 12 10 9 6 1 7 11 5 13 14 6 1 8 7 11 0 12 14 4 9 5 3 10 2 13 10 0 4 3 14 6 8 11 7 2 13 5 1 12 9 8 13 5 12 6 11 4 2 14 3 9 10 0 1 7 
0.69/0.73	
0.69/0.73	c Time=489 ms Backtracks=4412
0.69/0.73

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-2058083-1247320188/watcher-2058083-1247320188 -o /tmp/evaluation-result-2058083-1247320188/solver-2058083-1247320188 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2058083-1247320188 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.47 1.83 1.72 4/72 13319
/proc/meminfo: memFree=729832/2055920 swapFree=4192956/4192956
[pid=13319] ppid=13317 vsize=7000 CPUtime=0
/proc/13319/stat : 13319 (bprolog) R 13317 13319 12402 0 -1 4194304 386 0 0 0 0 0 0 0 20 0 1 0 19081612 7168000 104 996147200 134512640 135105188 4294956096 18446744073709551615 134530912 0 0 4096 0 0 0 0 17 1 0 0
/proc/13319/statm: 1750 104 72 144 0 1234 0

[startup+0.210196 s]
/proc/loadavg: 1.47 1.83 1.72 4/72 13319
/proc/meminfo: memFree=729832/2055920 swapFree=4192956/4192956
[pid=13319] ppid=13317 vsize=62208 CPUtime=0.2
/proc/13319/stat : 13319 (bprolog) R 13317 13319 12402 0 -1 4194304 1123 0 0 0 9 11 0 0 20 0 1 0 19081612 63700992 836 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/13319/statm: 15552 836 176 144 0 15036 0
Current children cumulated CPU time (s) 0.2
Current children cumulated vsize (KiB) 62208

[startup+0.302207 s]
/proc/loadavg: 1.47 1.83 1.72 4/72 13319
/proc/meminfo: memFree=729832/2055920 swapFree=4192956/4192956
[pid=13319] ppid=13317 vsize=72444 CPUtime=0.29
/proc/13319/stat : 13319 (bprolog) R 13317 13319 12402 0 -1 4194304 1595 0 0 0 16 13 0 0 22 0 2 0 19081612 74182656 1305 996147200 134512640 135105188 4294956096 18446744073709551615 134751466 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/13319/statm: 18111 1305 199 144 0 17595 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 72444

[startup+0.402213 s]
/proc/loadavg: 1.47 1.83 1.72 4/72 13319
/proc/meminfo: memFree=729832/2055920 swapFree=4192956/4192956
[pid=13319] ppid=13317 vsize=72444 CPUtime=0.39
/proc/13319/stat : 13319 (bprolog) R 13317 13319 12402 0 -1 4194304 1595 0 0 0 26 13 0 0 23 0 2 0 19081612 74182656 1305 996147200 134512640 135105188 4294956096 18446744073709551615 134718103 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/13319/statm: 18111 1305 199 144 0 17595 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 72444

[startup+0.702243 s]
/proc/loadavg: 1.47 1.83 1.72 4/72 13319
/proc/meminfo: memFree=729832/2055920 swapFree=4192956/4192956
[pid=13319] ppid=13317 vsize=72444 CPUtime=0.69
/proc/13319/stat : 13319 (bprolog) R 13317 13319 12402 0 -1 4194304 1595 0 0 0 56 13 0 0 25 0 2 0 19081612 74182656 1305 996147200 134512640 135105188 4294956096 18446744073709551615 134752060 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/13319/statm: 18111 1305 199 144 0 17595 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 72444

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

Child status: 0
Real time (s): 0.733819
CPU time (s): 0.722889
CPU user time (s): 0.58991
CPU system time (s): 0.132979
CPU usage (%): 98.5105
Max. virtual memory (cumulated for all children) (KiB): 72444

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

runsolver used 0.005999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node67 at 2009-07-11 15:49:49
IDJOB=2058083
IDBENCH=53443
IDSOLVER=770
FILE ID=node67/2058083-1247320188
PBS_JOBID= 9506497
Free space on /tmp= 66488 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/QWH-15/normalized-qwh-15-106-2_ext.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2058083-1247320188/watcher-2058083-1247320188 -o /tmp/evaluation-result-2058083-1247320188/solver-2058083-1247320188 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2058083-1247320188 1800

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

MD5SUM BENCH= e3b634eccb187062dda6e11401c04d1c
RANDOM SEED=718404756

node67.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.239
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.239
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:        730248 kB
Buffers:         43188 kB
Cached:        1192304 kB
SwapCached:          0 kB
Active:         120348 kB
Inactive:      1134736 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        730248 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            1720 kB
Writeback:           0 kB
Mapped:          31124 kB
Slab:            55908 kB
Committed_AS:   136292 kB
PageTables:       1776 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= 66488 MiB
End job on node67 at 2009-07-11 15:49:50