Trace number 355659

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
Rsat 2007-02-08? (exit code) 0.037993 0.0402589

General information on the benchmark

Nameindustrial/jarvisalo/
eq.atree.braun.7.unsat.cnf
MD5SUM39c753fcd6ac15019fa3a40cd8b8f69d
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.78973
Satisfiable
(Un)Satisfiability was proved
Number of variables505
Number of clauses1696
Sum of the clauses size4422
Maximum clause length13
Minimum clause length1
Number of clauses of size 13
Number of clauses of size 2719
Number of clauses of size 3948
Number of clauses of size 410
Number of clauses of size 510
Number of clauses of size over 56

Solver Data (download as text)

0.00/0.00	c Parsing...
0.00/0.00	c ==============================================================================
0.00/0.00	c |           |     ORIGINAL     |              LEARNT              |          |
0.00/0.00	c | Conflicts | Clauses Literals |   Limit Clauses Literals  Lit/Cl | Progress |
0.00/0.00	c ==============================================================================
0.00/0.00	c |         0 |    1693     4419 |     507       0        0     nan |  0.000 % |
0.00/0.01	c |         0 |    1409     4243 |      --       0       --      -- |     --   | -258/-121
0.00/0.01	c ==============================================================================
0.00/0.01	c Result  :   #vars: 341   #clauses: 1409   #literals: 4243
0.00/0.01	c CPU time:   0.007998 s
0.00/0.01	c ==============================================================================
0.00/0.01	c Rsat version 2.00
0.00/0.03	*** glibc detected *** free(): invalid next size (fast): 0x0813a110 ***
0.00/0.03	/tmp/evaluation/355659-1176784450/rsat.sh: line 39: 10051 Aborted                 (core dumped) $RS $TMP.cnf -r $TMP.result

Verifier Data (download as text)

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

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node74/watcher-355659-1176784450 -o ROOT/results/node74/solver-355659-1176784450 -C 10000 -W -M --output-limit 1,15 /tmp/evaluation/355659-1176784450/rsat.sh /tmp/evaluation/355659-1176784450/instance-355659-1176784450.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 10000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 10030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 0 seconds
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.73 0.93 0.98 3/66 10048
/proc/meminfo: memFree=1724232/2055920 swapFree=4183056/4192956
[pid=10048] ppid=10046 vsize=5352 CPUtime=0
/proc/10048/stat : 10048 (rsat.sh) S 10046 10048 9992 0 -1 4194304 283 0 0 0 0 0 0 0 18 0 1 0 126359774 5480448 232 18446744073709551615 4194304 4889804 548682069296 18446744073709551615 228774699844 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/10048/statm: 1338 232 195 169 0 49 0
[pid=10049] ppid=10048 vsize=820 CPUtime=0
/proc/10049/stat : 10049 (SatElite) R 10048 10048 9992 0 -1 4194304 147 0 0 0 0 0 0 0 20 0 1 0 126359775 839680 129 18446744073709551615 134512640 135038345 4294956736 18446744073709551615 134574928 0 0 4096 3 0 0 0 17 1 0 0
/proc/10049/statm: 205 132 67 128 0 74 0

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

Child status: 134
Real time (s): 0.0402589
CPU time (s): 0.037993
CPU user time (s): 0.030995
CPU system time (s): 0.006998
CPU usage (%): 94.3717
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.030995
system time used= 0.006998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 845
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= 27
involuntary context switches= 3

runsolver used 0.002999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node74 on Tue Apr 17 04:34:10 UTC 2007

IDJOB= 355659
IDBENCH= 20469
IDSOLVER= 169
FILE ID= node74/355659-1176784450

PBS_JOBID= 4580855

Free space on /tmp= 103226 MiB

SOLVER NAME= Rsat 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/industrial/jarvisalo/eq.atree.braun.7.unsat.cnf
COMMAND LINE= /tmp/evaluation/355659-1176784450/rsat.sh /tmp/evaluation/355659-1176784450/instance-355659-1176784450.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node74/watcher-355659-1176784450 -o ROOT/results/node74/solver-355659-1176784450 -C 10000 -W  -M  --output-limit 1,15  /tmp/evaluation/355659-1176784450/rsat.sh /tmp/evaluation/355659-1176784450/instance-355659-1176784450.cnf            

META MD5SUM SOLVER= d41d8cd98f00b204e9800998ecf8427e
MD5SUM BENCH=  39c753fcd6ac15019fa3a40cd8b8f69d

RANDOM SEED= 24281818

TIME LIMIT= 10000 seconds
MEMORY LIMIT=  MiB

Linux node74.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.213
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.213
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:       1724704 kB
Buffers:         28904 kB
Cached:         251508 kB
SwapCached:       3760 kB
Active:         178844 kB
Inactive:       111836 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1724704 kB
SwapTotal:     4192956 kB
SwapFree:      4183056 kB
Dirty:            1900 kB
Writeback:           0 kB
Mapped:          15540 kB
Slab:            26352 kB
Committed_AS:  1939244 kB
PageTables:       1480 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= 103226 MiB

End job on node74 on Tue Apr 17 04:34:10 UTC 2007