Trace number 1077172

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
Mistral-prime 1.313SAT 0.622904 0.62445

DiagnosticValue
ASSIGNMENTS173
CHECKS360717

General information on the benchmark

Namecsp/wordsHerald/
normalized-crossword-m1-words-19-08.xml
MD5SUMd20c7bd53f46e51d24a0574180a1c33a
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.58591
Satisfiable
(Un)Satisfiability was proved
Number of variables295
Number of constraints3243
Maximum constraint arity24
Maximum domain size26
Number of constraints which are defined in extension130
Number of constraints which are defined in intension3113
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.00	c mistral-prime version 1.313
0.49/0.58	s SATISFIABLE
0.49/0.58	v 0 1 11 4 0 9 0 17 4 1 1 18 18 19 20 1 6 0 8 13 1 0 1 4 21 8 0 11 7 8 17 4 4 11 18 4 0 1 1 4 0 17 2 14 14 11 6 0 3 8 18 12 8 18 18 0 11 18 19 7 22 0 17 19 4 3 0 18 7 18 0 18 7 18 8 19 2 14 22 18 11 8 15 18 3 0 3 0 12 2 6 4 4 0 3 0 4 13 0 2 19 11 0 22 13 14 17 0 11 15 4 6 18 6 11 0 17 4 24 4 0 12 0 18 10 4 18 18 4 13 4 11 4 13 0 3 8 21 8 3 4 18 17 8 14 3 0 19 20 12 11 8 13 4 2 11 8 15 18 4 3 4 17 4 10 0 6 22 0 24 0 17 4 0 11 4 21 17 0 3 0 17 18 0 6 0 17 4 0 11 14 11 0 5 11 0 13 4 18 3 0 17 15 4 13 8 18 18 11 0 1 11 4 0 19 7 4 17 13 25 14 4 8 6 14 17 18 0 14 0 15 15 0 11 11 4 3 0 20 3 8 14 6 17 0 12 18 1 11 0 1 8 17 0 13 12 0 13 13 3 8 0 11 1 4 11 11 19 8 19 14 14 13 2 4 4 3 13 0 24 0 11 4 4 10 4 3 17 4 0 3 18 4 4 12
0.49/0.58	d CHECKS 360717
0.49/0.58	d ASSIGNMENTS 173

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-1077172-1215192009/watcher-1077172-1215192009 -o /tmp/evaluation-result-1077172-1215192009/solver-1077172-1215192009 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1077172-1215192009.xml 

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.03 2.00 4/82 6684
/proc/meminfo: memFree=1466808/2055920 swapFree=4179560/4192956
[pid=6684] ppid=6682 vsize=4580 CPUtime=0
/proc/6684/stat : 6684 (xsolve) R 6682 6684 3002 0 -1 4194304 390 0 0 0 0 0 0 0 20 0 1 0 1998175943 4689920 356 996147200 134512640 135237403 4294956240 18446744073709551615 4159705056 0 0 4096 0 0 0 0 17 1 0 0
/proc/6684/statm: 1145 362 310 176 0 49 0

[startup+0.036948 s]
/proc/loadavg: 2.00 2.03 2.00 4/82 6684
/proc/meminfo: memFree=1466808/2055920 swapFree=4179560/4192956
[pid=6684] ppid=6682 vsize=5244 CPUtime=0.03
/proc/6684/stat : 6684 (xsolve) R 6682 6684 3002 0 -1 4194304 595 0 0 0 3 0 0 0 20 0 1 0 1998175943 5369856 561 996147200 134512640 135237403 4294956240 18446744073709551615 3741307 0 0 4096 0 0 0 0 17 1 0 0
/proc/6684/statm: 1311 561 354 176 0 215 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5244

