Trace number 1053484

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.028995 0.034796

DiagnosticValue
ASSIGNMENTS132
CHECKS48777

General information on the benchmark

Namecsp/jobShop-ewddr2/
normalized-ewddr2-10-by-5-7.xml
MD5SUM0e1a4f341de97802aede74af3b9ff51d
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.024995
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size153
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.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	(49 domains)
0.00/0.03	c          variables.............     0	(50 variables)
0.00/0.03	c          predicates............     0	(2 predicates)
0.00/0.03	c          constraints...........  0.01	(265 constraints)
0.00/0.03	c Parsing time:   0.01
0.00/0.03	c
0.00/0.03	c Building model
0.00/0.03	c         0 constants
0.00/0.03	c         0 Boolean variables    (+450)
0.00/0.03	c        50 range variables      (+490)
0.00/0.03	c         0 domain (b) variables (+0)
0.00/0.03	c         0 domain (l) variables (+0)
0.00/0.03	c       265 constraints          (+940)
0.00/0.03	c         0 values 
0.00/0.03	c Building time:      0
0.00/0.03	c
0.00/0.03	c Solving instance
0.00/0.03	c          heuristic = dom/wdeg
0.00/0.03	c          Randomized probing iteration = 100
0.00/0.03	c          probing limit = 30
0.00/0.03	c          level based weights = no
0.00/0.03	c          impact probing = no
0.00/0.03	c          restart policy = No restart
0.00/0.03	c          probing .  0.01
0.00/0.03	c          Probing Nodes   132
0.00/0.03	c Solving time:   0.01
0.00/0.03	c
0.00/0.03	s SATISFIABLE
0.00/0.03	v 0 6 11 42 47 30 36 45 57 177 36 98 110 124 134 42 52 57 70 79 11 22 32 66 121 14 79 85 97 106 92 129 138 150 169 0 11 70 85 95 85 92 98 110 159 6 22 124 137 144
0.00/0.03	d CHECKS 48777
0.00/0.03	d ASSIGNMENTS 132

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-1053484-1215057515/watcher-1053484-1215057515 -o /tmp/evaluation-result-1053484-1215057515/solver-1053484-1215057515 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1053484-1215057515.xml -v 1 -rs 341353586 -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.12 2.05 2.01 4/80 19811
/proc/meminfo: memFree=1760616/2055920 swapFree=4180028/4192956
[pid=19811] ppid=19809 vsize=820 CPUtime=0
/proc/19811/stat : 19811 (xsolve) R 19809 19811 15861 0 -1 4194304 39 0 0 0 0 0 0 0 21 0 1 0 1984726842 839680 25 996147200 134512640 135239859 4294956144 18446744073709551615 10588964 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/19811/statm: 205 25 19 177 0 3 0

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

Child status: 0
Real time (s): 0.034796
CPU time (s): 0.028995
CPU user time (s): 0.023996
CPU system time (s): 0.004999
CPU usage (%): 83.3286
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.023996
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= 783
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= 1

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node4 at 2008-07-03 05:58:35
IDJOB=1053484
IDBENCH=56078
IDSOLVER=342
FILE ID=node4/1053484-1215057515
PBS_JOBID= 7875166
Free space on /tmp= 66544 MiB

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

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 0e1a4f341de97802aede74af3b9ff51d
RANDOM SEED=341353586

node4.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:       1761096 kB
Buffers:         11120 kB
Cached:         115684 kB
SwapCached:       7292 kB
Active:         164268 kB
Inactive:        70224 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1761096 kB
SwapTotal:     4192956 kB
SwapFree:      4180028 kB
Dirty:            1244 kB
Writeback:           0 kB
Mapped:         119960 kB
Slab:            45364 kB
Committed_AS:  3976168 kB
PageTables:       2120 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= 66544 MiB
End job on node4 at 2008-07-03 05:58:35