Trace number 1048498

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
mddc-solv 2008-06-09UNSAT 0.673897 0.674405

DiagnosticValue
CHECKS6327

General information on the benchmark

Namecsp/rand-10-20-10/
normalized-rand-10-20-10-5-10000-19_ext.xml
MD5SUM46427bdc7f3b95f9a5a242e456509ade
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.673897
Satisfiable
(Un)Satisfiability was proved
Number of variables20
Number of constraints5
Maximum constraint arity10
Maximum domain size10
Number of constraints which are defined in extension5
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.00	c loading... 0.34 secs
0.29/0.35	c smallest 23963
0.29/0.35	c largest 24065
0.29/0.35	c average 24010.6
0.29/0.35	
0.60/0.66	s UNSATISFIABLE
0.60/0.66	d CHECKS 6327
0.60/0.66	c FAILS 782
0.60/0.66	c RESTARTS 4

Verifier Data (download as text)

No possible verification on an UNSAT instance

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-1048498-1215043269/watcher-1048498-1215043269 -o /tmp/evaluation-result-1048498-1215043269/solver-1048498-1215043269 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1048498-1215043269.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: 1.92 1.98 1.90 3/74 2631
/proc/meminfo: memFree=1807424/2055920 swapFree=4180416/4192956
[pid=2631] ppid=2628 vsize=8820 CPUtime=0
/proc/2631/stat : 2631 (solver) R 2628 2631 1882 0 -1 4194304 417 0 0 0 0 0 0 0 18 0 1 0 1983298776 9031680 384 996147200 134512640 134773262 4294956256 18446744073709551615 3053179 0 0 4096 0 0 0 0 17 0 0 0
/proc/2631/statm: 2205 384 334 63 0 1222 0

[startup+0.0928451 s]
/proc/loadavg: 1.92 1.98 1.90 3/74 2631
/proc/meminfo: memFree=1807424/2055920 swapFree=4180416/4192956
[pid=2631] ppid=2628 vsize=10168 CPUtime=0.08
/proc/2631/stat : 2631 (solver) R 2628 2631 1882 0 -1 4194304 2825 0 0 0 8 0 0 0 18 0 1 0 1983298776 10412032 1768 996147200 134512640 134773262 4294956256 18446744073709551615 3053179 0 0 4096 0 0 0 0 17 0 0 0
/proc/2631/statm: 2542 1768 338 63 0 1559 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 10168

[startup+0.102845 s]
/proc/loadavg: 1.92 1.98 1.90 3/74 2631
/proc/meminfo: memFree=1807424/2055920 swapFree=4180416/4192956
[pid=2631] ppid=2628 vsize=10300 CPUtime=0.09
/proc/2631/stat : 2631 (solver) R 2628 2631 1882 0 -1 4194304 2861 0 0 0 9 0 0 0 18 0 1 0 1983298776 10547200 1804 996147200 134512640 134773262 4294956256 18446744073709551615 3053125 0 0 4096 0 0 0 0 17 0 0 0
/proc/2631/statm: 2575 1805 338 63 0 1592 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 10300

[startup+0.302879 s]
/proc/loadavg: 1.92 1.98 1.90 3/74 2631
/proc/meminfo: memFree=1807424/2055920 swapFree=4180416/4192956
[pid=2631] ppid=2628 vsize=12964 CPUtime=0.29
/proc/2631/stat : 2631 (solver) R 2628 2631 1882 0 -1 4194304 3542 0 0 0 29 0 0 0 20 0 1 0 1983298776 13275136 2485 996147200 134512640 134773262 4294956256 18446744073709551615 3053179 0 0 4096 0 0 0 0 17 0 0 0
/proc/2631/statm: 3241 2485 338 63 0 2258 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 12964

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

[startup+0.501917 s]
/proc/loadavg: 1.92 1.98 1.90 3/74 2631
/proc/meminfo: memFree=1807424/2055920 swapFree=4180416/4192956
[pid=2631] ppid=2628 vsize=9848 CPUtime=0.5
/proc/2631/stat : 2631 (solver) R 2628 2631 1882 0 -1 4194304 4009 0 0 0 49 1 0 0 21 0 1 0 1983298776 10084352 1856 996147200 134512640 134773262 4294956256 18446744073709551615 134529837 0 0 4096 0 0 0 0 17 0 0 0
/proc/2631/statm: 2462 1856 364 63 0 1479 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 9848

[startup+0.601929 s]
/proc/loadavg: 1.92 1.98 1.90 3/74 2631
/proc/meminfo: memFree=1807424/2055920 swapFree=4180416/4192956
[pid=2631] ppid=2628 vsize=9848 CPUtime=0.6
/proc/2631/stat : 2631 (solver) R 2628 2631 1882 0 -1 4194304 4009 0 0 0 59 1 0 0 23 0 1 0 1983298776 10084352 1856 996147200 134512640 134773262 4294956256 18446744073709551615 134530120 0 0 4096 0 0 0 0 17 0 0 0
/proc/2631/statm: 2462 1856 364 63 0 1479 0
Current children cumulated CPU time (s) 0.6
Current children cumulated vsize (KiB) 9848

Child status: 0
Real time (s): 0.674405
CPU time (s): 0.673897
CPU user time (s): 0.661899
CPU system time (s): 0.011998
CPU usage (%): 99.9247
Max. virtual memory (cumulated for all children) (KiB): 12964

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.661899
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4020
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= 13

runsolver used 0.004999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node51 at 2008-07-03 02:01:09
IDJOB=1048498
IDBENCH=54365
IDSOLVER=311
FILE ID=node51/1048498-1215043269
PBS_JOBID= 7875073
Free space on /tmp= 66548 MiB

SOLVER NAME= mddc-solv 2008-06-09
BENCH NAME= CPAI08/csp/rand-10-20-10/normalized-rand-10-20-10-5-10000-19_ext.xml
COMMAND LINE= HOME/solver BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1048498-1215043269/watcher-1048498-1215043269 -o /tmp/evaluation-result-1048498-1215043269/solver-1048498-1215043269 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1048498-1215043269.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 46427bdc7f3b95f9a5a242e456509ade
RANDOM SEED=316069434

node51.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.263
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.263
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:       1808936 kB
Buffers:         31588 kB
Cached:         148956 kB
SwapCached:       7000 kB
Active:         131036 kB
Inactive:        60228 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1808936 kB
SwapTotal:     4192956 kB
SwapFree:      4180416 kB
Dirty:            3292 kB
Writeback:           0 kB
Mapped:          16228 kB
Slab:            41016 kB
Committed_AS:  3713844 kB
PageTables:       1796 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= 66548 MiB
End job on node51 at 2008-07-03 02:01:10