Trace number 1073402

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 1.13983 1.1618

DiagnosticValue
CHECKS10834

General information on the benchmark

Namecsp/modifiedRenault/
normalized-renault-mod-27_ext.xml
MD5SUMd195fd4e3ae3a69fafec02a0db1e800b
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.697893
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.08/0.11	c loading... 1.09 secs
1.08/1.11	c smallest 4
1.08/1.11	c largest 362
1.08/1.11	c average 43.0211
1.08/1.11	
1.08/1.16	s UNSATISFIABLE
1.08/1.16	d CHECKS 10834
1.08/1.16	c FAILS 279
1.08/1.16	c RESTARTS 0

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-1073402-1215177152/watcher-1073402-1215177152 -o /tmp/evaluation-result-1073402-1215177152/solver-1073402-1215177152 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1073402-1215177152.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.06 2.03 2.00 4/81 17436
/proc/meminfo: memFree=1466432/2055920 swapFree=4180000/4192956
[pid=17436] ppid=17434 vsize=364 CPUtime=0
/proc/17436/stat : 17436 (solver) R 17434 17436 16733 0 -1 4194304 39 0 0 0 0 0 0 0 19 0 1 0 1996689424 372736 25 996147200 134512640 134773262 4294956240 18446744073709551615 2495268 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/17436/statm: 91 25 19 63 0 3 0

[startup+0.0932351 s]
/proc/loadavg: 2.06 2.03 2.00 4/81 17436
/proc/meminfo: memFree=1466432/2055920 swapFree=4180000/4192956
[pid=17436] ppid=17434 vsize=9084 CPUtime=0.07
/proc/17436/stat : 17436 (solver) R 17434 17436 16733 0 -1 4194304 1523 0 0 0 7 0 0 0 19 0 1 0 1996689424 9302016 1487 996147200 134512640 134773262 4294956240 18446744073709551615 2961111 0 0 4096 0 0 0 0 17 1 0 0
/proc/17436/statm: 2271 1487 338 63 0 1288 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 9084

[startup+0.101232 s]
/proc/loadavg: 2.06 2.03 2.00 4/81 17436
/proc/meminfo: memFree=1466432/2055920 swapFree=4180000/4192956
[pid=17436] ppid=17434 vsize=9288 CPUtime=0.08
/proc/17436/stat : 17436 (solver) R 17434 17436 16733 0 -1 4194304 1527 0 0 0 8 0 0 0 19 0 1 0 1996689424 9510912 1491 996147200 134512640 134773262 4294956240 18446744073709551615 134534551 0 0 4096 0 0 0 0 17 1 0 0
/proc/17436/statm: 2322 1491 338 63 0 1339 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 9288

[startup+0.301256 s]
/proc/loadavg: 2.06 2.03 2.00 4/81 17436
/proc/meminfo: memFree=1466432/2055920 swapFree=4180000/4192956
[pid=17436] ppid=17434 vsize=9576 CPUtime=0.28
/proc/17436/stat : 17436 (solver) R 17434 17436 16733 0 -1 4194304 1596 0 0 0 28 0 0 0 21 0 1 0 1996689424 9805824 1560 996147200 134512640 134773262 4294956240 18446744073709551615 2936049 0 0 4096 0 0 0 0 17 1 0 0
/proc/17436/statm: 2394 1560 338 63 0 1411 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 9576

[startup+0.701292 s]
/proc/loadavg: 2.06 2.03 2.00 4/81 17436
/proc/meminfo: memFree=1466432/2055920 swapFree=4180000/4192956
[pid=17436] ppid=17434 vsize=9636 CPUtime=0.67
/proc/17436/stat : 17436 (solver) R 17434 17436 16733 0 -1 4194304 1625 0 0 0 67 0 0 0 25 0 1 0 1996689424 9867264 1589 996147200 134512640 134773262 4294956240 18446744073709551615 134603703 0 0 4096 0 0 0 0 17 1 0 0
/proc/17436/statm: 2409 1589 338 63 0 1426 0
Current children cumulated CPU time (s) 0.67
Current children cumulated vsize (KiB) 9636

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

[startup+1.10635 s]
/proc/loadavg: 2.06 2.03 2.00 3/82 17437
/proc/meminfo: memFree=1461048/2055920 swapFree=4180000/4192956
[pid=17436] ppid=17434 vsize=5348 CPUtime=1.08
/proc/17436/stat : 17436 (solver) R 17434 17436 16733 0 -1 4194304 1758 0 0 0 107 1 0 0 25 0 1 0 1996689424 5476352 695 996147200 134512640 134773262 4294956240 18446744073709551615 2928332 0 0 4096 0 0 0 0 17 1 0 0
/proc/17436/statm: 1337 695 343 63 0 354 0
Current children cumulated CPU time (s) 1.08
Current children cumulated vsize (KiB) 5348

Child status: 0
Real time (s): 1.1618
CPU time (s): 1.13983
CPU user time (s): 1.12483
CPU system time (s): 0.014997
CPU usage (%): 98.1088
Max. virtual memory (cumulated for all children) (KiB): 9856

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

runsolver used 0.004999 second user time and 0.009998 second system time

The end

Launcher Data (download as text)

Begin job on node23 at 2008-07-04 15:12:33
IDJOB=1073402
IDBENCH=56350
IDSOLVER=311
FILE ID=node23/1073402-1215177152
PBS_JOBID= 7881536
Free space on /tmp= 66540 MiB

SOLVER NAME= mddc-solv 2008-06-09
BENCH NAME= CPAI08/csp/modifiedRenault/normalized-renault-mod-27_ext.xml
COMMAND LINE= HOME/solver BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1073402-1215177152/watcher-1073402-1215177152 -o /tmp/evaluation-result-1073402-1215177152/solver-1073402-1215177152 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1073402-1215177152.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= d195fd4e3ae3a69fafec02a0db1e800b
RANDOM SEED=1896799205

node23.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.216
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.216
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:       1466912 kB
Buffers:         31296 kB
Cached:         137048 kB
SwapCached:       6756 kB
Active:         488240 kB
Inactive:        46232 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1466912 kB
SwapTotal:     4192956 kB
SwapFree:      4180000 kB
Dirty:            3224 kB
Writeback:           0 kB
Mapped:         382592 kB
Slab:            39104 kB
Committed_AS:  4135096 kB
PageTables:       2536 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= 66540 MiB
End job on node23 at 2008-07-04 15:12:34