Trace number 2062581

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.6519 0.66373

DiagnosticValue
ASSIGNMENTS106
CHECKS112809
NODES106

General information on the benchmark

Namecsp/QG6/
normalized-quasigroup6-9.xml
MD5SUM3a37583be3e48d0c415f0063d476413f
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.6519
Satisfiable
(Un)Satisfiability was proved
Number of variables403
Number of constraints323
Maximum constraint arity83
Maximum domain size73
Number of constraints which are defined in extension0
Number of constraints which are defined in intension144
Global constraints used (with number of constraints)alldifferent(18),element(161)

Solver Data

0.00/0.21	c mistral version 1.545
0.58/0.66	s SATISFIABLE
0.58/0.66	v 1 5 8 9 6 7 2 4 3 9 2 7 1 8 4 5 3 6 5 1 3 2 4 9 6 7 8 7 8 6 4 2 1 3 9 5 4 6 9 7 5 3 8 1 2 8 3 1 5 7 6 9 2 4 3 4 5 8 9 2 7 6 1 2 9 4 6 3 5 1 8 7 6 7 2 3 1 8 4 5 9 1 1 38 1 6 66 1 4 76 1 3 50 1 7 60 1 2 16 1 5 35 1 9 27 1 8 73 1 18 6 1 11 1 11 2 57 1 16 5 4 1 10 9 68 1 17 3 33 1 13 1 43 1 14 8 26 1 12 7 54 1 15 4 37 1 23 4 2 1 19 5 1 21 1 21 3 13 1 20 1 32 1 22 2 78 1 27 8 52 1 24 9 62 1 25 6 72 1 26 7 55 1 34 3 65 1 35 9 48 1 33 1 1 31 1 31 4 14 1 29 8 6 1 28 7 25 1 30 6 80 1 36 5 45 1 32 2 28 1 40 7 47 1 42 3 75 1 45 2 58 1 43 8 1 41 1 41 5 24 1 39 9 70 1 44 1 8 1 37 4 18 1 38 6 64 1 53 2 20 1 48 1 3 1 46 8 40 1 50 7 59 1 52 9 1 51 1 51 6 79 1 54 4 17 1 47 3 36 1 49 5 19 1 57 5 29 1 58 8 39 1 59 9 67 1 62 6 77 1 63 1 15 1 56 4 73 61 1 61 7 53 1 60 2 9 1 55 3 10 1 65 9 74 1 72 7 30 1 67 6 49 1 69 5 23 1 66 4 42 1 68 3 7 1 64 2 73 71 1 71 8 63 1 70 1 46 1 78 8 56 1 79 4 12 1 74 7 22 1 75 2 5 1 73 6 69 1 80 5 34 1 76 3 44 1 77 1 1 81 1 81 9
0.58/0.66	d CHECKS 112809
0.58/0.66	d ASSIGNMENTS 106
0.58/0.66	d NODES 106 BACKTRACKS 9 FAILURES 9 RUNTIME 0.57 TOTALTIME 0.64 NODES/s 185.965 CHECKS/s 197911

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-2062581-1247328902/watcher-2062581-1247328902 -o /tmp/evaluation-result-2062581-1247328902/solver-2062581-1247328902 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2062581-1247328902.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: 0.99 0.97 0.91 4/81 12317
/proc/meminfo: memFree=857448/2055920 swapFree=4192956/4192956
[pid=12317] ppid=12315 vsize=18576 CPUtime=0
/proc/12317/stat : 12317 (runsolver) R 12315 12317 10909 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 19954122 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 236437695783 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/12317/statm: 4644 284 249 26 0 2626 0

[startup+0.255666 s]
/proc/loadavg: 0.99 0.97 0.91 4/81 12317
/proc/meminfo: memFree=857448/2055920 swapFree=4192956/4192956
[pid=12317] ppid=12315 vsize=6252 CPUtime=0.24
/proc/12317/stat : 12317 (ld-linux.so.2) R 12315 12317 10909 0 -1 4194304 844 0 0 0 24 0 0 0 19 0 1 0 19954122 6402048 823 996147200 1448431616 1448550632 4294956208 18446744073709551615 134529712 0 0 4096 0 0 0 0 17 1 0 0
/proc/12317/statm: 1563 823 437 29 0 378 0
Current children cumulated CPU time (s) 0.24
Current children cumulated vsize (KiB) 6252

