10
49%
master: 49%

Ran 28 Aug 2019 12:45PM UTC

Files 79

Run time 7s

Badge

Embed ▾

Committed 28 Aug 2019 12:26PM UTC coverage: 47.218% (-0.03%) from 47.25%

Job # CI_TARGET=coverage-parvorm

Build Type

push

travis-ci

Committed by Takahiro Ueda

Commit Message

Fix a problem with tablebases with larger numbers of namesblocks

The newly created larger array was not swapped with the old array.
This caused lots of invalid array accesses and, sometimes, an fseek
to an undefined location resulting in incorrectly sized output files.
See Issue #318 .

Also when comparing contents the block under consideration was not
correctly updated. This caused valgrind to report an Illegal write.
I have not found any actual runtime issues caused by this.

Could this be the cause of an old issue from the forum, where I
described how FORM writes a really enormous amount of data to disk
when creating relatively small tablebase files? For this reason it
is a very bad idea to create a tablebase directly in a network
directory.

Run Details

31206 of 66089 relevant lines covered (47.22%)

130341.68 hits per line

vermaseren / form / 304 / 10
49%
master: 49%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 304.10 (CI_TARGET=coverage-parvorm)

vermaseren / form / 304 / 10 49% master: 49%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 304.10 (CI_TARGET=coverage-parvorm)

vermaseren / form / 304 / 10
49%
master: 49%

README BADGES
x