Trace number 1059756

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
MDG-noprobe 2008-06-27SAT 0.065989 0.0679341

DiagnosticValue
ASSIGNMENTS390
CHECKS134809

General information on the benchmark

Namecsp/primes-30/
normalized-primes-30-60-2-3.xml
MD5SUMbb68641783171ba02b4bd9bfd4e8486c
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.046992
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints60
Maximum constraint arity5
Maximum domain size112
Number of constraints which are defined in extension0
Number of constraints which are defined in intension60
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.00	c mistral-prime version 1.313
0.01/0.06	s SATISFIABLE
0.01/0.06	v 43 59 107 101 89 101 59 2 29 3 5 19 73 71 89 59 2 10 83 59 37 23 107 29 66 73 5 43 19 101 2 41 41 67 113 107 43 59 3 83 29 7 79 113 47 2 23 47 13 43 89 59 3 73 103 7 5 73 59 3 53 53 2 107 103 13 59 29 43 58 97 53 41 53 47 107 47 47 2 73 19 67 17 4 23 2 7 37 18 71 41 2 103 67 71 83 59 17 97 113
0.01/0.06	d CHECKS 134809
0.01/0.06	d ASSIGNMENTS 390

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-1059756-1215124884/watcher-1059756-1215124884 -o /tmp/evaluation-result-1059756-1215124884/solver-1059756-1215124884 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1059756-1215124884.xml -heu dom/wdeg -res no 

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: 0.91 1.03 1.39 3/82 31418
/proc/meminfo: memFree=1012400/2055920 swapFree=4180424/4192956
[pid=31418] ppid=31416 vsize=4584 CPUtime=0
/proc/31418/stat : 31418 (xsolve) R 31416 31418 31045 0 -1 4194304 307 0 0 0 0 0 0 0 18 0 1 0 1991461904 4694016 274 996147200 134512640 135239859 4294956208 18446744073709551615 134529744 0 0 4096 0 0 0 0 17 1 0 0
/proc/31418/statm: 1146 283 239 177 0 49 0

[startup+0.023418 s]
/proc/loadavg: 0.91 1.03 1.39 3/82 31418
/proc/meminfo: memFree=1012400/2055920 swapFree=4180424/4192956
[pid=31418] ppid=31416 vsize=5120 CPUtime=0.01
/proc/31418/stat : 31418 (xsolve) R 31416 31418 31045 0 -1 4194304 635 0 0 0 1 0 0 0 18 0 1 0 1991461904 5242880 601 996147200 134512640 135239859 4294956208 18446744073709551615 135101088 0 0 4096 0 0 0 0 17 1 0 0
/proc/31418/statm: 1280 601 412 177 0 183 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5120

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

[startup+0.023418 s]
/proc/loadavg: 0.91 1.03 1.39 3/82 31418
/proc/meminfo: memFree=1012400/2055920 swapFree=4180424/4192956
[pid=31418] ppid=31416 vsize=5120 CPUtime=0.01
/proc/31418/stat : 31418 (xsolve) R 31416 31418 31045 0 -1 4194304 635 0 0 0 1 0 0 0 18 0 1 0 1991461904 5242880 601 996147200 134512640 135239859 4294956208 18446744073709551615 135101088 0 0 4096 0 0 0 0 17 1 0 0
/proc/31418/statm: 1280 601 412 177 0 183 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5120

Child status: 0
Real time (s): 0.0679341
CPU time (s): 0.065989
CPU user time (s): 0.05999
CPU system time (s): 0.005999
CPU usage (%): 97.1368
Max. virtual memory (cumulated for all children) (KiB): 5120

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

runsolver used 0.004999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node33 at 2008-07-04 00:41:24
IDJOB=1059756
IDBENCH=54374
IDSOLVER=343
FILE ID=node33/1059756-1215124884
PBS_JOBID= 7877230
Free space on /tmp= 66544 MiB

SOLVER NAME= MDG-noprobe 2008-06-27
BENCH NAME= CPAI08/csp/primes-30/normalized-primes-30-60-2-3.xml
COMMAND LINE= HOME/xsolve BENCHNAME -heu dom/wdeg -res no 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1059756-1215124884/watcher-1059756-1215124884 -o /tmp/evaluation-result-1059756-1215124884/solver-1059756-1215124884 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1059756-1215124884.xml -heu dom/wdeg -res no 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= bb68641783171ba02b4bd9bfd4e8486c
RANDOM SEED=46655788

node33.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.231
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.231
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:       1012816 kB
Buffers:         27112 kB
Cached:         196352 kB
SwapCached:       6444 kB
Active:         887840 kB
Inactive:        89624 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1012816 kB
SwapTotal:     4192956 kB
SwapFree:      4180424 kB
Dirty:            1044 kB
Writeback:           0 kB
Mapped:         770180 kB
Slab:            49468 kB
Committed_AS:  4235260 kB
PageTables:       3324 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= 66544 MiB
End job on node33 at 2008-07-04 00:41:24