[startup+0.301669 s]
/proc/loadavg: 0.99 0.97 0.91 4/81 12317
/proc/meminfo: memFree=857448/2055920 swapFree=4192956/4192956
[pid=12317] ppid=12315 vsize=6252 CPUtime=0.29
/proc/12317/stat : 12317 (ld-linux.so.2) R 12315 12317 10909 0 -1 4194304 846 0 0 0 29 0 0 0 19 0 1 0 19954122 6402048 825 996147200 1448431616 1448550632 4294956208 18446744073709551615 134832516 0 0 4096 0 0 0 0 17 1 0 0
/proc/12317/statm: 1563 825 437 29 0 378 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 6252

[startup+0.401684 s]
/proc/loadavg: 0.99 0.97 0.91 4/81 12317
/proc/meminfo: memFree=857448/2055920 swapFree=4192956/4192956
[pid=12317] ppid=12315 vsize=6252 CPUtime=0.38
/proc/12317/stat : 12317 (ld-linux.so.2) R 12315 12317 10909 0 -1 4194304 852 0 0 0 38 0 0 0 20 0 1 0 19954122 6402048 831 996147200 1448431616 1448550632 4294956208 18446744073709551615 135269620 0 0 4096 0 0 0 0 17 1 0 0
/proc/12317/statm: 1563 831 438 29 0 378 0
Current children cumulated CPU time (s) 0.38
Current children cumulated vsize (KiB) 6252

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

[startup+0.501692 s]
/proc/loadavg: 0.99 0.97 0.91 4/81 12317
/proc/meminfo: memFree=857448/2055920 swapFree=4192956/4192956
[pid=12317] ppid=12315 vsize=6252 CPUtime=0.48
/proc/12317/stat : 12317 (ld-linux.so.2) R 12315 12317 10909 0 -1 4194304 852 0 0 0 48 0 0 0 21 0 1 0 19954122 6402048 831 996147200 1448431616 1448550632 4294956208 18446744073709551615 135269558 0 0 4096 0 0 0 0 17 1 0 0
/proc/12317/statm: 1563 831 438 29 0 378 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 6252

[startup+0.601704 s]
/proc/loadavg: 0.99 0.97 0.91 4/81 12317
/proc/meminfo: memFree=857448/2055920 swapFree=4192956/4192956
[pid=12317] ppid=12315 vsize=6252 CPUtime=0.58
/proc/12317/stat : 12317 (ld-linux.so.2) R 12315 12317 10909 0 -1 4194304 852 0 0 0 58 0 0 0 22 0 1 0 19954122 6402048 831 996147200 1448431616 1448550632 4294956208 18446744073709551615 134832445 0 0 4096 0 0 0 0 17 1 0 0
/proc/12317/statm: 1563 831 438 29 0 378 0
Current children cumulated CPU time (s) 0.58
Current children cumulated vsize (KiB) 6252

Child status: 0
Real time (s): 0.66373
CPU time (s): 0.6519
CPU user time (s): 0.646901
CPU system time (s): 0.004999
CPU usage (%): 98.2177
Max. virtual memory (cumulated for all children) (KiB): 6252

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.646901
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= 888
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= 14
involuntary context switches= 17

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data

Begin job on node62 at 2009-07-11 18:15:02
IDJOB=2062581
IDBENCH=53912
IDSOLVER=769
FILE ID=node62/2062581-1247328902
PBS_JOBID= 9506506
Free space on /tmp= 66324 MiB

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

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

MD5SUM BENCH= 3a37583be3e48d0c415f0063d476413f
RANDOM SEED=154506731

node62.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.220
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.220
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:        857928 kB
Buffers:         62284 kB
Cached:        1044484 kB
SwapCached:          0 kB
Active:         163580 kB
Inactive:       980944 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        857928 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            1552 kB
Writeback:           0 kB
Mapped:          58164 kB
Slab:            38292 kB
Committed_AS:   193220 kB
PageTables:       1984 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= 66324 MiB
End job on node62 at 2009-07-11 18:15:03