Trace number 1057330

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
cpHydra k_40SAT 0.030995 0.0319761

DiagnosticValue
ASSIGNMENTS419
CHECKS16634

General information on the benchmark

Namecsp/primes-25/
normalized-primes-25-20-2-7.xml
MD5SUMf31fe02afe517b20e843c92c91181f95
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.016997
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints20
Maximum constraint arity9
Maximum domain size96
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 (download as text)

0.00/0.00	c cpHydra_k_40 version 0.0
0.00/0.03	c mistral-prime version 1.313
0.00/0.03	s SATISFIABLE
0.00/0.03	v 2 2 15 61 65 24 25 58 93 2 70 2 4 2 24 2 2 2 2 11 2 2 2 96 3 2 89 2 2 3 67 2 22 68 97 15 2 2 12 58 11 97 2 2 2 2 3 2 9 2 28 2 2 13 2 95 97 2 2 29 45 83 2 2 3 72 52 2 2 2 2 2 57 30 97 2 2 2 2 2 2 2 6 44 87 71 17 4 23 88 2 63 61 2 4 2 2 56 2 2
0.00/0.03	d CHECKS 16634
0.00/0.03	d ASSIGNMENTS 419

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-1057330-1215110192/watcher-1057330-1215110192 -o /tmp/evaluation-result-1057330-1215110192/solver-1057330-1215110192 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/cpHydra_k_40/hydra HOME/instance-1057330-1215110192.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.09 2.04 1.97 4/85 16666
/proc/meminfo: memFree=1804024/2055920 swapFree=4179496/4192956
[pid=16666] ppid=16664 vsize=5360 CPUtime=0
/proc/16666/stat : 16666 (hydra) S 16664 16666 16326 0 -1 4194304 285 0 0 0 0 0 0 0 18 0 1 0 244007200 5488640 236 996147200 4194304 4889804 548682068816 18446744073709551615 269807575876 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/16666/statm: 1340 236 195 169 0 51 0
[pid=16667] ppid=16666 vsize=5360 CPUtime=0
/proc/16667/stat : 16667 (hydra) R 16666 16666 16326 0 -1 4194368 22 0 0 0 0 0 0 0 19 0 1 0 244007200 5488640 239 996147200 4194304 4889804 548682068816 18446744073709551615 269807578407 0 0 4096 0 0 0 0 17 1 0 0
/proc/16667/statm: 1340 239 198 169 0 51 0

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

Child status: 0
Real time (s): 0.0319761
CPU time (s): 0.030995
CPU user time (s): 0.017997
CPU system time (s): 0.012998
CPU usage (%): 96.9318
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.017997
system time used= 0.012998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1724
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= 26
involuntary context switches= 12

runsolver used 0.000999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node81 at 2008-07-03 20:36:32
IDJOB=1057330
IDBENCH=54025
IDSOLVER=366
FILE ID=node81/1057330-1215110192
PBS_JOBID= 7877046
Free space on /tmp= 126828 MiB

SOLVER NAME= cpHydra k_40
BENCH NAME= CPAI08/csp/primes-25/normalized-primes-25-20-2-7.xml
COMMAND LINE= HOME/cpHydra_k_40/hydra BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1057330-1215110192/watcher-1057330-1215110192 -o /tmp/evaluation-result-1057330-1215110192/solver-1057330-1215110192 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/cpHydra_k_40/hydra HOME/instance-1057330-1215110192.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= f31fe02afe517b20e843c92c91181f95
RANDOM SEED=428535690

node81.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.236
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.236
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:       1804504 kB
Buffers:         11140 kB
Cached:         165644 kB
SwapCached:       6544 kB
Active:         151488 kB
Inactive:        65096 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1804504 kB
SwapTotal:     4192956 kB
SwapFree:      4179496 kB
Dirty:           24408 kB
Writeback:           0 kB
Mapped:          57192 kB
Slab:            19900 kB
Committed_AS:   539024 kB
PageTables:       1788 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= 126804 MiB
End job on node81 at 2008-07-03 20:36:33