Trace number 2081898

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.444931 0.455183

General information on the benchmark

Namecsp/rlfapScens/
normalized-scen5.xml
MD5SUMd00375a0db2ca765457bfad019ed3136
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.333948
Satisfiable
(Un)Satisfiability was proved
Number of variables400
Number of constraints2598
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2598
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-2081898-1247374454)
0.29/0.37	c Converted in 146 ms
0.38/0.42	c solving(HOME/instance-2081898-1247374454,1800000)
0.38/0.42	c solving(HOME/instance-2081898-1247374454,1800000)
0.38/0.44	c (ffc_inout)
0.38/0.44	s SATISFIABLE
0.38/0.44	v 156 394 156 394 16 254 30 268 736 498 254 16 128 366 414 652 792 554 554 792 16 254 708 470 666 428 442 680 72 310 414 652 128 366 736 498 44 282 268 30 442 680 736 498 254 16 310 72 736 498 792 554 310 72 764 526 310 72 428 666 30 268 484 722 254 16 16 254 470 708 254 16 16 254 484 722 296 58 296 58 16 254 16 254 296 58 366 128 128 366 16 254 254 16 736 498 156 394 380 142 792 554 254 16 156 394 324 86 540 778 498 736 380 142 16 254 282 44 254 16 156 394 414 652 268 30 254 16 708 470 442 680 394 156 394 156 268 30 680 442 666 428 750 512 414 652 666 428 114 352 338 100 338 100 30 268 750 512 722 484 750 512 366 128 268 30 428 666 694 456 30 268 394 156 16 254 764 526 666 428 338 100 428 666 680 442 268 30 100 338 666 428 428 666 128 366 72 310 414 652 652 414 792 554 254 16 428 666 512 750 352 114 114 352 708 470 498 736 268 30 512 750 456 694 30 268 44 282 540 778 652 414 16 254 764 526 366 128 652 414 254 16 512 750 268 30 428 666 296 58 680 442 268 30 428 666 268 30 324 86 310 72 86 324 750 512 540 778 526 764 666 428 30 268 282 44 428 666 114 352 666 428 86 324 114 352 114 352 44 282 16 254 666 428 680 442 414 652 394 156 778 540 296 58 282 44 296 58 694 456 128 366 254 16 540 778 442 680 666 428 414 652 310 72 30 268 484 722 526 764 30 268 694 456 114 352 428 666 498 736 16 254 324 86 268 30 100 338 428 666 722 484 694 456 484 722 268 30 666 428 268 30 498 736 428 666 268 30 750 512 30 268 484 722 30 268 484 722 428 666 268 30 428 666 282 44 268 30 694 456 764 526 268 30 114 352 268 30 16 254 
0.38/0.45	
0.38/0.45	c Time=70 ms Backtracks=9
0.38/0.45

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-2081898-1247374454/watcher-2081898-1247374454 -o /tmp/evaluation-result-2081898-1247374454/solver-2081898-1247374454 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2081898-1247374454 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.42 2.09 2.03 4/82 24922
/proc/meminfo: memFree=1671544/2055920 swapFree=4192812/4192956
[pid=24922] ppid=24920 vsize=5356 CPUtime=0
/proc/24922/stat : 24922 (sh) R 24920 24922 19846 0 -1 4194304 270 0 0 0 0 0 0 0 20 0 1 0 24510505 5484544 237 996147200 4194304 4889804 548682068864 18446744073709551615 269807578407 0 0 4096 0 0 0 0 17 0 0 0
/proc/24922/statm: 1339 237 196 169 0 50 0

[startup+0.115713 s]
/proc/loadavg: 2.42 2.09 2.03 4/82 24922
/proc/meminfo: memFree=1671544/2055920 swapFree=4192812/4192956
[pid=24922] ppid=24920 vsize=62208 CPUtime=0.1
/proc/24922/stat : 24922 (bprolog) R 24920 24922 19846 0 -1 4194304 1143 0 0 0 4 6 0 0 21 0 1 0 24510505 63700992 856 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 0 0 0
/proc/24922/statm: 15552 856 176 144 0 15036 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 62208

[startup+0.201719 s]
/proc/loadavg: 2.42 2.09 2.03 4/82 24922
/proc/meminfo: memFree=1671544/2055920 swapFree=4192812/4192956
[pid=24922] ppid=24920 vsize=62208 CPUtime=0.19
/proc/24922/stat : 24922 (bprolog) R 24920 24922 19846 0 -1 4194304 1146 0 0 0 8 11 0 0 21 0 1 0 24510505 63700992 859 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 0 0 0
/proc/24922/statm: 15552 859 176 144 0 15036 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 62208

[startup+0.301727 s]
/proc/loadavg: 2.42 2.09 2.03 4/82 24922
/proc/meminfo: memFree=1671544/2055920 swapFree=4192812/4192956
[pid=24922] ppid=24920 vsize=62208 CPUtime=0.29
/proc/24922/stat : 24922 (bprolog) R 24920 24922 19846 0 -1 4194304 1150 0 0 0 13 16 0 0 23 0 1 0 24510505 63700992 863 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 0 0 0
/proc/24922/statm: 15552 863 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.401742 s]
/proc/loadavg: 2.42 2.09 2.03 4/82 24922
/proc/meminfo: memFree=1671544/2055920 swapFree=4192812/4192956
[pid=24922] ppid=24920 vsize=62204 CPUtime=0.38
/proc/24922/stat : 24922 (bprolog) R 24920 24922 19846 0 -1 4194304 1425 0 0 0 18 20 0 0 23 0 1 0 24510505 63696896 1136 996147200 134512640 135105188 4294956096 18446744073709551615 134563284 0 0 4096 2 0 0 0 17 0 0 0
/proc/24922/statm: 15551 1136 180 144 0 15035 0
Current children cumulated CPU time (s) 0.38
Current children cumulated vsize (KiB) 62204

Child status: 0
Real time (s): 0.455183
CPU time (s): 0.444931
CPU user time (s): 0.230964
CPU system time (s): 0.213967
CPU usage (%): 97.7477
Max. virtual memory (cumulated for all children) (KiB): 62208

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.230964
system time used= 0.213967
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1901
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= 3
involuntary context switches= 438

runsolver used 0.003999 second user time and 0.010998 second system time

The end

Launcher Data 

Begin job on node81 at 2009-07-12 06:54:14
IDJOB=2081898
IDBENCH=57507
IDSOLVER=770
FILE ID=node81/2081898-1247374454
PBS_JOBID= 9507093
Free space on /tmp= 126680 MiB

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

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

MD5SUM BENCH= d00375a0db2ca765457bfad019ed3136
RANDOM SEED=407769803

node81.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.233
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.233
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1672024 kB
Buffers:         59256 kB
Cached:         180172 kB
SwapCached:        136 kB
Active:         195724 kB
Inactive:       110760 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1672024 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2324 kB
Writeback:           0 kB
Mapped:          87328 kB
Slab:            62208 kB
Committed_AS:   261404 kB
PageTables:       2028 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 126680 MiB
End job on node81 at 2009-07-12 06:54:15