Trace number 1102866

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.154976 0.161712

DiagnosticValue
ASSIGNMENTS3438
CHECKS598000

General information on the benchmark

Namecsp/composed-75-1-80/
normalized-composed-75-1-80-1_ext.xml
MD5SUM48585bc76f56f4e7178f9d3982b8e6f7
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.048991
Satisfiable
(Un)Satisfiability was proved
Number of variables83
Number of constraints702
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension702
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.03	c mistral-prime version 1.313
0.00/0.03	c 
0.00/0.03	c Parsing xml file
0.00/0.03	c          domains...............     0	(1 domains)
0.00/0.03	c          variables.............     0	(83 variables)
0.00/0.03	c          relations.............  0.01	(702 relations)
0.00/0.03	c          constraints...........  0.02	(702 constraints)
0.00/0.04	c Parsing time:   0.03
0.00/0.04	c
0.00/0.04	c Building model
0.03/0.05	c         0 constants
0.03/0.05	c         0 Boolean variables    (+0)
0.03/0.05	c         0 range variables      (+0)
0.03/0.05	c         0 domain (b) variables (+0)
0.03/0.05	c        83 domain (l) variables (+0)
0.03/0.05	c       702 constraints          (+0)
0.03/0.05	c         0 values 
0.03/0.05	c Building time:   0.01
0.03/0.05	c
0.03/0.05	c Solving instance
0.03/0.05	c          heuristic = dom/wdeg
0.03/0.05	c          Randomized probing iteration = 100
0.03/0.05	c          probing limit = 30
0.03/0.05	c          level based weights = no
0.03/0.05	c          impact probing = no
0.03/0.05	c          restart policy = No restart
0.03/0.05	c          probing .......   0.1
0.08/0.15	c          Probing Nodes  3438
0.08/0.15	c Solving time:    0.1
0.08/0.15	c
0.08/0.15	s UNSATISFIABLE
0.08/0.15	d CHECKS 598000
0.08/0.15	d ASSIGNMENTS 3438

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-1102866-1215299837/watcher-1102866-1215299837 -o /tmp/evaluation-result-1102866-1215299837/solver-1102866-1215299837 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1102866-1215299837.xml -v 1 -rs 425097840 -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: 2.06 2.00 1.99 4/87 16287
/proc/meminfo: memFree=1660072/2055920 swapFree=4178936/4192956
[pid=16287] ppid=16285 vsize=18572 CPUtime=0
/proc/16287/stat : 16287 (runsolver) R 16285 16287 15427 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 2008954019 19017728 292 996147200 4194304 4296836 548682068336 18446744073709551615 251255123239 0 0 4096 24578 0 0 0 17 1 0 0
/proc/16287/statm: 4643 292 257 25 0 2626 0

[startup+0.04873 s]
/proc/loadavg: 2.06 2.00 1.99 4/87 16287
/proc/meminfo: memFree=1660072/2055920 swapFree=4178936/4192956
[pid=16287] ppid=16285 vsize=5648 CPUtime=0.03
/proc/16287/stat : 16287 (xsolve) R 16285 16287 15427 0 -1 4194304 765 0 0 0 3 0 0 0 20 0 1 0 2008954019 5783552 731 996147200 134512640 135239859 4294956144 18446744073709551615 4159157508 0 0 4096 0 0 0 0 17 1 0 0
/proc/16287/statm: 1412 731 404 177 0 315 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5648

[startup+0.101731 s]
/proc/loadavg: 2.06 2.00 1.99 4/87 16287
/proc/meminfo: memFree=1660072/2055920 swapFree=4178936/4192956
[pid=16287] ppid=16285 vsize=5780 CPUtime=0.08
/proc/16287/stat : 16287 (xsolve) R 16285 16287 15427 0 -1 4194304 806 0 0 0 8 0 0 0 20 0 1 0 2008954019 5918720 772 996147200 134512640 135239859 4294956144 18446744073709551615 134789675 0 0 4096 0 0 0 0 17 1 0 0
/proc/16287/statm: 1445 772 409 177 0 348 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5780

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

Child status: 0
Real time (s): 0.161712
CPU time (s): 0.154976
CPU user time (s): 0.148977
CPU system time (s): 0.005999
CPU usage (%): 95.8346
Max. virtual memory (cumulated for all children) (KiB): 5780

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.148977
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= 819
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= 32

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node64 at 2008-07-06 01:17:17
IDJOB=1102866
IDBENCH=60240
IDSOLVER=342
FILE ID=node64/1102866-1215299837
PBS_JOBID= 7882450
Free space on /tmp= 66392 MiB

SOLVER NAME= MDG-probe 2008-06-27
BENCH NAME= CPAI08/csp/composed-75-1-80/normalized-composed-75-1-80-1_ext.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-1102866-1215299837/watcher-1102866-1215299837 -o /tmp/evaluation-result-1102866-1215299837/solver-1102866-1215299837 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1102866-1215299837.xml -v 1 -rs 425097840 -probe 1 -ph 0 -heu dom/wdeg -res no

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 48585bc76f56f4e7178f9d3982b8e6f7
RANDOM SEED=425097840

node64.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.248
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.248
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:       1660552 kB
Buffers:         75864 kB
Cached:         229460 kB
SwapCached:       7408 kB
Active:         230384 kB
Inactive:       104084 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1660552 kB
SwapTotal:     4192956 kB
SwapFree:      4178936 kB
Dirty:            1656 kB
Writeback:           0 kB
Mapped:          46624 kB
Slab:            45128 kB
Committed_AS:  4190044 kB
PageTables:       2368 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= 66392 MiB
End job on node64 at 2008-07-06 01:17:17