Trace number 1087973

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-27SAT 0.05599 0.0634239

DiagnosticValue
ASSIGNMENTS446
CHECKS263949

General information on the benchmark

Namecsp/jobShop-enddr2/
normalized-enddr2-10-by-5-3.xml
MD5SUMa75bfbb25f97eb50028bb62c779078dd
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.028994
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size143
Number of constraints which are defined in extension0
Number of constraints which are defined in intension265
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.06	c mistral-prime version 1.313
0.00/0.06	c 
0.00/0.06	c Parsing xml file
0.00/0.06	c          domains...............     0	(46 domains)
0.00/0.06	c          variables.............     0	(50 variables)
0.00/0.06	c          predicates............     0	(2 predicates)
0.00/0.06	c          constraints...........  0.01	(265 constraints)
0.00/0.06	c Parsing time:   0.01
0.00/0.06	c
0.00/0.06	c Building model
0.00/0.06	c         0 constants
0.00/0.06	c         0 Boolean variables    (+450)
0.00/0.06	c        50 range variables      (+490)
0.00/0.06	c         0 domain (b) variables (+0)
0.00/0.06	c         0 domain (l) variables (+0)
0.00/0.06	c       265 constraints          (+940)
0.00/0.06	c         0 values 
0.00/0.06	c Building time:      0
0.00/0.06	c
0.00/0.06	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 .  0.04
0.00/0.06	c          Probing Nodes   446
0.00/0.06	c Solving time:   0.04
0.00/0.06	c
0.00/0.06	s SATISFIABLE
0.00/0.06	v 0 9 74 117 130 0 45 64 74 78 37 45 85 100 104 30 39 51 64 158 0 10 14 30 61 104 115 126 138 146 10 20 30 41 45 58 68 100 110 117 20 30 41 56 88 50 76 110 126 167
0.00/0.06	d CHECKS 263949
0.00/0.06	d ASSIGNMENTS 446

Verifier Data (download as text)

OK

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-1087973-1215245675/watcher-1087973-1215245675 -o /tmp/evaluation-result-1087973-1215245675/solver-1087973-1215245675 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1087973-1215245675.xml -v 1 -rs 1405210683 -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.97 2.03 2.00 3/73 6523
/proc/meminfo: memFree=1861832/2055920 swapFree=4179604/4192956
[pid=6523] ppid=6521 vsize=18572 CPUtime=0
/proc/6523/stat : 6523 (runsolver) R 6521 6523 5520 0 -1 4194368 15 0 0 0 0 0 0 0 23 0 1 0 2003518628 19017728 292 996147200 4194304 4296836 548682068336 18446744073709551615 228774702375 0 0 4096 24578 0 0 0 17 1 0 0
/proc/6523/statm: 4643 292 257 25 0 2626 0

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

Child status: 0
Real time (s): 0.0634239
CPU time (s): 0.05599
CPU user time (s): 0.053991
CPU system time (s): 0.001999
CPU usage (%): 88.279
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node74 at 2008-07-05 10:14:35
IDJOB=1087973
IDBENCH=58059
IDSOLVER=342
FILE ID=node74/1087973-1215245675
PBS_JOBID= 7882030
Free space on /tmp= 103236 MiB

SOLVER NAME= MDG-probe 2008-06-27
BENCH NAME= CPAI08/csp/jobShop-enddr2/normalized-enddr2-10-by-5-3.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-1087973-1215245675/watcher-1087973-1215245675 -o /tmp/evaluation-result-1087973-1215245675/solver-1087973-1215245675 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1087973-1215245675.xml -v 1 -rs 1405210683 -probe 1 -ph 0 -heu dom/wdeg -res no

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= a75bfbb25f97eb50028bb62c779078dd
RANDOM SEED=1405210683

node74.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:       1862312 kB
Buffers:          7220 kB
Cached:         100432 kB
SwapCached:       6520 kB
Active:         114980 kB
Inactive:        26344 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1862312 kB
SwapTotal:     4192956 kB
SwapFree:      4179604 kB
Dirty:            1136 kB
Writeback:           0 kB
Mapped:          41656 kB
Slab:            37356 kB
Committed_AS:  4157468 kB
PageTables:       1852 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= 103232 MiB
End job on node74 at 2008-07-05 10:14:35