Trace number 315461

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.042993 0.0448529

General information on the benchmark

Nameindustrial/palacios/uts/
uts-l06-ipc5-h32-unknown.cnf
MD5SUM31ebf23e42c2af5eeb4e8b1cb1366a0c
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark67.3348
Satisfiable
(Un)Satisfiability was proved
Number of variables161116
Number of clauses800163
Sum of the clauses size2079881
Maximum clause length591
Minimum clause length1
Number of clauses of size 1276
Number of clauses of size 2640925
Number of clauses of size 3153402
Number of clauses of size 41419
Number of clauses of size 5124
Number of clauses of size over 54017

Solver Data (download as text)

0.00/0.04	c ERROR - clause too long
0.00/0.04	c +------------------------------+
0.00/0.04	c | R+AdaptNovelty+, version 1.5 |
0.00/0.04	c +------------------------------+
0.00/0.04	c ranov -h for help
0.00/0.04	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/node4/watcher-315461-1172654358 -o ROOT/results/node4/solver-315461-1172654358 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/315461-1172654358/ranov /tmp/evaluation/315461-1172654358/instance-315461-1172654358.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.92 0.97 0.97 3/77 1999
/proc/meminfo: memFree=877472/2055920 swapFree=4192812/4192956
[pid=1999] ppid=1997 vsize=319884 CPUtime=0
/proc/1999/stat : 1999 (ranov) R 1997 1999 1561 0 -1 4194304 884 0 0 0 0 0 0 0 18 0 1 0 285390697 327561216 870 18446744073709551615 134512640 134914624 4294956624 18446744073709551615 134528292 0 0 4096 0 0 0 0 17 1 0 0
/proc/1999/statm: 79971 877 30 98 0 79870 0

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

Child status: 255
Real time (s): 0.0448529
CPU time (s): 0.042993
CPU user time (s): 0.024996
CPU system time (s): 0.017997
CPU usage (%): 95.8533
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.024996
system time used= 0.017997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5020
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.003999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node4 on Wed Feb 28 09:19:18 UTC 2007

IDJOB= 315461
IDBENCH= 20417
IDSOLVER= 105
FILE ID= node4/315461-1172654358

PBS_JOBID= 3980949

Free space on /tmp= 66502 MiB

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

META MD5SUM SOLVER= f62d3053d967228316972e47f5f50e74
MD5SUM BENCH=  31ebf23e42c2af5eeb4e8b1cb1366a0c

RANDOM SEED= 200845812

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node4.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.231
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.231
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:        877880 kB
Buffers:         37664 kB
Cached:        1018308 kB
SwapCached:          0 kB
Active:         220432 kB
Inactive:       895200 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        877880 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           15404 kB
Writeback:           0 kB
Mapped:          78584 kB
Slab:            47936 kB
Committed_AS:  1138128 kB
PageTables:       1768 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= 66502 MiB

End job on node4 on Wed Feb 28 09:19:19 UTC 2007