Trace number 1057607

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.06299 0.0693301

DiagnosticValue
ASSIGNMENTS0
CHECKS3399

General information on the benchmark

Namecsp/radar-9-28-4-2/
normalized-radar-9-28-4-2-43.xml
MD5SUM80f9deb82500e1b4197867c0c639f6ff
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.05899
Satisfiable
(Un)Satisfiability was proved
Number of variables168
Number of constraints81
Maximum constraint arity22
Maximum domain size5
Number of constraints which are defined in extension0
Number of constraints which are defined in intension81
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.04	c mistral-prime version 1.313
0.00/0.04	c 
0.00/0.04	c Parsing xml file
0.00/0.04	c          domains...............     0	(1 domains)
0.00/0.04	c          variables.............     0	(168 variables)
0.00/0.04	c          predicates............  0.03	(81 predicates)
0.00/0.04	c          constraints...........  0.01	(81 constraints)
0.00/0.05	c Parsing time:   0.04
0.00/0.05	c
0.00/0.05	c Building model
0.00/0.05	c         0 constants
0.00/0.05	c         0 Boolean variables    (+1016)
0.00/0.05	c       168 range variables      (+854)
0.00/0.05	c         0 domain (b) variables (+0)
0.00/0.05	c         0 domain (l) variables (+0)
0.00/0.05	c         0 constraints          (+1951)
0.00/0.05	c         0 values 
0.00/0.05	c Building time:   0.01
0.00/0.05	c
0.00/0.05	c Solving instance
0.00/0.06	c          heuristic = dom/wdeg
0.00/0.06	c          Randomized probing iteration = 100
0.00/0.06	c          probing limit = 30
0.00/0.06	c          level based weights = no
0.00/0.06	c          impact probing = no
0.00/0.06	c          restart policy = No restart
0.00/0.06	c          probing -2.7749e-18
0.00/0.06	c          Probing Nodes     0
0.00/0.06	c Solving time:      0
0.00/0.06	c
0.00/0.06	s UNSATISFIABLE
0.00/0.06	d CHECKS 3399
0.00/0.06	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-1057607-1215111294/watcher-1057607-1215111294 -o /tmp/evaluation-result-1057607-1215111294/solver-1057607-1215111294 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1057607-1215111294.xml -v 1 -rs 1353059883 -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.80 1.89 1.89 4/80 11842
/proc/meminfo: memFree=1467120/2055920 swapFree=4180396/4192956
[pid=11842] ppid=11840 vsize=0 CPUtime=0.05
/proc/11842/stat : 11842 (xsolve) Z 11840 11842 11402 0 -1 4194316 1119 0 0 0 5 0 0 0 18 0 1 0 1990102288 0 0 996147200 0 0 0 0 0 0 0 4096 0 18446744071563351923 0 0 17 1 0 0
/proc/11842/statm: 0 0 0 0 0 0 0

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

Child status: 0
Real time (s): 0.0693301
CPU time (s): 0.06299
CPU user time (s): 0.056991
CPU system time (s): 0.005999
CPU usage (%): 90.8553
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node44 at 2008-07-03 20:54:54
IDJOB=1057607
IDBENCH=54055
IDSOLVER=342
FILE ID=node44/1057607-1215111294
PBS_JOBID= 7877118
Free space on /tmp= 66524 MiB

SOLVER NAME= MDG-probe 2008-06-27
BENCH NAME= CPAI08/csp/radar-9-28-4-2/normalized-radar-9-28-4-2-43.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-1057607-1215111294/watcher-1057607-1215111294 -o /tmp/evaluation-result-1057607-1215111294/solver-1057607-1215111294 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1057607-1215111294.xml -v 1 -rs 1353059883 -probe 1 -ph 0 -heu dom/wdeg -res no

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 80f9deb82500e1b4197867c0c639f6ff
RANDOM SEED=1353059883

node44.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:       1467600 kB
Buffers:         60112 kB
Cached:         378628 kB
SwapCached:       6524 kB
Active:         273876 kB
Inactive:       239060 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1467600 kB
SwapTotal:     4192956 kB
SwapFree:      4180396 kB
Dirty:            1148 kB
Writeback:           0 kB
Mapped:          87844 kB
Slab:            60416 kB
Committed_AS:  4242584 kB
PageTables:       1936 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= 66524 MiB
End job on node44 at 2008-07-03 20:54:54