Trace number 2070743

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.009997 0.074294

DiagnosticValue
ASSIGNMENTS69
CHECKS1892
NODES69

General information on the benchmark

Namecsp/primes-20/
normalized-primes-20-20-2-1.xml
MD5SUMb233b8519d2f71c6ff7ca4b677055e01
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.009997
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints20
Maximum constraint arity3
Maximum domain size70
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.06	c mistral version 1.545
0.00/0.07	s SATISFIABLE
0.00/0.07	v 71 17 2 71 43 53 5 41 29 3 71 71 71 62 2 2 71 17 2 59 71 23 71 2 2 31 2 7 19 53 29 5 2 2 2 2 43 59 2 71 29 43 3 71 71 71 67 71 2 71 2 2 2 11 71 71 5 71 59 2 2 71 71 71 71 71 2 2 43 2 71 53 71 2 2 71 71 71 2 31 2 71 2 71 23 71 71 71 47 2 71 2 64 2 2 71 17 58 2 2
0.00/0.07	d CHECKS 1892
0.00/0.07	d ASSIGNMENTS 69
0.00/0.07	d NODES 69 BACKTRACKS 1 FAILURES 1 RUNTIME 0 TOTALTIME 0 NODES/s 6900 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-2070743-1247351693/watcher-2070743-1247351693 -o /tmp/evaluation-result-2070743-1247351693/solver-2070743-1247351693 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2070743-1247351693.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: 2.00 2.02 2.12 4/80 17530
/proc/meminfo: memFree=1801840/2055920 swapFree=4192812/4192956
[pid=17530] ppid=17528 vsize=18576 CPUtime=0
/proc/17530/stat : 17530 (runsolver) R 17528 17530 16948 0 -1 4194368 15 0 0 0 0 0 0 0 19 0 1 0 22235972 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 217871609127 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/17530/statm: 4644 284 249 26 0 2626 0

[startup+0.044153 s]
/proc/loadavg: 2.00 2.02 2.12 4/80 17530
/proc/meminfo: memFree=1801840/2055920 swapFree=4192812/4192956
[pid=17530] ppid=17528 vsize=2292 CPUtime=0
/proc/17530/stat : 17530 (ld-linux.so.2) D 17528 17530 16948 0 -1 4194304 51 0 2 0 0 0 0 0 18 0 1 0 22235972 2347008 38 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448525156 0 2147483391 4096 0 18446744072099937270 0 0 17 1 0 0
/proc/17530/statm: 573 38 28 29 0 5 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2292

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

[startup+0.044153 s]
/proc/loadavg: 2.00 2.02 2.12 4/80 17530
/proc/meminfo: memFree=1801840/2055920 swapFree=4192812/4192956
[pid=17530] ppid=17528 vsize=2292 CPUtime=0
/proc/17530/stat : 17530 (ld-linux.so.2) D 17528 17530 16948 0 -1 4194304 51 0 2 0 0 0 0 0 18 0 1 0 22235972 2347008 38 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448525156 0 2147483391 4096 0 18446744072099937270 0 0 17 1 0 0
/proc/17530/statm: 573 38 28 29 0 5 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2292

Child status: 0
Real time (s): 0.074294
CPU time (s): 0.009997
CPU user time (s): 0.007998
CPU system time (s): 0.001999
CPU usage (%): 13.456
Max. virtual memory (cumulated for all children) (KiB): 2292

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.007998
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 546
page faults= 9
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 38
involuntary context switches= 7

runsolver used 0.002999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node28 at 2009-07-12 00:34:53
IDJOB=2070743
IDBENCH=55390
IDSOLVER=769
FILE ID=node28/2070743-1247351693
PBS_JOBID= 9506896
Free space on /tmp= 66096 MiB

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

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

MD5SUM BENCH= b233b8519d2f71c6ff7ca4b677055e01
RANDOM SEED=260784096

node28.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.230
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.230
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:       1802320 kB
Buffers:         12524 kB
Cached:          79548 kB
SwapCached:          0 kB
Active:         157904 kB
Inactive:        47412 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1802320 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1512 kB
Writeback:           0 kB
Mapped:         131088 kB
Slab:            33236 kB
Committed_AS:   894240 kB
PageTables:       2024 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= 66096 MiB
End job on node28 at 2009-07-12 00:34:54