Trace number 2065595

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.012997 0.0210739

DiagnosticValue
ASSIGNMENTS79
CHECKS9638
NODES79

General information on the benchmark

Namecsp/primes-30/
normalized-primes-30-20-2-5.xml
MD5SUM50f72344c481dde4742ead244b18f8da
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.012997
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints20
Maximum constraint arity7
Maximum domain size112
Number of constraints which are defined in extension0
Number of constraints which are defined in intension20
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c mistral version 1.545
0.00/0.02	s SATISFIABLE
0.00/0.02	v 43 101 2 113 2 64 2 57 13 2 113 2 5 113 113 113 2 46 113 2 38 113 113 2 113 113 113 53 92 3 93 83 2 37 113 2 2 113 113 19 37 113 5 113 113 2 2 113 64 2 77 109 113 35 113 2 39 113 107 2 2 113 89 2 63 2 113 2 96 60 113 113 15 113 12 2 3 2 26 113 2 4 2 113 72 107 2 2 64 2 104 64 11 55 113 73 79 113 2 113
0.00/0.02	d CHECKS 9638
0.00/0.02	d ASSIGNMENTS 79
0.00/0.02	d NODES 79 BACKTRACKS 10 FAILURES 10 RUNTIME 0 TOTALTIME 0 NODES/s 7900 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-2065595-1247338452/watcher-2065595-1247338452 -o /tmp/evaluation-result-2065595-1247338452/solver-2065595-1247338452 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2065595-1247338452.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.98 2.02 2.00 5/81 12314
/proc/meminfo: memFree=791360/2055920 swapFree=4192956/4192956
[pid=12314] ppid=12312 vsize=18576 CPUtime=0
/proc/12314/stat : 12314 (runsolver) R 12312 12314 11881 0 -1 4194368 15 0 0 0 0 0 0 0 19 0 1 0 20911584 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 238487661863 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/12314/statm: 4644 284 249 26 0 2626 0

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

Child status: 0
Real time (s): 0.0210739
CPU time (s): 0.012997
CPU user time (s): 0.008998
CPU system time (s): 0.003999
CPU usage (%): 61.6733
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.004999 second user time and 0.003999 second system time

The end

Launcher Data 

Begin job on node23 at 2009-07-11 20:54:12
IDJOB=2065595
IDBENCH=54378
IDSOLVER=769
FILE ID=node23/2065595-1247338452
PBS_JOBID= 9506761
Free space on /tmp= 66332 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/primes-30/normalized-primes-30-20-2-5.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2065595-1247338452/watcher-2065595-1247338452 -o /tmp/evaluation-result-2065595-1247338452/solver-2065595-1247338452 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2065595-1247338452.xml

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

MD5SUM BENCH= 50f72344c481dde4742ead244b18f8da
RANDOM SEED=1436538374

node23.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.277
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.277
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:        791840 kB
Buffers:         64416 kB
Cached:        1084308 kB
SwapCached:          0 kB
Active:         367780 kB
Inactive:       841576 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        791840 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            1184 kB
Writeback:           0 kB
Mapped:          81100 kB
Slab:            39780 kB
Committed_AS:   201108 kB
PageTables:       1932 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= 66332 MiB
End job on node23 at 2009-07-11 20:54:12