[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#964613: liborcus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2



tag 964613 + pending
retitle 964613 liborcus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 when built with mdds 1.6.0
thanks

Hi,

On Thu, Jul 16, 2020 at 10:08:30PM +0300, Dmitry Shachnev wrote:
> On Thu, Jul 09, 2020 at 01:01:01PM +0200, Lucas Nussbaum wrote:
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> > Relevant part (hopefully):
> > > make[6]: Entering directory '/<<PKGBUILDDIR>>/src/python'
> > > PASS: ../../test/python/json.py
> > > PASS: ../../test/python/module.py
> > > ../../test-driver: line 107:  6642 Segmentation fault      "$@" > $log_file 2>&1
> > > FAIL: ../../test/python/csv_export.py
> > > ../../test-driver: line 107:  6639 Segmentation fault      "$@" > $log_file 2>&1
> > > FAIL: ../../test/python/csv.py
> > > ../../test-driver: line 107:  6669 Segmentation fault      "$@" > $log_file 2>&1
> > > FAIL: ../../test/python/ods.py
> > > ../../test-driver: line 107:  6665 Segmentation fault      "$@" > $log_file 2>&1
> > > FAIL: ../../test/python/xlsx.py
> > > ../../test-driver: line 107:  6668 Segmentation fault      "$@" > $log_file 2>&1
> > > FAIL: ../../test/python/xls_xml.py
> > > ../../test-driver: line 107:  6678 Segmentation fault      "$@" > $log_file 2>&1
> > > FAIL: ../../test/python/gnumeric.py
> 
> The crash is probably related to mdds 1.6.0 which recently reached unstable.
> 
> It is happening in /usr/include/mdds-1.5/mdds/multi_type_vector_itr.hpp:163,
> when dereferencing blk.mp_data pointer (which is invalid, like 0x1 or 0x3).

Hrm. That mail never appared in my mbox... (Probably because the ML
filtered it out because of the attachement?)

Anyway, this still fails also with mdds 1.7.0 which just entered unstable.

It *does* work though with liborcus 0.16.0 which I just uploaded to NEW,
so we probably should upload that one to unstable ASAP if it cleared NEW
(and transition LO to it, upstream it's only in the tree for 7.1.0 which
is unfortunately too late for bullseye.)

Regards,

Rene


Reply to: