Trace number 315421

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, and are wall clock time (not CPU 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
ranov 2007-02-08? (exit code) 0.041993 0.0422399

General information on the benchmark

Nameindustrial/palacios/uts/
uts-l06-ipc5-h30-unknown.cnf
MD5SUMfad87308d3751e996b7b3c35a13a7fd9
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark30.2494
Satisfiable
(Un)Satisfiability was proved
Number of variables137341
Number of clauses724504
Sum of the clauses size1900318
Maximum clause length591
Minimum clause length1
Number of clauses of size 1276
Number of clauses of size 2588905
Number of clauses of size 3130263
Number of clauses of size 41197
Number of clauses of size 5111
Number of clauses of size over 53752

Solver Data (download as text)

0.01/0.03	c ERROR - clause too long
0.01/0.03	c +------------------------------+
0.01/0.03	c | R+AdaptNovelty+, version 1.5 |
0.01/0.03	c +------------------------------+
0.01/0.03	c ranov -h for help
0.01/0.03	c

Verifier Data (download as text)

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer:

Watcher Data (download as text)

runsolver version 3.2.1 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node42/watcher-315421-1172653813 -o ROOT/results/node42/solver-315421-1172653813 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/315421-1172653813/ranov /tmp/evaluation/315421-1172653813/instance-315421-1172653813.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 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.91 0.97 0.99 3/64 25592
/proc/meminfo: memFree=1080224/2055920 swapFree=4183440/4192956
[pid=25592] ppid=25590 vsize=319884 CPUtime=0
/proc/25592/stat : 25592 (ranov) R 25590 25592 24639 0 -1 4194304 872 0 0 0 0 0 0 0 18 0 1 0 285337341 327561216 857 18446744073709551615 134512640 134914624 4294956640 18446744073709551615 134528292 0 0 4096 0 0 0 0 17 1 0 0
/proc/25592/statm: 79971 865 30 98 0 79870 0

[startup+0.026167 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 25592
/proc/meminfo: memFree=1080224/2055920 swapFree=4183440/4192956
[pid=25592] ppid=25590 vsize=319884 CPUtime=0.01
/proc/25592/stat : 25592 (ranov) R 25590 25592 24639 0 -1 4194304 4841 0 0 0 0 1 0 0 18 0 1 0 285337341 327561216 4826 18446744073709551615 134512640 134914624 4294956640 18446744073709551615 134528292 0 0 4096 0 0 0 0 17 1 0 0
/proc/25592/statm: 79971 4833 30 98 0 79870 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 319884

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

[startup+0.026167 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 25592
/proc/meminfo: memFree=1080224/2055920 swapFree=4183440/4192956
[pid=25592] ppid=25590 vsize=319884 CPUtime=0.01
/proc/25592/stat : 25592 (ranov) R 25590 25592 24639 0 -1 4194304 4841 0 0 0 0 1 0 0 18 0 1 0 285337341 327561216 4826 18446744073709551615 134512640 134914624 4294956640 18446744073709551615 134528292 0 0 4096 0 0 0 0 17 1 0 0
/proc/25592/statm: 79971 4833 30 98 0 79870 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 319884

Child status: 255
Real time (s): 0.0422399
CPU time (s): 0.041993
CPU user time (s): 0.017997
CPU system time (s): 0.023996
CPU usage (%): 99.4155
Max. virtual memory (cumulated for all children) (KiB): 319884

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.017997
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= 5009
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= 8
involuntary context switches= 1

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node42 on Wed Feb 28 09:10:13 UTC 2007

IDJOB= 315421
IDBENCH= 20416
IDSOLVER= 105
FILE ID= node42/315421-1172653813

PBS_JOBID= 3981189

Free space on /tmp= 66496 MiB

SOLVER NAME= ranov 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/industrial/palacios/uts/uts-l06-ipc5-h30-unknown.cnf
COMMAND LINE= /tmp/evaluation/315421-1172653813/ranov /tmp/evaluation/315421-1172653813/instance-315421-1172653813.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node42/watcher-315421-1172653813 -o ROOT/results/node42/solver-315421-1172653813 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/315421-1172653813/ranov /tmp/evaluation/315421-1172653813/instance-315421-1172653813.cnf            

META MD5SUM SOLVER= f62d3053d967228316972e47f5f50e74
MD5SUM BENCH=  fad87308d3751e996b7b3c35a13a7fd9

RANDOM SEED= 427797305

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node42.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.261
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.261
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:       1080696 kB
Buffers:         42256 kB
Cached:         865492 kB
SwapCached:       3792 kB
Active:         315104 kB
Inactive:       616380 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1080696 kB
SwapTotal:     4192956 kB
SwapFree:      4183440 kB
Dirty:           13964 kB
Writeback:           0 kB
Mapped:          29152 kB
Slab:            29744 kB
Committed_AS:   952460 kB
PageTables:       1448 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= 66496 MiB

End job on node42 on Wed Feb 28 09:10:13 UTC 2007