Trace number 1073725

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.54976 1.59166

DiagnosticValue
ASSIGNMENTS176
CHECKS154826

General information on the benchmark

Namecsp/modifiedRenault/
normalized-renault-mod-24_ext.xml
MD5SUM0aa7168aea0418cd8fdedf9a6147e0cb
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.691894
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)

1.45/1.59	s UNSATISFIABLE
1.45/1.59	d CHECKS 154826
1.45/1.59	d ASSIGNMENTS 176

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-1073725-1215177566/watcher-1073725-1215177566 -o /tmp/evaluation-result-1073725-1215177566/solver-1073725-1215177566 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/run -c HOME/instance-1073725-1215177566.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.32 2.33 2.24 4/82 25223
/proc/meminfo: memFree=1667488/2055920 swapFree=4157816/4192956
[pid=25223] ppid=25221 vsize=18572 CPUtime=0
/proc/25223/stat : 25223 (runsolver) R 25221 25223 22759 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 640679745 19017728 292 996147200 4194304 4296836 548682068480 18446744073709551615 271894244647 0 0 4096 24578 0 0 0 17 1 0 0
/proc/25223/statm: 4643 292 257 25 0 2626 0

[startup+0.0685009 s]
/proc/loadavg: 2.32 2.33 2.24 4/82 25223
/proc/meminfo: memFree=1667488/2055920 swapFree=4157816/4192956
[pid=25223] ppid=25221 vsize=4552 CPUtime=0.03
/proc/25223/stat : 25223 (ld-linux.so.2) R 25221 25223 22759 0 -1 4194304 691 0 3 0 3 0 0 0 18 0 1 0 640679745 4661248 425 996147200 1448431616 1448550632 4294956272 18446744073709551615 134618466 0 0 4096 0 0 0 0 17 0 0 0
/proc/25223/statm: 1138 425 328 29 0 128 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 4552

[startup+0.101495 s]
/proc/loadavg: 2.32 2.33 2.24 4/82 25223
/proc/meminfo: memFree=1667488/2055920 swapFree=4157816/4192956
[pid=25223] ppid=25221 vsize=4552 CPUtime=0.06
/proc/25223/stat : 25223 (ld-linux.so.2) R 25221 25223 22759 0 -1 4194304 727 0 3 0 6 0 0 0 18 0 1 0 640679745 4661248 461 996147200 1448431616 1448550632 4294956272 18446744073709551615 134557737 0 0 4096 0 0 0 0 17 0 0 0
/proc/25223/statm: 1138 461 328 29 0 128 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 4552

[startup+0.301517 s]
/proc/loadavg: 2.32 2.33 2.24 4/82 25223
/proc/meminfo: memFree=1667488/2055920 swapFree=4157816/4192956
[pid=25223] ppid=25221 vsize=6852 CPUtime=0.26
/proc/25223/stat : 25223 (ld-linux.so.2) R 25221 25223 22759 0 -1 4194304 1019 0 3 0 26 0 0 0 19 0 1 0 640679745 7016448 753 996147200 1448431616 1448550632 4294956272 18446744073709551615 134609030 0 0 4096 0 0 0 0 17 0 0 0
/proc/25223/statm: 1713 753 328 29 0 703 0
Current children cumulated CPU time (s) 0.26
Current children cumulated vsize (KiB) 6852

[startup+0.701555 s]
/proc/loadavg: 2.32 2.33 2.24 4/82 25223
/proc/meminfo: memFree=1667488/2055920 swapFree=4157816/4192956
[pid=25223] ppid=25221 vsize=7732 CPUtime=0.67
/proc/25223/stat : 25223 (ld-linux.so.2) R 25221 25223 22759 0 -1 4194304 1464 0 3 0 66 1 0 0 23 0 1 0 640679745 7917568 1198 996147200 1448431616 1448550632 4294956272 18446744073709551615 134557843 0 0 4096 0 0 0 0 17 0 0 0
/proc/25223/statm: 1933 1198 328 29 0 923 0
Current children cumulated CPU time (s) 0.67
Current children cumulated vsize (KiB) 7732

[startup+1.50164 s]
/proc/loadavg: 2.32 2.33 2.24 3/82 25225
/proc/meminfo: memFree=1659096/2055920 swapFree=4157816/4192956
[pid=25223] ppid=25221 vsize=16240 CPUtime=1.45
/proc/25223/stat : 25223 (ld-linux.so.2) R 25221 25223 22759 0 -1 4194304 3674 0 3 0 143 2 0 0 25 0 1 0 640679745 16629760 3408 996147200 1448431616 1448550632 4294956272 18446744073709551615 134547567 0 0 4096 0 0 0 0 17 0 0 0
/proc/25223/statm: 4060 3408 343 29 0 3050 0
Current children cumulated CPU time (s) 1.45
Current children cumulated vsize (KiB) 16240

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

Child status: 0
Real time (s): 1.59166
CPU time (s): 1.54976
CPU user time (s): 1.52577
CPU system time (s): 0.023996
CPU usage (%): 97.368
Max. virtual memory (cumulated for all children) (KiB): 16240

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

runsolver used 0.003999 second user time and 0.009998 second system time

The end

Launcher Data (download as text)

Begin job on node60 at 2008-07-04 15:19:26
IDJOB=1073725
IDBENCH=56370
IDSOLVER=328
FILE ID=node60/1073725-1215177566
PBS_JOBID= 7881437
Free space on /tmp= 66548 MiB

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

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 0aa7168aea0418cd8fdedf9a6147e0cb
RANDOM SEED=1963000056

node60.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:       1667968 kB
Buffers:         26204 kB
Cached:         115896 kB
SwapCached:      29328 kB
Active:         290764 kB
Inactive:        45112 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1667968 kB
SwapTotal:     4192956 kB
SwapFree:      4157816 kB
Dirty:            8484 kB
Writeback:           0 kB
Mapped:         209540 kB
Slab:            36840 kB
Committed_AS:  1264968 kB
PageTables:       2280 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 node60 at 2008-07-04 15:19:28