Trace number 1074095

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-27UNSAT 0.795878 0.805573

DiagnosticValue
ASSIGNMENTS124
CHECKS15453

General information on the benchmark

Namecsp/modifiedRenault/
normalized-renault-mod-29_ext.xml
MD5SUM45166fbe1f988656ff16b282249bbf04
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.727888
Satisfiable
(Un)Satisfiability was proved
Number of variables111
Number of constraints159
Maximum constraint arity10
Maximum domain size42
Number of constraints which are defined in extension159
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.14/0.20	c mistral-prime version 1.313
0.68/0.78	s UNSATISFIABLE
0.68/0.78	d CHECKS 15453
0.68/0.78	d ASSIGNMENTS 124

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-1074095-1215178035/watcher-1074095-1215178035 -o /tmp/evaluation-result-1074095-1215178035/solver-1074095-1215178035 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1074095-1215178035.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: 2.07 2.11 1.93 4/72 25895
/proc/meminfo: memFree=1802128/2055920 swapFree=4179464/4192956
[pid=25895] ppid=25893 vsize=820 CPUtime=0
/proc/25895/stat : 25895 (xsolve) R 25893 25895 25458 0 -1 4194304 39 0 0 0 0 0 0 0 18 0 1 0 1996778354 839680 25 996147200 134512640 135239859 4294956208 18446744073709551615 8905508 0 2147483391 4096 0 0 0 0 17 0 0 0
/proc/25895/statm: 205 25 19 177 0 3 0

[startup+0.154928 s]
/proc/loadavg: 2.07 2.11 1.93 4/72 25895
/proc/meminfo: memFree=1802128/2055920 swapFree=4179464/4192956
[pid=25895] ppid=25893 vsize=7424 CPUtime=0.14
/proc/25895/stat : 25895 (xsolve) R 25893 25895 25458 0 -1 4194304 1145 0 0 0 14 0 0 0 19 0 1 0 1996778354 7602176 1111 996147200 134512640 135239859 4294956208 18446744073709551615 134669888 0 0 4096 0 0 0 0 17 1 0 0
/proc/25895/statm: 1856 1111 350 177 0 759 0
Current children cumulated CPU time (s) 0.14
Current children cumulated vsize (KiB) 7424

[startup+0.201932 s]
/proc/loadavg: 2.07 2.11 1.93 4/72 25895
/proc/meminfo: memFree=1802128/2055920 swapFree=4179464/4192956
[pid=25895] ppid=25893 vsize=8332 CPUtime=0.18
/proc/25895/stat : 25895 (xsolve) R 25893 25895 25458 0 -1 4194304 1361 0 0 0 18 0 0 0 19 0 1 0 1996778354 8531968 1327 996147200 134512640 135239859 4294956208 18446744073709551615 134524411 0 0 4096 0 0 0 0 17 1 0 0
/proc/25895/statm: 2083 1327 350 177 0 986 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 8332

[startup+0.301949 s]
/proc/loadavg: 2.07 2.11 1.93 4/72 25895
/proc/meminfo: memFree=1802128/2055920 swapFree=4179464/4192956
[pid=25895] ppid=25893 vsize=10184 CPUtime=0.29
/proc/25895/stat : 25895 (xsolve) R 25893 25895 25458 0 -1 4194304 1820 0 0 0 28 1 0 0 19 0 1 0 1996778354 10428416 1786 996147200 134512640 135239859 4294956208 18446744073709551615 134524370 0 0 4096 0 0 0 0 17 1 0 0
/proc/25895/statm: 2546 1786 350 177 0 1449 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 10184

[startup+0.702007 s]
/proc/loadavg: 2.07 2.11 1.93 4/72 25895
/proc/meminfo: memFree=1802128/2055920 swapFree=4179464/4192956
[pid=25895] ppid=25893 vsize=14584 CPUtime=0.68
/proc/25895/stat : 25895 (xsolve) R 25893 25895 25458 0 -1 4194304 2895 0 0 0 67 1 0 0 24 0 1 0 1996778354 14934016 2861 996147200 134512640 135239859 4294956208 18446744073709551615 135015603 0 0 4096 0 0 0 0 17 1 0 0
/proc/25895/statm: 3646 2861 388 177 0 2549 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 14584

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

[startup+0.802022 s]
/proc/loadavg: 2.07 2.11 1.93 4/72 25895
/proc/meminfo: memFree=1802128/2055920 swapFree=4179464/4192956
[pid=25895] ppid=25893 vsize=12312 CPUtime=0.78
/proc/25895/stat : 25895 (xsolve) R 25893 25895 25458 0 -1 4194304 2910 0 0 0 77 1 0 0 24 0 1 0 1996778354 12607488 2405 996147200 134512640 135239859 4294956208 18446744073709551615 9338364 0 0 4096 0 0 0 0 17 1 0 0
/proc/25895/statm: 3078 2405 403 177 0 1981 0
Current children cumulated CPU time (s) 0.78
Current children cumulated vsize (KiB) 12312

Child status: 0
Real time (s): 0.805573
CPU time (s): 0.795878
CPU user time (s): 0.778881
CPU system time (s): 0.016997
CPU usage (%): 98.7965
Max. virtual memory (cumulated for all children) (KiB): 14584

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

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node10 at 2008-07-04 15:27:15
IDJOB=1074095
IDBENCH=56388
IDSOLVER=343
FILE ID=node10/1074095-1215178035
PBS_JOBID= 7881559
Free space on /tmp= 66524 MiB

SOLVER NAME= MDG-noprobe 2008-06-27
BENCH NAME= CPAI08/csp/modifiedRenault/normalized-renault-mod-29_ext.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-1074095-1215178035/watcher-1074095-1215178035 -o /tmp/evaluation-result-1074095-1215178035/solver-1074095-1215178035 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1074095-1215178035.xml -heu dom/wdeg -res no 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 45166fbe1f988656ff16b282249bbf04
RANDOM SEED=1489257287

node10.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.229
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.229
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:       1802736 kB
Buffers:         39204 kB
Cached:         148960 kB
SwapCached:       7540 kB
Active:         140072 kB
Inactive:        59232 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1802736 kB
SwapTotal:     4192956 kB
SwapFree:      4179464 kB
Dirty:            8084 kB
Writeback:           0 kB
Mapped:          18588 kB
Slab:            39168 kB
Committed_AS:  3333168 kB
PageTables:       1900 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= 66524 MiB
End job on node10 at 2008-07-04 15:27:16