Trace number 1073633

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
spider 2008-06-14UNSAT 1.49677 1.51358

DiagnosticValue
ASSIGNMENTS227
CHECKS240572

General information on the benchmark

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

Solver Data (download as text)

1.48/1.51	s UNSATISFIABLE
1.48/1.51	d CHECKS 240572
1.48/1.51	d ASSIGNMENTS 227

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-1073633-1215177431/watcher-1073633-1215177431 -o /tmp/evaluation-result-1073633-1215177431/solver-1073633-1215177431 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/run -c HOME/instance-1073633-1215177431.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.20 1.98 1.77 4/88 27161
/proc/meminfo: memFree=1595808/2055920 swapFree=4178892/4192956
[pid=27161] ppid=27159 vsize=4244 CPUtime=0
/proc/27161/stat : 27161 (ld-linux.so.2) R 27159 27161 26841 0 -1 4194304 658 0 0 0 0 0 0 0 18 0 1 0 673472070 4345856 389 996147200 1448431616 1448550632 4294956272 18446744073709551615 4157598267 0 0 4096 0 0 0 0 17 0 0 0
/proc/27161/statm: 1061 389 327 29 0 51 0

[startup+0.0970681 s]
/proc/loadavg: 2.20 1.98 1.77 4/88 27161
/proc/meminfo: memFree=1595808/2055920 swapFree=4178892/4192956
[pid=27161] ppid=27159 vsize=4684 CPUtime=0.08
/proc/27161/stat : 27161 (ld-linux.so.2) R 27159 27161 26841 0 -1 4194304 763 0 0 0 8 0 0 0 18 0 1 0 673472070 4796416 494 996147200 1448431616 1448550632 4294956272 18446744073709551615 134561409 0 0 4096 0 0 0 0 17 0 0 0
/proc/27161/statm: 1171 494 328 29 0 161 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 4684

[startup+0.101067 s]
/proc/loadavg: 2.20 1.98 1.77 4/88 27161
/proc/meminfo: memFree=1595808/2055920 swapFree=4178892/4192956
[pid=27161] ppid=27159 vsize=4832 CPUtime=0.09
/proc/27161/stat : 27161 (ld-linux.so.2) R 27159 27161 26841 0 -1 4194304 772 0 0 0 9 0 0 0 18 0 1 0 673472070 4947968 503 996147200 1448431616 1448550632 4294956272 18446744073709551615 134539011 0 0 4096 0 0 0 0 17 0 0 0
/proc/27161/statm: 1208 503 328 29 0 198 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4832

[startup+0.301096 s]
/proc/loadavg: 2.20 1.98 1.77 4/88 27161
/proc/meminfo: memFree=1595808/2055920 swapFree=4178892/4192956
[pid=27161] ppid=27159 vsize=6852 CPUtime=0.28
/proc/27161/stat : 27161 (ld-linux.so.2) R 27159 27161 26841 0 -1 4194304 1050 0 0 0 28 0 0 0 20 0 1 0 673472070 7016448 781 996147200 1448431616 1448550632 4294956272 18446744073709551615 134610201 0 0 4096 0 0 0 0 17 0 0 0
/proc/27161/statm: 1713 782 328 29 0 703 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 6852

[startup+0.701135 s]
/proc/loadavg: 2.20 1.98 1.77 4/88 27161
/proc/meminfo: memFree=1595808/2055920 swapFree=4178892/4192956
[pid=27161] ppid=27159 vsize=7732 CPUtime=0.69
/proc/27161/stat : 27161 (ld-linux.so.2) R 27159 27161 26841 0 -1 4194304 1507 0 0 0 68 1 0 0 23 0 1 0 673472070 7917568 1238 996147200 1448431616 1448550632 4294956272 18446744073709551615 134539011 0 0 4096 0 0 0 0 17 0 0 0
/proc/27161/statm: 1933 1238 328 29 0 923 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 7732

[startup+1.50122 s]
/proc/loadavg: 2.19 1.98 1.77 3/89 27162
/proc/meminfo: memFree=1590552/2055920 swapFree=4178892/4192956
[pid=27161] ppid=27159 vsize=16032 CPUtime=1.48
/proc/27161/stat : 27161 (ld-linux.so.2) R 27159 27161 26841 0 -1 4194304 3625 0 0 0 146 2 0 0 25 0 1 0 673472070 16416768 3356 996147200 1448431616 1448550632 4294956272 18446744073709551615 134535319 0 0 4096 0 0 0 0 17 0 0 0
/proc/27161/statm: 4008 3356 343 29 0 2998 0
Current children cumulated CPU time (s) 1.48
Current children cumulated vsize (KiB) 16032

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

Child status: 0
Real time (s): 1.51358
CPU time (s): 1.49677
CPU user time (s): 1.47078
CPU system time (s): 0.025996
CPU usage (%): 98.8893
Max. virtual memory (cumulated for all children) (KiB): 16032

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.47078
system time used= 0.025996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3637
page faults= 3
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 29
involuntary context switches= 30

runsolver used 0.002999 second user time and 0.012998 second system time

The end

Launcher Data (download as text)

Begin job on node86 at 2008-07-04 15:17:11
IDJOB=1073633
IDBENCH=56364
IDSOLVER=328
FILE ID=node86/1073633-1215177431
PBS_JOBID= 7881567
Free space on /tmp= 66548 MiB

SOLVER NAME= spider 2008-06-14
BENCH NAME= CPAI08/csp/modifiedRenault/normalized-renault-mod-33_ext.xml
COMMAND LINE= HOME/run -c BENCHNAME
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1073633-1215177431/watcher-1073633-1215177431 -o /tmp/evaluation-result-1073633-1215177431/solver-1073633-1215177431 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/run -c HOME/instance-1073633-1215177431.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 4bd629645af9fc943eb24885c153501f
RANDOM SEED=207792413

node86.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.220
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.220
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:       1596288 kB
Buffers:         62136 kB
Cached:         164304 kB
SwapCached:       6392 kB
Active:         317232 kB
Inactive:        93256 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1596288 kB
SwapTotal:     4192956 kB
SwapFree:      4178892 kB
Dirty:            4756 kB
Writeback:           0 kB
Mapped:         198280 kB
Slab:            33376 kB
Committed_AS:  1446544 kB
PageTables:       2732 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 node86 at 2008-07-04 15:17:13