Trace number 2084197

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.422934 0.440465

General information on the benchmark

Namecsp/rlfapGraphs/
normalized-graph2.xml
MD5SUM4b1880b220e0e2c53300bef9fd72ba3f
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.274957
Satisfiable
(Un)Satisfiability was proved
Number of variables400
Number of constraints2245
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2245
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-2084197-1247378890)
0.29/0.35	c Converted in 140 ms
0.39/0.40	c solving(HOME/instance-2084197-1247378890,1800000)
0.39/0.40	c solving(HOME/instance-2084197-1247378890,1800000)
0.39/0.42	c (ffc_inout)
0.39/0.42	s SATISFIABLE
0.39/0.42	v 114 352 100 338 324 86 100 338 254 16 366 128 72 310 16 254 128 366 44 282 16 254 254 16 268 30 58 296 254 16 296 58 394 156 338 100 142 380 282 44 72 310 16 254 72 310 324 86 72 310 156 394 380 142 282 44 58 296 30 268 72 310 86 324 30 268 30 268 44 282 142 380 366 128 324 86 16 254 352 114 268 30 310 72 114 352 30 268 666 428 30 268 352 114 72 310 16 254 338 100 296 58 156 394 352 114 30 268 72 310 30 268 324 86 72 310 282 44 142 380 72 310 324 86 44 282 310 72 142 380 16 254 296 58 380 142 366 128 282 44 30 268 338 100 268 30 44 282 366 128 324 86 16 254 142 380 694 456 16 254 324 86 380 142 310 72 268 30 72 310 30 268 268 30 296 58 296 58 142 380 72 310 652 414 268 30 100 338 142 380 58 296 666 428 310 72 254 16 254 16 394 156 30 268 16 254 352 114 338 100 296 58 142 380 254 16 254 16 44 282 324 86 44 282 338 100 380 142 394 156 282 44 58 296 58 296 338 100 282 44 72 310 30 268 72 310 142 380 100 338 296 58 100 338 142 380 268 30 380 142 324 86 142 380 142 380 254 16 72 310 442 680 114 352 72 310 268 30 30 268 428 666 268 30 142 380 254 16 44 282 380 142 380 142 30 268 142 380 142 380 44 282 16 254 58 296 142 380 380 142 142 380 142 380 86 324 142 380 86 324 100 338 44 282 254 16 428 666 268 30 44 282 114 352 324 86 86 324 380 142 282 44 652 414 58 296 30 268 142 380 142 380 652 414 114 352 652 414 324 86 16 254 282 44 72 310 254 16 366 128 16 254 114 352 324 86 86 324 394 156 268 30 254 16 268 30 268 30 254 16 338 100 254 16 268 30 72 310 128 366 
0.39/0.43	
0.39/0.43	c Time=65 ms Backtracks=0
0.39/0.43	

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-2084197-1247378890/watcher-2084197-1247378890 -o /tmp/evaluation-result-2084197-1247378890/solver-2084197-1247378890 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2084197-1247378890 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.47 2.38 2.34 4/80 24538
/proc/meminfo: memFree=1425448/2055920 swapFree=4192812/4192956
[pid=24538] ppid=24536 vsize=5356 CPUtime=0
/proc/24538/stat : 24538 (sh) R 24536 24538 22121 0 -1 4194304 263 0 0 0 0 0 0 0 20 0 1 0 24956535 5484544 230 996147200 4194304 4889804 548682068864 18446744073709551615 4381484 0 0 4100 65536 0 0 0 17 1 0 0
/proc/24538/statm: 1339 230 192 169 0 50 0

[startup+0.10515 s]
/proc/loadavg: 2.47 2.38 2.34 4/80 24538
/proc/meminfo: memFree=1425448/2055920 swapFree=4192812/4192956
[pid=24538] ppid=24536 vsize=62208 CPUtime=0.09
/proc/24538/stat : 24538 (bprolog) R 24536 24538 22121 0 -1 4194304 1144 0 0 0 5 4 0 0 20 0 1 0 24956535 63700992 857 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/24538/statm: 15552 857 176 144 0 15036 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 62208

[startup+0.201155 s]
/proc/loadavg: 2.47 2.38 2.34 4/80 24538
/proc/meminfo: memFree=1425448/2055920 swapFree=4192812/4192956
[pid=24538] ppid=24536 vsize=62208 CPUtime=0.19
/proc/24538/stat : 24538 (bprolog) R 24536 24538 22121 0 -1 4194304 1147 0 0 0 9 10 0 0 20 0 1 0 24956535 63700992 860 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/24538/statm: 15552 860 176 144 0 15036 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 62208

[startup+0.301163 s]
/proc/loadavg: 2.47 2.38 2.34 4/80 24538
/proc/meminfo: memFree=1425448/2055920 swapFree=4192812/4192956
[pid=24538] ppid=24536 vsize=62208 CPUtime=0.29
/proc/24538/stat : 24538 (bprolog) R 24536 24538 22121 0 -1 4194304 1149 0 0 0 13 16 0 0 21 0 1 0 24956535 63700992 862 996147200 134512640 135105188 4294956096 18446744073709551615 11002437 0 0 4096 2 0 0 0 17 1 0 0
/proc/24538/statm: 15552 862 176 144 0 15036 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 62208

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

[startup+0.401181 s]
/proc/loadavg: 2.47 2.38 2.34 4/80 24538
/proc/meminfo: memFree=1425448/2055920 swapFree=4192812/4192956
[pid=24538] ppid=24536 vsize=70176 CPUtime=0.39
/proc/24538/stat : 24538 (bprolog) R 24536 24538 22121 0 -1 4194304 1606 0 0 0 20 19 0 0 22 0 1 0 24956535 71860224 1316 996147200 134512640 135105188 4294956096 18446744073709551615 135073136 0 0 4096 2 0 0 0 17 1 0 0
/proc/24538/statm: 17544 1316 181 144 0 17028 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 70176

Child status: 0
Real time (s): 0.440465
CPU time (s): 0.422934
CPU user time (s): 0.224965
CPU system time (s): 0.197969
CPU usage (%): 96.0199
Max. virtual memory (cumulated for all children) (KiB): 70176

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.224965
system time used= 0.197969
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1841
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= 4
involuntary context switches= 440

runsolver used 0.007998 second user time and 0.013997 second system time

The end

Launcher Data

Begin job on node4 at 2009-07-12 08:08:10
IDJOB=2084197
IDBENCH=58053
IDSOLVER=770
FILE ID=node4/2084197-1247378890
PBS_JOBID= 9507116
Free space on /tmp= 66264 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/rlfapGraphs/normalized-graph2.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2084197-1247378890/watcher-2084197-1247378890 -o /tmp/evaluation-result-2084197-1247378890/solver-2084197-1247378890 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2084197-1247378890 1800

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

MD5SUM BENCH= 4b1880b220e0e2c53300bef9fd72ba3f
RANDOM SEED=326478344

node4.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.213
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.213
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:       1425928 kB
Buffers:          4496 kB
Cached:          47048 kB
SwapCached:          0 kB
Active:         566036 kB
Inactive:        14784 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1425928 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2708 kB
Writeback:           0 kB
Mapped:         547128 kB
Slab:            33384 kB
Committed_AS:   929632 kB
PageTables:       2900 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= 66264 MiB
End job on node4 at 2009-07-12 08:08:11