[startup+0.101955 s]
/proc/loadavg: 2.00 2.03 2.00 4/82 6684
/proc/meminfo: memFree=1466808/2055920 swapFree=4179560/4192956
[pid=6684] ppid=6682 vsize=6428 CPUtime=0.09
/proc/6684/stat : 6684 (xsolve) R 6682 6684 3002 0 -1 4194304 904 0 0 0 9 0 0 0 20 0 1 0 1998175943 6582272 870 996147200 134512640 135237403 4294956240 18446744073709551615 134941192 0 0 4096 0 0 0 0 17 1 0 0
/proc/6684/statm: 1607 870 372 176 0 511 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6428

[startup+0.301974 s]
/proc/loadavg: 2.00 2.03 2.00 4/82 6684
/proc/meminfo: memFree=1466808/2055920 swapFree=4179560/4192956
[pid=6684] ppid=6682 vsize=16320 CPUtime=0.29
/proc/6684/stat : 6684 (xsolve) R 6682 6684 3002 0 -1 4194304 3384 0 0 0 28 1 0 0 22 0 1 0 1998175943 16711680 3350 996147200 134512640 135237403 4294956240 18446744073709551615 3741307 0 0 4096 0 0 0 0 17 1 0 0
/proc/6684/statm: 4080 3352 396 176 0 2984 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 16320

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

[startup+0.501993 s]
/proc/loadavg: 2.00 2.03 2.00 4/82 6684
/proc/meminfo: memFree=1466808/2055920 swapFree=4179560/4192956
[pid=6684] ppid=6682 vsize=20008 CPUtime=0.49
/proc/6684/stat : 6684 (xsolve) R 6682 6684 3002 0 -1 4194304 4267 0 0 0 48 1 0 0 24 0 1 0 1998175943 20488192 4233 996147200 134512640 135237403 4294956240 18446744073709551615 134818584 0 0 4096 0 0 0 0 17 1 0 0
/proc/6684/statm: 5002 4233 409 176 0 3906 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 20008

[startup+0.602004 s]
/proc/loadavg: 2.00 2.03 2.00 4/82 6684
/proc/meminfo: memFree=1466808/2055920 swapFree=4179560/4192956
[pid=6684] ppid=6682 vsize=20084 CPUtime=0.59
/proc/6684/stat : 6684 (xsolve) R 6682 6684 3002 0 -1 4194304 4279 0 0 0 58 1 0 0 25 0 1 0 1998175943 20566016 4245 996147200 134512640 135237403 4294956240 18446744073709551615 3735550 0 0 4096 0 0 0 0 17 1 0 0
/proc/6684/statm: 5021 4245 416 176 0 3925 0
Current children cumulated CPU time (s) 0.59
Current children cumulated vsize (KiB) 20084

Child status: 0
Real time (s): 0.62445
CPU time (s): 0.622904
CPU user time (s): 0.600908
CPU system time (s): 0.021996
CPU usage (%): 99.7524
Max. virtual memory (cumulated for all children) (KiB): 20084

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

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node8 at 2008-07-04 19:20:09
IDJOB=1077172
IDBENCH=56650
IDSOLVER=358
FILE ID=node8/1077172-1215192009
PBS_JOBID= 7881560
Free space on /tmp= 66332 MiB

SOLVER NAME= Mistral-prime 1.313
BENCH NAME= CPAI08/csp/wordsHerald/normalized-crossword-m1-words-19-08.xml
COMMAND LINE= HOME/xsolve BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1077172-1215192009/watcher-1077172-1215192009 -o /tmp/evaluation-result-1077172-1215192009/solver-1077172-1215192009 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1077172-1215192009.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= d20c7bd53f46e51d24a0574180a1c33a
RANDOM SEED=1487328264

node8.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.222
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.222
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1467288 kB
Buffers:         54540 kB
Cached:         391508 kB
SwapCached:       6900 kB
Active:         241952 kB
Inactive:       287196 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1467288 kB
SwapTotal:     4192956 kB
SwapFree:      4179560 kB
Dirty:            2180 kB
Writeback:           0 kB
Mapped:          96792 kB
Slab:            44368 kB
Committed_AS:  4079044 kB
PageTables:       1952 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= 66332 MiB
End job on node8 at 2008-07-04 19:20:10