Trace number 1047875

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.60576 1.63005

DiagnosticValue
ASSIGNMENTS2120
CHECKS162036

General information on the benchmark

Namecsp/bddLarge/
normalized-bdd-21-2713-15-79-1_ext.xml
MD5SUM8032590ef8e58177625c69560ed6b0e1
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 benchmark21.2638
Satisfiable
(Un)Satisfiability was proved
Number of variables21
Number of constraints2713
Maximum constraint arity15
Maximum domain size2
Number of constraints which are defined in extension2713
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

1.57/1.62	s UNSATISFIABLE
1.57/1.62	d CHECKS 162036
1.57/1.62	d ASSIGNMENTS 2120

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-1047875-1215041539/watcher-1047875-1215041539 -o /tmp/evaluation-result-1047875-1215041539/solver-1047875-1215041539 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/run -c HOME/instance-1047875-1215041539.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.03 2.03 1.76 4/72 6992
/proc/meminfo: memFree=1017736/2055920 swapFree=4180424/4192956
[pid=6992] ppid=6990 vsize=5260 CPUtime=0
/proc/6992/stat : 6992 (run) R 6990 6992 6772 0 -1 4194304 69 0 0 0 0 0 0 0 20 0 1 0 1983126202 5386240 43 996147200 4194304 4889804 548682068848 18446744073709551615 273651136601 0 0 4096 0 0 0 0 17 1 0 0
/proc/6992/statm: 1315 43 29 169 0 14 0

[startup+0.030713 s]
/proc/loadavg: 2.03 2.03 1.76 4/72 6992
/proc/meminfo: memFree=1017736/2055920 swapFree=4180424/4192956
[pid=6992] ppid=6990 vsize=4112 CPUtime=0
/proc/6992/stat : 6992 (ld-linux.so.2) D 6990 6992 6772 0 -1 4194304 444 0 3 0 0 0 0 0 18 0 1 0 1983126202 4210688 179 996147200 1448431616 1448550632 4294956288 18446744073709551615 4157628384 0 0 4096 0 18446744071563479169 0 0 17 0 0 0
/proc/6992/statm: 1028 179 149 29 0 18 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 4112

[startup+0.101723 s]
/proc/loadavg: 2.03 2.03 1.76 4/72 6992
/proc/meminfo: memFree=1017736/2055920 swapFree=4180424/4192956
[pid=6992] ppid=6990 vsize=4648 CPUtime=0.06
/proc/6992/stat : 6992 (ld-linux.so.2) R 6990 6992 6772 0 -1 4194304 729 0 4 0 6 0 0 0 18 0 1 0 1983126202 4759552 464 996147200 1448431616 1448550632 4294956288 18446744073709551615 4159729157 0 0 4096 0 0 0 0 17 0 0 0
/proc/6992/statm: 1162 464 328 29 0 152 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 4648

[startup+0.301749 s]
/proc/loadavg: 2.03 2.03 1.76 4/72 6992
/proc/meminfo: memFree=1017736/2055920 swapFree=4180424/4192956
[pid=6992] ppid=6990 vsize=7564 CPUtime=0.27
/proc/6992/stat : 6992 (ld-linux.so.2) R 6990 6992 6772 0 -1 4194304 1481 0 4 0 26 1 0 0 19 0 1 0 1983126202 7745536 1216 996147200 1448431616 1448550632 4294956288 18446744073709551615 4157598267 0 0 4096 0 0 0 0 17 0 0 0
/proc/6992/statm: 1891 1216 331 29 0 881 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 7564

[startup+0.70181 s]
/proc/loadavg: 2.03 2.03 1.76 4/72 6992
/proc/meminfo: memFree=1017736/2055920 swapFree=4180424/4192956
[pid=6992] ppid=6990 vsize=9680 CPUtime=0.67
/proc/6992/stat : 6992 (ld-linux.so.2) R 6990 6992 6772 0 -1 4194304 2020 0 4 0 66 1 0 0 22 0 1 0 1983126202 9912320 1755 996147200 1448431616 1448550632 4294956288 18446744073709551615 134522691 0 0 4096 0 0 0 0 17 0 0 0
/proc/6992/statm: 2420 1755 343 29 0 1410 0
Current children cumulated CPU time (s) 0.67
Current children cumulated vsize (KiB) 9680

[startup+1.50193 s]
/proc/loadavg: 2.03 2.03 1.76 3/73 6993
/proc/meminfo: memFree=1010048/2055920 swapFree=4180424/4192956
[pid=6992] ppid=6990 vsize=9680 CPUtime=1.47
/proc/6992/stat : 6992 (ld-linux.so.2) R 6990 6992 6772 0 -1 4194304 2020 0 4 0 146 1 0 0 25 0 1 0 1983126202 9912320 1755 996147200 1448431616 1448550632 4294956288 18446744073709551615 134544042 0 0 4096 0 0 0 0 17 0 0 0
/proc/6992/statm: 2420 1755 343 29 0 1410 0
Current children cumulated CPU time (s) 1.47
Current children cumulated vsize (KiB) 9680

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

[startup+1.60194 s]
/proc/loadavg: 2.03 2.03 1.76 3/73 6993
/proc/meminfo: memFree=1010048/2055920 swapFree=4180424/4192956
[pid=6992] ppid=6990 vsize=9680 CPUtime=1.57
/proc/6992/stat : 6992 (ld-linux.so.2) R 6990 6992 6772 0 -1 4194304 2020 0 4 0 156 1 0 0 25 0 1 0 1983126202 9912320 1755 996147200 1448431616 1448550632 4294956288 18446744073709551615 134546509 0 0 4096 0 0 0 0 17 0 0 0
/proc/6992/statm: 2420 1755 343 29 0 1410 0
Current children cumulated CPU time (s) 1.57
Current children cumulated vsize (KiB) 9680

Child status: 0
Real time (s): 1.63005
CPU time (s): 1.60576
CPU user time (s): 1.58676
CPU system time (s): 0.018997
CPU usage (%): 98.5099
Max. virtual memory (cumulated for all children) (KiB): 9680

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.58676
system time used= 0.018997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2035
page faults= 4
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 40
involuntary context switches= 15

runsolver used 0.005999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node52 at 2008-07-03 01:32:19
IDJOB=1047875
IDBENCH=54166
IDSOLVER=328
FILE ID=node52/1047875-1215041539
PBS_JOBID= 7875072
Free space on /tmp= 66524 MiB

SOLVER NAME= spider 2008-06-14
BENCH NAME= CPAI08/csp/bddLarge/normalized-bdd-21-2713-15-79-1_ext.xml
COMMAND LINE= HOME/run -c BENCHNAME
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1047875-1215041539/watcher-1047875-1215041539 -o /tmp/evaluation-result-1047875-1215041539/solver-1047875-1215041539 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/run -c HOME/instance-1047875-1215041539.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 8032590ef8e58177625c69560ed6b0e1
RANDOM SEED=737350257

node52.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.265
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.265
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:       1018216 kB
Buffers:         28224 kB
Cached:         128872 kB
SwapCached:       6784 kB
Active:         924532 kB
Inactive:        55120 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1018216 kB
SwapTotal:     4192956 kB
SwapFree:      4180424 kB
Dirty:            1680 kB
Writeback:           0 kB
Mapped:         830004 kB
Slab:            41756 kB
Committed_AS:  4658812 kB
PageTables:       3424 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= 66520 MiB
End job on node52 at 2008-07-03 01:32:21