9
4%
master: 4%

Ran 27 Jan 2020 04:38PM UTC

Files 638

Run time 2min

Badge

Embed ▾

Committed 27 Jan 2020 04:04PM UTC coverage: 61.218% (+0.001%) from 61.217%

Job # TEST_SUITES=testbugfix CONFIGFLAGS="--enable-memory-checking"

Build Type

push

travis-ci

Committed by

fingolfin

Commit Message

julia: remove the need for GAPTypes.jl

... by doing something moderately evil: If GAP is loaded before Julia, we
create the Julia type `ForeignGAP.MPtr` *without* a super type. Then once
Julia is loaded, and the type `GAP.GapObj` has been created, GAP.jl calls the
new function `GAP_register_GapObj` with this type as argument, and we patch
`ForeignGAP.MPtr` to have `GAP.GapObj` as supertype.

This seems to work well in practice and ought to be safe, as prior to the
moment were we change the super type, no Julia code beyond the Julia GC should
have ever "seen" `ForeignGAP.MPtr` or any instances of it, and hence no
internal data structures of the Julia runtime that might get into an invalid
state due to our change (e.g. anything related to method dispatch) should
reference it.

Also, *don't* set `GapObj` as supertype for `ForeignGAP.Bag` and
`ForeignGAP.LargeBag`, doing that was IMHO simply a mistake. In practice it
should not have mattered so far, as no regular Julia code ever touches
instances of these types directly. This might change in the future though, if
we introduce Julia wrapper objects for GAP objects that directly access their
underlying bits, instead of going through libgap APIs.

Run Details

176892 of 288955 relevant lines covered (61.22%)

2503846.26 hits per line

gap-system / gap / 11403 / 9
4%
master: 4%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 11403.9 (TEST_SUITES=testbugfix CONFIGFLAGS="--enable-memory-checking")

gap-system / gap / 11403 / 9 4% master: 4%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 11403.9 (TEST_SUITES=testbugfix CONFIGFLAGS="--enable-memory-checking")

gap-system / gap / 11403 / 9
4%
master: 4%

README BADGES
x