Trace number 1089217

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 2008-06-27UNSAT 0.509922 0.51647

General information on the benchmark

Namecsp/graphColoring/register/mulsol/
normalized-mulsol-i-1-05.xml
MD5SUMceabdbc0d5189ac3439aa553c9a48b16
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.141977
Satisfiable
(Un)Satisfiability was proved
Number of variables197
Number of constraints3925
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3925
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.02	c bpsolver version 6.27.2008
0.00/0.02	c converting(HOME/instance-1089217-1215267304)
0.38/0.44	c Converted in 200 ms
0.38/0.44	c solving(HOME/instance-1089217-1215267304,1800000)
0.49/0.51	s UNSATISFIABLE
0.49/0.51	
0.49/0.51	
0.49/0.51	c Time=71 ms
0.49/0.51

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.2.5 (c) roussel@cril.univ-artois.fr

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1089217-1215267304/watcher-1089217-1215267304 -o /tmp/evaluation-result-1089217-1215267304/solver-1089217-1215267304 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1089217-1215267304 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): 2200 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.97 2.00 2.00 4/80 19447
/proc/meminfo: memFree=1689160/2055920 swapFree=4179828/4192956
[pid=19447] ppid=19445 vsize=4780 CPUtime=0
/proc/19447/stat : 19447 (bprolog) R 19445 19447 18713 0 -1 4194304 600 0 0 0 0 0 0 0 20 0 1 0 2005703848 4894720 318 996147200 134512640 134990860 4294956096 18446744073709551615 134530856 0 0 4096 0 0 0 0 17 1 0 0
/proc/19447/statm: 1195 318 72 116 0 706 0

[startup+0.139506 s]
/proc/loadavg: 1.97 2.00 2.00 4/80 19447
/proc/meminfo: memFree=1689160/2055920 swapFree=4179828/4192956
[pid=19447] ppid=19445 vsize=56080 CPUtime=0.12
/proc/19447/stat : 19447 (bprolog) R 19445 19447 18713 0 -1 4194304 1118 0 0 0 6 6 0 0 20 0 1 0 2005703848 57425920 831 996147200 134512640 134990860 4294956096 18446744073709551615 134634924 0 0 4096 2 0 0 0 17 1 0 0
/proc/19447/statm: 14020 831 178 116 0 13531 0
Current children cumulated CPU time (s) 0.12
Current children cumulated vsize (KiB) 56080

[startup+0.201515 s]
/proc/loadavg: 1.97 2.00 2.00 4/80 19447
/proc/meminfo: memFree=1689160/2055920 swapFree=4179828/4192956
[pid=19447] ppid=19445 vsize=56080 CPUtime=0.18
/proc/19447/stat : 19447 (bprolog) R 19445 19447 18713 0 -1 4194304 1120 0 0 0 9 9 0 0 20 0 1 0 2005703848 57425920 833 996147200 134512640 134990860 4294956096 18446744073709551615 134565721 0 0 4096 2 0 0 0 17 1 0 0
/proc/19447/statm: 14020 833 178 116 0 13531 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 56080

[startup+0.301532 s]
/proc/loadavg: 1.97 2.00 2.00 4/80 19447
/proc/meminfo: memFree=1689160/2055920 swapFree=4179828/4192956
[pid=19447] ppid=19445 vsize=56080 CPUtime=0.29
/proc/19447/stat : 19447 (bprolog) R 19445 19447 18713 0 -1 4194304 1123 0 0 0 15 14 0 0 21 0 1 0 2005703848 57425920 836 996147200 134512640 134990860 4294956096 18446744073709551615 134570562 0 0 4096 2 0 0 0 17 1 0 0
/proc/19447/statm: 14020 836 178 116 0 13531 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 56080

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

[startup+0.401547 s]
/proc/loadavg: 1.97 2.00 2.00 4/80 19447
/proc/meminfo: memFree=1689160/2055920 swapFree=4179828/4192956
[pid=19447] ppid=19445 vsize=56080 CPUtime=0.38
/proc/19447/stat : 19447 (bprolog) R 19445 19447 18713 0 -1 4194304 1126 0 0 0 19 19 0 0 22 0 1 0 2005703848 57425920 839 996147200 134512640 134990860 4294956096 18446744073709551615 8093756 0 0 4096 2 0 0 0 17 1 0 0
/proc/19447/statm: 14020 839 178 116 0 13531 0
Current children cumulated CPU time (s) 0.38
Current children cumulated vsize (KiB) 56080

[startup+0.501571 s]
/proc/loadavg: 1.97 2.00 2.00 4/80 19447
/proc/meminfo: memFree=1689160/2055920 swapFree=4179828/4192956
[pid=19447] ppid=19445 vsize=64056 CPUtime=0.49
/proc/19447/stat : 19447 (bprolog) R 19445 19447 18713 0 -1 4194304 1730 0 0 0 27 22 0 0 23 0 1 0 2005703848 65593344 1440 996147200 134512640 134990860 4294956096 18446744073709551615 134559363 0 0 4096 2 0 0 0 17 1 0 0
/proc/19447/statm: 16014 1440 184 116 0 15525 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 64056

Child status: 0
Real time (s): 0.51647
CPU time (s): 0.509922
CPU user time (s): 0.286956
CPU system time (s): 0.222966
CPU usage (%): 98.7322
Max. virtual memory (cumulated for all children) (KiB): 64056

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node34 at 2008-07-05 16:15:04
IDJOB=1089217
IDBENCH=58238
IDSOLVER=347
FILE ID=node34/1089217-1215267304
PBS_JOBID= 7882170
Free space on /tmp= 66504 MiB

SOLVER NAME= bpsolver 2008-06-27
BENCH NAME= CPAI08/csp/graphColoring/register/mulsol/normalized-mulsol-i-1-05.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1089217-1215267304/watcher-1089217-1215267304 -o /tmp/evaluation-result-1089217-1215267304/solver-1089217-1215267304 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1089217-1215267304 1800

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= ceabdbc0d5189ac3439aa553c9a48b16
RANDOM SEED=1212020301

node34.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.259
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.259
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:       1689640 kB
Buffers:         35800 kB
Cached:         199824 kB
SwapCached:       7272 kB
Active:         214680 kB
Inactive:       100204 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1689640 kB
SwapTotal:     4192956 kB
SwapFree:      4179828 kB
Dirty:            2148 kB
Writeback:           0 kB
Mapped:          95256 kB
Slab:            36464 kB
Committed_AS:  4359052 kB
PageTables:       1992 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= 66504 MiB
End job on node34 at 2008-07-05 16:15:04