Trace number 1033953

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-14SAT 0.896863 0.913589

DiagnosticValue
ASSIGNMENTS1248
CHECKS609322

General information on the benchmark

Namecsp/driver/
normalized-driverlogw-02c-sat_ext.xml
MD5SUM8940ec32450c33705b342604bcff6d69
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.135979
Satisfiable
(Un)Satisfiability was proved
Number of variables301
Number of constraints4055
Maximum constraint arity2
Maximum domain size8
Number of constraints which are defined in extension4055
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.87/0.90	s SATISFIABLE
0.87/0.90	v 0 0 0 0 1 0 0 1 0 1 3 1 0 0 0 0 0 0 0 0 0 0 1 1 0 0 2 0 0 0 0 0 3 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 3 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 5 0 0 0 0 0 0 1 0 0 0 0 1 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 2 0 0 0 1 0 0 0 0 0 1 0 0 0 0 1 0 5 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 3 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 2 0 0 0 0 0 0 0 1 1 0 0 1 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 2 0 0 0 0 1 0 0 0 1 1 0 0 1 1 1 0 0 0 0 0 0 0 0 1 1 0 0 1 1 0 0 1 1 1 0 1 0 0 
0.87/0.90	d CHECKS 609322
0.87/0.90	d ASSIGNMENTS 1248

Verifier Data (download as text)

OK

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-1033953-1214949478/watcher-1033953-1214949478 -o /tmp/evaluation-result-1033953-1214949478/solver-1033953-1214949478 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/run -c HOME/instance-1033953-1214949478.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: 0.16 0.03 0.01 4/81 5032
/proc/meminfo: memFree=1613568/2055920 swapFree=4179604/4192956
[pid=5032] ppid=5030 vsize=18572 CPUtime=0
/proc/5032/stat : 5032 (runsolver) R 5030 5032 4917 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 1973898905 19017728 292 996147200 4194304 4296836 548682068496 18446744073709551615 228774702375 0 0 4096 24578 0 0 0 17 1 0 0
/proc/5032/statm: 4643 292 257 25 0 2626 0

[startup+0.0710459 s]
/proc/loadavg: 0.16 0.03 0.01 4/81 5032
/proc/meminfo: memFree=1613568/2055920 swapFree=4179604/4192956
[pid=5032] ppid=5030 vsize=8996 CPUtime=0.05
/proc/5032/stat : 5032 (ld-linux.so.2) R 5030 5032 4917 0 -1 4194304 1836 0 0 0 5 0 0 0 18 0 1 0 1973898905 9211904 1567 996147200 1448431616 1448550632 4294956288 18446744073709551615 4157596714 0 0 4096 0 0 0 0 17 1 0 0
/proc/5032/statm: 2249 1567 330 29 0 1239 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 8996

[startup+0.101051 s]
/proc/loadavg: 0.16 0.03 0.01 4/81 5032
/proc/meminfo: memFree=1613568/2055920 swapFree=4179604/4192956
[pid=5032] ppid=5030 vsize=12296 CPUtime=0.09
/proc/5032/stat : 5032 (ld-linux.so.2) R 5030 5032 4917 0 -1 4194304 2649 0 0 0 8 1 0 0 18 0 1 0 1973898905 12591104 2380 996147200 1448431616 1448550632 4294956288 18446744073709551615 134568173 0 0 4096 0 0 0 0 17 1 0 0
/proc/5032/statm: 3074 2380 330 29 0 2064 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 12296

[startup+0.30109 s]
/proc/loadavg: 0.16 0.03 0.01 4/81 5032
/proc/meminfo: memFree=1613568/2055920 swapFree=4179604/4192956
[pid=5032] ppid=5030 vsize=33812 CPUtime=0.28
/proc/5032/stat : 5032 (ld-linux.so.2) R 5030 5032 4917 0 -1 4194304 8032 0 0 0 25 3 0 0 19 0 1 0 1973898905 34623488 7763 996147200 1448431616 1448550632 4294956288 18446744073709551615 4159185709 0 0 4096 0 0 0 0 17 1 0 0
/proc/5032/statm: 8453 7763 330 29 0 7443 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 33812

[startup+0.701157 s]
/proc/loadavg: 0.16 0.03 0.01 4/81 5032
/proc/meminfo: memFree=1613568/2055920 swapFree=4179604/4192956
[pid=5032] ppid=5030 vsize=36860 CPUtime=0.67
/proc/5032/stat : 5032 (ld-linux.so.2) R 5030 5032 4917 0 -1 4194304 8816 0 0 0 63 4 0 0 23 0 1 0 1973898905 37744640 8547 996147200 1448431616 1448550632 4294956288 18446744073709551615 134544033 0 0 4096 0 0 0 0 17 0 0 0
/proc/5032/statm: 9215 8547 342 29 0 8205 0
Current children cumulated CPU time (s) 0.67
Current children cumulated vsize (KiB) 36860

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

[startup+0.901196 s]
/proc/loadavg: 0.16 0.03 0.01 4/81 5032
/proc/meminfo: memFree=1613568/2055920 swapFree=4179604/4192956
[pid=5032] ppid=5030 vsize=36864 CPUtime=0.87
/proc/5032/stat : 5032 (ld-linux.so.2) R 5030 5032 4917 0 -1 4194304 8820 0 0 0 83 4 0 0 24 0 1 0 1973898905 37748736 8551 996147200 1448431616 1448550632 4294956288 18446744073709551615 134545142 0 0 4096 0 0 0 0 17 0 0 0
/proc/5032/statm: 9216 8551 342 29 0 8206 0
Current children cumulated CPU time (s) 0.87
Current children cumulated vsize (KiB) 36864

Child status: 0
Real time (s): 0.913589
CPU time (s): 0.896863
CPU user time (s): 0.845871
CPU system time (s): 0.050992
CPU usage (%): 98.1692
Max. virtual memory (cumulated for all children) (KiB): 36864

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

runsolver used 0.004999 second user time and 0.009998 second system time

The end

Launcher Data (download as text)

Begin job on node74 at 2008-07-01 23:57:58
IDJOB=1033953
IDBENCH=53315
IDSOLVER=328
FILE ID=node74/1033953-1214949478
PBS_JOBID= 7870187
Free space on /tmp= 103212 MiB

SOLVER NAME= spider 2008-06-14
BENCH NAME= CPAI08/csp/driver/normalized-driverlogw-02c-sat_ext.xml
COMMAND LINE= HOME/run -c BENCHNAME
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1033953-1214949478/watcher-1033953-1214949478 -o /tmp/evaluation-result-1033953-1214949478/solver-1033953-1214949478 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/run -c HOME/instance-1033953-1214949478.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 8940ec32450c33705b342604bcff6d69
RANDOM SEED=1835042181

node74.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.259
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.259
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:       1614048 kB
Buffers:         24804 kB
Cached:         272312 kB
SwapCached:       6640 kB
Active:         117920 kB
Inactive:       253380 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1614048 kB
SwapTotal:     4192956 kB
SwapFree:      4179604 kB
Dirty:            3952 kB
Writeback:           0 kB
Mapped:          90560 kB
Slab:            55640 kB
Committed_AS:  4618112 kB
PageTables:       1980 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 103216 MiB
End job on node74 at 2008-07-01 23:57:59