Trace number 1068133

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.437932 0.444779

DiagnosticValue
ASSIGNMENTS123
CHECKS245428

General information on the benchmark

Namecsp/lexHerald/
normalized-crossword-m1-lex-19-09.xml
MD5SUMb21238ab3357771cb5ca4999aeceaa15
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.437932
Satisfiable
(Un)Satisfiability was proved
Number of variables295
Number of constraints2699
Maximum constraint arity30
Maximum domain size26
Number of constraints which are defined in extension130
Number of constraints which are defined in intension2569
Global constraints used (with number of constraints)

Solver Data (download as text)

0.19/0.20	c mistral-prime version 1.313
0.39/0.41	s SATISFIABLE
0.39/0.41	v 3 0 7 11 3 4 4 17 20 18 3 0 0 13 13 0 0 11 0 8 0 23 11 4 19 14 0 3 15 8 14 13 13 4 17 14 17 0 18 0 19 17 20 4 18 19 0 13 0 2 10 13 14 22 11 4 3 6 4 0 1 11 4 17 0 4 4 12 8 19 14 0 17 0 11 18 14 17 0 8 18 8 13 3 20 1 19 22 8 11 8 6 7 19 4 17 13 18 19 1 0 19 1 4 0 3 15 11 4 0 0 2 19 6 0 3 12 0 15 11 4 24 0 15 17 7 4 13 8 18 7 18 20 18 8 4 0 2 2 17 0 11 0 13 0 0 2 17 8 3 1 17 0 4 0 11 11 24 13 18 13 0 17 11 2 0 12 1 17 8 2 8 8 8 4 2 14 11 4 5 0 3 8 3 0 3 14 6 4 21 0 3 4 2 14 11 0 1 13 4 17 4 13 4 17 21 0 19 4 22 14 4 0 17 17 4 0 17 13 0 8 11 18 4 13 20 17 6 4 0 5 19 18 20 1 18 19 8 19 20 19 8 14 13 0 17 24 13 0 18 0 0 11 14 4 14 19 8 18 13 2 0 0 3 17 8 15 19 0 11 4 17 0 2 4 4 12 8 11 24 4 0 17 4 1 4 13 19 7 0 13 17 4 13 4
0.39/0.41	d CHECKS 245428
0.39/0.41	d ASSIGNMENTS 123

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-1068133-1215152546/watcher-1068133-1215152546 -o /tmp/evaluation-result-1068133-1215152546/solver-1068133-1215152546 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1068133-1215152546.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: 1.92 1.98 1.99 4/81 6448
/proc/meminfo: memFree=1782856/2055920 swapFree=4180232/4192956
[pid=6448] ppid=6446 vsize=820 CPUtime=0
/proc/6448/stat : 6448 (xsolve) R 6446 6448 3357 0 -1 4194304 39 0 0 0 0 0 0 0 19 0 1 0 638191724 839680 25 996147200 134512640 135239859 4294956208 18446744073709551615 7893796 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/6448/statm: 205 25 19 177 0 3 0

[startup+0.0487259 s]
/proc/loadavg: 1.92 1.98 1.99 4/81 6448
/proc/meminfo: memFree=1782856/2055920 swapFree=4180232/4192956
[pid=6448] ppid=6446 vsize=5248 CPUtime=0.04
/proc/6448/stat : 6448 (xsolve) R 6446 6448 3357 0 -1 4194304 603 0 0 0 4 0 0 0 18 0 1 0 638191724 5373952 569 996147200 134512640 135239859 4294956208 18446744073709551615 4159729144 0 0 4096 0 0 0 0 17 1 0 0
/proc/6448/statm: 1312 569 350 177 0 215 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5248

[startup+0.101761 s]
/proc/loadavg: 1.92 1.98 1.99 4/81 6448
/proc/meminfo: memFree=1782856/2055920 swapFree=4180232/4192956
[pid=6448] ppid=6446 vsize=6284 CPUtime=0.09
/proc/6448/stat : 6448 (xsolve) R 6446 6448 3357 0 -1 4194304 876 0 0 0 9 0 0 0 18 0 1 0 638191724 6434816 842 996147200 134512640 135239859 4294956208 18446744073709551615 134706928 0 0 4096 0 0 0 0 17 1 0 0
/proc/6448/statm: 1571 842 369 177 0 474 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6284

[startup+0.301781 s]
/proc/loadavg: 1.92 1.98 1.99 4/81 6448
/proc/meminfo: memFree=1782856/2055920 swapFree=4180232/4192956
[pid=6448] ppid=6446 vsize=15940 CPUtime=0.29
/proc/6448/stat : 6448 (xsolve) R 6446 6448 3357 0 -1 4194304 3251 0 0 0 28 1 0 0 19 0 1 0 638191724 16322560 3217 996147200 134512640 135239859 4294956208 18446744073709551615 134789188 0 0 4096 0 0 0 0 17 1 0 0
/proc/6448/statm: 3985 3217 404 177 0 2888 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 15940

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

[startup+0.402801 s]
/proc/loadavg: 1.92 1.98 1.99 4/81 6448
/proc/meminfo: memFree=1782856/2055920 swapFree=4180232/4192956
[pid=6448] ppid=6446 vsize=16108 CPUtime=0.39
/proc/6448/stat : 6448 (xsolve) R 6446 6448 3357 0 -1 4194304 3278 0 0 0 38 1 0 0 20 0 1 0 638191724 16494592 3244 996147200 134512640 135239859 4294956208 18446744073709551615 134789231 0 0 4096 0 0 0 0 17 1 0 0
/proc/6448/statm: 4027 3244 404 177 0 2930 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 16108

Child status: 0
Real time (s): 0.444779
CPU time (s): 0.437932
CPU user time (s): 0.423935
CPU system time (s): 0.013997
CPU usage (%): 98.4606
Max. virtual memory (cumulated for all children) (KiB): 16108

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

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node5 at 2008-07-04 08:22:26
IDJOB=1068133
IDBENCH=55480
IDSOLVER=343
FILE ID=node5/1068133-1215152546
PBS_JOBID= 7877346
Free space on /tmp= 66560 MiB

SOLVER NAME= MDG-noprobe 2008-06-27
BENCH NAME= CPAI08/csp/lexHerald/normalized-crossword-m1-lex-19-09.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-1068133-1215152546/watcher-1068133-1215152546 -o /tmp/evaluation-result-1068133-1215152546/solver-1068133-1215152546 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1068133-1215152546.xml -heu dom/wdeg -res no 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= b21238ab3357771cb5ca4999aeceaa15
RANDOM SEED=2103743528

node5.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.279
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.279
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:       1783336 kB
Buffers:         38328 kB
Cached:         139432 kB
SwapCached:       6996 kB
Active:         139264 kB
Inactive:        75496 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1783336 kB
SwapTotal:     4192956 kB
SwapFree:      4180232 kB
Dirty:            1720 kB
Writeback:           0 kB
Mapped:          52756 kB
Slab:            42964 kB
Committed_AS:   955800 kB
PageTables:       1888 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= 66560 MiB
End job on node5 at 2008-07-04 08:22:26