Trace number 2061228

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 1.545SAT 0.015996 0.0169759

DiagnosticValue
ASSIGNMENTS4
CHECKS2096
NODES4

General information on the benchmark

Namecsp/QG5/
normalized-quasigroup5-7.xml
MD5SUMb004dea6dc914c57ae65ef52d6e2252d
Bench CategoryAlldiff+Elt+WSum (alldiff,element,weightedsum)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.015996
Satisfiable
(Un)Satisfiability was proved
Number of variables133
Number of constraints98
Maximum constraint arity9
Maximum domain size7
Number of constraints which are defined in extension0
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)alldifferent(14),element(84)

Solver Data 

0.00/0.00	c mistral version 1.545
0.00/0.01	s SATISFIABLE
0.00/0.01	v 1 4 6 7 3 5 2 4 2 1 3 6 7 5 6 1 3 5 7 2 4 7 3 5 4 2 1 6 3 6 7 2 5 4 1 5 7 2 1 4 6 3 2 5 4 6 1 3 7 7 2 5 3 2 4 6 5 3 6 4 7 3 1 4 3 1 4 7 5 5 6 6 7 2 1 6 2 7 4 4 5 1 6 5 7 6 1 5 2 2 3 3 5 7 6 1 7 7 1 4 2 1 3 6 4 2 6 3 7 4 1 3 2 7 3 5 4 1 5 2 7 5 1 1 2 6 3 3 4 2 5 4 6
0.00/0.01	d CHECKS 2096
0.00/0.01	d ASSIGNMENTS 4
0.00/0.01	d NODES 4 BACKTRACKS 0 FAILURES 0 RUNTIME 0 TOTALTIME 0 NODES/s 400 CHECKS/s 0

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2061228-1247326840/watcher-2061228-1247326840 -o /tmp/evaluation-result-2061228-1247326840/solver-2061228-1247326840 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2061228-1247326840.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): 2000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.86 1.91 1.87 3/73 13450
/proc/meminfo: memFree=1030896/2055920 swapFree=4192948/4192956
[pid=13450] ppid=13448 vsize=4804 CPUtime=0
/proc/13450/stat : 13450 (ld-linux.so.2) R 13448 13450 11369 0 -1 4194304 254 0 0 0 0 0 0 0 18 0 1 0 19748797 4919296 233 996147200 1448431616 1448550632 4294956208 18446744073709551615 4159123440 0 0 4096 0 0 0 0 17 0 0 0
/proc/13450/statm: 1201 238 206 29 0 16 0

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

Child status: 0
Real time (s): 0.0169759
CPU time (s): 0.015996
CPU user time (s): 0.008998
CPU system time (s): 0.006998
CPU usage (%): 94.2276
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.008998
system time used= 0.006998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 590
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= 15
involuntary context switches= 6

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node54 at 2009-07-11 17:40:40
IDJOB=2061228
IDBENCH=53789
IDSOLVER=769
FILE ID=node54/2061228-1247326840
PBS_JOBID= 9506521
Free space on /tmp= 66412 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/QG5/normalized-quasigroup5-7.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2061228-1247326840/watcher-2061228-1247326840 -o /tmp/evaluation-result-2061228-1247326840/solver-2061228-1247326840 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2061228-1247326840.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= b004dea6dc914c57ae65ef52d6e2252d
RANDOM SEED=276394361

node54.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:       1031312 kB
Buffers:         46488 kB
Cached:         889048 kB
SwapCached:          8 kB
Active:         113632 kB
Inactive:       858956 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1031312 kB
SwapTotal:     4192956 kB
SwapFree:      4192948 kB
Dirty:            1576 kB
Writeback:           0 kB
Mapped:          48684 kB
Slab:            37292 kB
Committed_AS:   159148 kB
PageTables:       1724 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= 66412 MiB
End job on node54 at 2009-07-11 17:40:40