Trace number 1090698

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
cpHydra k_10UNSAT 0.024995 0.0289271

DiagnosticValue
ASSIGNMENTS94
CHECKS3392

General information on the benchmark

Namecsp/graphColoring/insertion/full-insertion/
normalized-2-fullins-3-4.xml
MD5SUMe39e842e3e3021146201992a2d1cf419
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.013997
Satisfiable
(Un)Satisfiability was proved
Number of variables52
Number of constraints201
Maximum constraint arity2
Maximum domain size4
Number of constraints which are defined in extension0
Number of constraints which are defined in intension201
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.00	c cpHydra_k_10 version 0.0
0.00/0.02	c mistral-prime version 1.313
0.00/0.02	s UNSATISFIABLE
0.00/0.02	d CHECKS 3392
0.00/0.02	d ASSIGNMENTS 94

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-1090698-1215271871/watcher-1090698-1215271871 -o /tmp/evaluation-result-1090698-1215271871/solver-1090698-1215271871 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/cpHydra_k_10/hydra HOME/instance-1090698-1215271871.xml 

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: 2.15 2.03 2.01 4/73 3597
/proc/meminfo: memFree=1724312/2055920 swapFree=4177348/4192956
[pid=3597] ppid=3595 vsize=5360 CPUtime=0
/proc/3597/stat : 3597 (hydra) R 3595 3597 1492 0 -1 4194304 184 0 0 0 0 0 0 0 20 0 1 0 650107236 5488640 153 996147200 4194304 4889804 548682068816 18446744073709551615 243665739993 0 0 4096 0 0 0 0 17 1 0 0
/proc/3597/statm: 1340 153 126 169 0 51 0

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

Child status: 0
Real time (s): 0.0289271
CPU time (s): 0.024995
CPU user time (s): 0.014997
CPU system time (s): 0.009998
CPU usage (%): 86.4069
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node84 at 2008-07-05 17:31:11
IDJOB=1090698
IDBENCH=58465
IDSOLVER=365
FILE ID=node84/1090698-1215271871
PBS_JOBID= 7882060
Free space on /tmp= 66556 MiB

SOLVER NAME= cpHydra k_10
BENCH NAME= CPAI08/csp/graphColoring/insertion/full-insertion/normalized-2-fullins-3-4.xml
COMMAND LINE= HOME/cpHydra_k_10/hydra BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1090698-1215271871/watcher-1090698-1215271871 -o /tmp/evaluation-result-1090698-1215271871/solver-1090698-1215271871 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/cpHydra_k_10/hydra HOME/instance-1090698-1215271871.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= e39e842e3e3021146201992a2d1cf419
RANDOM SEED=882128999

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1724728 kB
Buffers:         40596 kB
Cached:         227792 kB
SwapCached:       9596 kB
Active:         175596 kB
Inactive:       108232 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1724728 kB
SwapTotal:     4192956 kB
SwapFree:      4177348 kB
Dirty:           24580 kB
Writeback:           0 kB
Mapped:          23264 kB
Slab:            32716 kB
Committed_AS:  1294608 kB
PageTables:       1736 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= 66532 MiB
End job on node84 at 2008-07-05 17:31:11