Trace number 2084934

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 09UNSAT 1.64775 1.66634

General information on the benchmark

Namecsp/graphColoring/register/mulsol/
normalized-mulsol-i-4-15.xml
MD5SUM27ed6ca75345b86c43e31d012b7fc2a8
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.144977
Satisfiable
(Un)Satisfiability was proved
Number of variables185
Number of constraints3946
Maximum constraint arity2
Maximum domain size15
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3946
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-2084934-1247380343)
0.38/0.44	c Converted in 189 ms
0.48/0.50	c solving(HOME/instance-2084934-1247380343,1800000)
0.48/0.50	c solving(HOME/instance-2084934-1247380343,1800000)
1.57/1.66	c before_labeling
1.57/1.66	s UNSATISFIABLE
1.57/1.66	
1.57/1.66	
1.57/1.66	c Time=1202 ms Backtracks=0
1.57/1.66

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2084934-1247380343/watcher-2084934-1247380343 -o /tmp/evaluation-result-2084934-1247380343/solver-2084934-1247380343 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2084934-1247380343 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.91 1.98 2.03 4/81 24874
/proc/meminfo: memFree=1876688/2055920 swapFree=4192812/4192956
[pid=24874] ppid=24872 vsize=18576 CPUtime=0
/proc/24874/stat : 24874 (runsolver) R 24872 24874 24810 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 25101791 19021824 284 996147200 4194304 4302564 548682068528 18446744073709551615 259913215271 0 0 4096 24578 0 0 0 17 1 0 0
/proc/24874/statm: 4644 284 249 26 0 2626 0

[startup+0.064507 s]
/proc/loadavg: 1.91 1.98 2.03 4/81 24874
/proc/meminfo: memFree=1876688/2055920 swapFree=4192812/4192956
[pid=24874] ppid=24872 vsize=62208 CPUtime=0.05
/proc/24874/stat : 24874 (bprolog) R 24872 24874 24810 0 -1 4194304 1118 0 0 0 3 2 0 0 20 0 1 0 25101791 63700992 831 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/24874/statm: 15552 831 177 144 0 15036 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 62208

[startup+0.101506 s]
/proc/loadavg: 1.91 1.98 2.03 4/81 24874
/proc/meminfo: memFree=1876688/2055920 swapFree=4192812/4192956
[pid=24874] ppid=24872 vsize=62208 CPUtime=0.08
/proc/24874/stat : 24874 (bprolog) R 24872 24874 24810 0 -1 4194304 1119 0 0 0 4 4 0 0 20 0 1 0 25101791 63700992 832 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/24874/statm: 15552 832 177 144 0 15036 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 62208

[startup+0.301525 s]
/proc/loadavg: 1.91 1.98 2.03 4/81 24874
/proc/meminfo: memFree=1876688/2055920 swapFree=4192812/4192956
[pid=24874] ppid=24872 vsize=62208 CPUtime=0.28
/proc/24874/stat : 24874 (bprolog) R 24872 24874 24810 0 -1 4194304 1125 0 0 0 13 15 0 0 21 0 1 0 25101791 63700992 838 996147200 134512640 135105188 4294956096 18446744073709551615 134672639 0 0 4096 2 0 0 0 17 1 0 0
/proc/24874/statm: 15552 838 177 144 0 15036 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 62208

[startup+0.701563 s]
/proc/loadavg: 1.91 1.98 2.03 4/81 24874
/proc/meminfo: memFree=1876688/2055920 swapFree=4192812/4192956
[pid=24874] ppid=24872 vsize=70184 CPUtime=0.68
/proc/24874/stat : 24874 (bprolog) R 24872 24874 24810 0 -1 4194304 1752 0 0 0 45 23 0 0 25 0 1 0 25101791 71868416 1462 996147200 134512640 135105188 4294956096 18446744073709551615 134684433 0 0 4096 2 0 0 0 17 1 0 0
/proc/24874/statm: 17546 1462 186 144 0 17030 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 70184

[startup+1.50164 s]
/proc/loadavg: 1.91 1.98 2.03 3/82 24875
/proc/meminfo: memFree=1871304/2055920 swapFree=4192812/4192956
[pid=24874] ppid=24872 vsize=70184 CPUtime=1.47
/proc/24874/stat : 24874 (bprolog) R 24872 24874 24810 0 -1 4194304 1752 0 0 0 124 23 0 0 25 0 1 0 25101791 71868416 1462 996147200 134512640 135105188 4294956096 18446744073709551615 134684276 0 0 4096 2 0 0 0 17 1 0 0
/proc/24874/statm: 17546 1462 186 144 0 17030 0
Current children cumulated CPU time (s) 1.47
Current children cumulated vsize (KiB) 70184

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

[startup+1.60165 s]
/proc/loadavg: 1.91 1.98 2.03 3/82 24875
/proc/meminfo: memFree=1871304/2055920 swapFree=4192812/4192956
[pid=24874] ppid=24872 vsize=70184 CPUtime=1.57
/proc/24874/stat : 24874 (bprolog) R 24872 24874 24810 0 -1 4194304 1780 0 0 0 134 23 0 0 25 0 1 0 25101791 71868416 1490 996147200 134512640 135105188 4294956096 18446744073709551615 134800690 0 0 4096 2 0 0 0 17 1 0 0
/proc/24874/statm: 17546 1490 186 144 0 17030 0
Current children cumulated CPU time (s) 1.57
Current children cumulated vsize (KiB) 70184

Child status: 0
Real time (s): 1.66634
CPU time (s): 1.64775
CPU user time (s): 1.40779
CPU system time (s): 0.239963
CPU usage (%): 98.8844
Max. virtual memory (cumulated for all children) (KiB): 70184

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

runsolver used 0.004999 second user time and 0.010998 second system time

The end

Launcher Data 

Begin job on node4 at 2009-07-12 08:32:23
IDJOB=2084934
IDBENCH=58233
IDSOLVER=770
FILE ID=node4/2084934-1247380343
PBS_JOBID= 9507253
Free space on /tmp= 66268 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/graphColoring/register/mulsol/normalized-mulsol-i-4-15.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2084934-1247380343/watcher-2084934-1247380343 -o /tmp/evaluation-result-2084934-1247380343/solver-2084934-1247380343 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2084934-1247380343 1800

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

MD5SUM BENCH= 27ed6ca75345b86c43e31d012b7fc2a8
RANDOM SEED=553943123

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:       1877168 kB
Buffers:          6676 kB
Cached:          58536 kB
SwapCached:          0 kB
Active:         108784 kB
Inactive:        21848 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1877168 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1884 kB
Writeback:           0 kB
Mapped:          85908 kB
Slab:            33140 kB
Committed_AS:   266820 kB
PageTables:       2052 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:32:25