Trace number 1055482

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-noprobe 2008-06-27SAT 0.082986 0.0909779

DiagnosticValue
ASSIGNMENTS92
CHECKS59818

General information on the benchmark

Namecsp/nengfa/
normalized-queens2.xml
MD5SUMfeda91e5b3c1ff49ee389ed427acc709
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.075987
Satisfiable
(Un)Satisfiability was proved
Number of variables310
Number of constraints211
Maximum constraint arity104
Maximum domain size104
Number of constraints which are defined in extension0
Number of constraints which are defined in intension208
Global constraints used (with number of constraints)alldifferent(3)

Solver Data (download as text)

0.00/0.09	c mistral-prime version 1.313
0.00/0.09	s SATISFIABLE
0.00/0.09	v 1 4 3 2 7 5 3 59 56 53 66 62 58 9 4 -1 63 57 51 14 7 0 71 63 55 70 61 52 91 81 71 65 54 43 18 6 -6 89 76 63 96 82 68 80 65 50 24 8 -8 107 90 73 95 77 59 72 53 34 88 68 48 104 83 62 31 9 -13 87 64 41 76 52 28 68 43 18 75 49 23 98 71 44 116 88 60 39 10 -19 77 47 17 111 80 49 83 51 19 93 60 27 92 58 24 90 55 20 54 18 -18 48 11 -26 84 46 8 118 79 40 109 69 29 79 38 -3 114 72 30 82 39 -4 73 29 -15 62 17 -28 58 12 -34 132 85 38 85 37 -11 123 74 25 136 86 36 135 84 33 139 87 35 151 98 45 113 59 5 74 19 -36 69 13 -43 161 104 47 131 73 15 101 42 -17 157 97 37 164 103 42 163 101 39 138 75 12 159 95 31 97 32 -33 86 20 -46 81 14 -53 168 100 32 160 91 22 166 96 26 112 41 -30 165 93 21 117 44 -29 152 78 4 103 28 -47 143 67 -9 147 70 -7 99 21 -57 94 15 -64 146 66 -14 173 92 11 122 40 -42 172 89 6 106 22 -62 184 99 14 188 102 16 181 94 7 124 36 -52 134 45 -44 115 25 -65 141 50 -41 108 16 -76 119 26 -67 127 33 -61 130 35 -60 144 48 -48 120 23 -74 128 30 -68 126 27 -72 102 2 -98 125 24 -77 133 31 -71 137 34 -69
0.00/0.09	d CHECKS 59818
0.00/0.09	d ASSIGNMENTS 92

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-1055482-1215059678/watcher-1055482-1215059678 -o /tmp/evaluation-result-1055482-1215059678/solver-1055482-1215059678 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1055482-1215059678.xml -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.00 2.04 2.01 4/72 31072
/proc/meminfo: memFree=1785720/2055920 swapFree=4180076/4192956
[pid=31072] ppid=31070 vsize=18572 CPUtime=0
/proc/31072/stat : 31072 (runsolver) R 31070 31072 27392 0 -1 4194368 15 0 0 0 0 0 0 0 21 0 1 0 1984941857 19017728 292 996147200 4194304 4296836 548682068448 18446744073709551615 225612197159 0 0 4096 24578 0 0 0 17 1 0 0
/proc/31072/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.0909779
CPU time (s): 0.082986
CPU user time (s): 0.072988
CPU system time (s): 0.009998
CPU usage (%): 91.2155
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.072988
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= 1615
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.004999 second system time

The end

Launcher Data (download as text)

Begin job on node31 at 2008-07-03 06:34:38
IDJOB=1055482
IDBENCH=56822
IDSOLVER=343
FILE ID=node31/1055482-1215059678
PBS_JOBID= 7875111
Free space on /tmp= 66544 MiB

SOLVER NAME= MDG-noprobe 2008-06-27
BENCH NAME= CPAI08/csp/nengfa/normalized-queens2.xml
COMMAND LINE= HOME/xsolve BENCHNAME -heu dom/wdeg -res no 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1055482-1215059678/watcher-1055482-1215059678 -o /tmp/evaluation-result-1055482-1215059678/solver-1055482-1215059678 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1055482-1215059678.xml -heu dom/wdeg -res no 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= feda91e5b3c1ff49ee389ed427acc709
RANDOM SEED=1232181232

node31.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.232
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.232
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:       1786200 kB
Buffers:         27496 kB
Cached:         139932 kB
SwapCached:       5972 kB
Active:         147912 kB
Inactive:        63548 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1786200 kB
SwapTotal:     4192956 kB
SwapFree:      4180076 kB
Dirty:            1008 kB
Writeback:           0 kB
Mapped:          51884 kB
Slab:            42936 kB
Committed_AS:  3049932 kB
PageTables:       2176 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= 66544 MiB
End job on node31 at 2008-07-03 06:34:38