Trace number 1089044

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
MDG-probe 2008-06-27UNSAT 0.331949 0.342624

DiagnosticValue
ASSIGNMENTS0
CHECKS3

General information on the benchmark

Namecsp/graphColoring/register/fpsol/
normalized-fpsol2-i-2-27.xml
MD5SUMbae4e74e8302566c5df94afffcbc4902
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.309952
Satisfiable
(Un)Satisfiability was proved
Number of variables451
Number of constraints8691
Maximum constraint arity2
Maximum domain size27
Number of constraints which are defined in extension0
Number of constraints which are defined in intension8691
Global constraints used (with number of constraints)

Solver Data (download as text)

0.19/0.21	c mistral-prime version 1.313
0.19/0.21	c 
0.19/0.21	c Parsing xml file
0.19/0.21	c          domains...............     0	(1 domains)
0.19/0.21	c          variables.............     0	(451 variables)
0.19/0.21	c          predicates............     0	(1 predicates)
0.19/0.21	c          constraints...........  0.29	(8691 constraints)
0.19/0.30	c Parsing time:   0.29
0.19/0.30	c
0.19/0.30	c Building model
0.29/0.31	c        73 AllDifferent constraints infered
0.29/0.32	c         0 constants
0.29/0.32	c         0 Boolean variables    (+0)
0.29/0.32	c        88 range variables      (+0)
0.29/0.32	c         0 domain (b) variables (+0)
0.29/0.32	c       363 domain (l) variables (+0)
0.29/0.32	c      8691 constraints          (+73)
0.29/0.32	c         0 values 
0.29/0.32	c Building time:   0.02
0.29/0.32	c
0.29/0.32	c Solving instance
0.29/0.32	c          heuristic = dom/wdeg
0.29/0.32	c          Randomized probing iteration = 100
0.29/0.32	c          probing limit = 30
0.29/0.32	c          level based weights = no
0.29/0.32	c          impact probing = no
0.29/0.32	c          restart policy = No restart
0.29/0.32	c          probing 2.2226e-18
0.29/0.32	c          Probing Nodes     0
0.29/0.32	c Solving time:      0
0.29/0.32	c
0.29/0.32	s UNSATISFIABLE
0.29/0.32	d CHECKS 3
0.29/0.32	d ASSIGNMENTS 0

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-1089044-1215261354/watcher-1089044-1215261354 -o /tmp/evaluation-result-1089044-1215261354/solver-1089044-1215261354 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1089044-1215261354.xml -v 1 -rs 1482753773 -probe 1 -ph 0 -heu dom/wdeg -res no 

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.93 1.98 1.99 4/81 16768
/proc/meminfo: memFree=1620368/2055920 swapFree=4192812/4192956
[pid=16768] ppid=16766 vsize=820 CPUtime=0
/proc/16768/stat : 16768 (xsolve) R 16766 16768 16397 0 -1 4194304 39 0 0 0 0 0 0 0 21 0 1 0 153520763 839680 25 996147200 134512640 135239859 4294956144 18446744073709551615 12591908 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/16768/statm: 205 25 19 177 0 3 0

[startup+0.0814759 s]
/proc/loadavg: 1.93 1.98 1.99 4/81 16768
/proc/meminfo: memFree=1620368/2055920 swapFree=4192812/4192956
[pid=16768] ppid=16766 vsize=5236 CPUtime=0.07
/proc/16768/stat : 16768 (xsolve) R 16766 16768 16397 0 -1 4194304 646 0 0 0 7 0 0 0 18 0 1 0 153520763 5361664 612 996147200 134512640 135239859 4294956144 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/16768/statm: 1309 612 391 177 0 212 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5236

[startup+0.102476 s]
/proc/loadavg: 1.93 1.98 1.99 4/81 16768
/proc/meminfo: memFree=1620368/2055920 swapFree=4192812/4192956
[pid=16768] ppid=16766 vsize=5364 CPUtime=0.09
/proc/16768/stat : 16768 (xsolve) R 16766 16768 16397 0 -1 4194304 684 0 0 0 9 0 0 0 18 0 1 0 153520763 5492736 650 996147200 134512640 135239859 4294956144 18446744073709551615 13902049 0 0 4096 0 0 0 0 17 1 0 0
/proc/16768/statm: 1341 650 391 177 0 244 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5364

[startup+0.301498 s]
/proc/loadavg: 1.93 1.98 1.99 4/81 16768
/proc/meminfo: memFree=1620368/2055920 swapFree=4192812/4192956
[pid=16768] ppid=16766 vsize=7056 CPUtime=0.29
/proc/16768/stat : 16768 (xsolve) R 16766 16768 16397 0 -1 4194304 1079 0 0 0 29 0 0 0 19 0 1 0 153520763 7225344 1045 996147200 134512640 135239859 4294956144 18446744073709551615 134909900 0 0 4096 0 0 0 0 17 1 0 0
/proc/16768/statm: 1764 1045 400 177 0 667 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 7056

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

Child status: 0
Real time (s): 0.342624
CPU time (s): 0.331949
CPU user time (s): 0.32695
CPU system time (s): 0.004999
CPU usage (%): 96.8844
Max. virtual memory (cumulated for all children) (KiB): 7056

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

runsolver used 0.004999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node28 at 2008-07-05 14:35:55
IDJOB=1089044
IDBENCH=58191
IDSOLVER=342
FILE ID=node28/1089044-1215261354
PBS_JOBID= 7882149
Free space on /tmp= 66504 MiB

SOLVER NAME= MDG-probe 2008-06-27
BENCH NAME= CPAI08/csp/graphColoring/register/fpsol/normalized-fpsol2-i-2-27.xml
COMMAND LINE= HOME/xsolve BENCHNAME -v 1 -rs RANDOMSEED -probe 1 -ph 0 -heu dom/wdeg -res no
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1089044-1215261354/watcher-1089044-1215261354 -o /tmp/evaluation-result-1089044-1215261354/solver-1089044-1215261354 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1089044-1215261354.xml -v 1 -rs 1482753773 -probe 1 -ph 0 -heu dom/wdeg -res no

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= bae4e74e8302566c5df94afffcbc4902
RANDOM SEED=1482753773

node28.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.231
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.231
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:       1620848 kB
Buffers:         31660 kB
Cached:         213004 kB
SwapCached:          0 kB
Active:         276264 kB
Inactive:       107892 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1620848 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2072 kB
Writeback:           0 kB
Mapped:         159656 kB
Slab:            35672 kB
Committed_AS:   576788 kB
PageTables:       2120 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= 66500 MiB
End job on node28 at 2008-07-05 14:35:55