Bug#877419: pandas FTBFS on !x86/ppc64el: test failures

Hi I refreshed and re-enabled Andreas' mark_tests_working_on_intel.patch [1] which was disabled in 0.22.0-1. I additionally marked test_sum_nanops_timedelta and test_timedelta_ops_with_missing_values with pytest.mark.intel which were failing at least on arm64. To address a new failure on

Bug#889539: marked as done (pandas FTBFS: test failures)

Your message dated Thu, 12 Apr 2018 17:36:12 +0200 with message-id <4a41bea5-add7-ce06-5d52-41f3d08cd...@debian.org> and subject line Re: pandas FTBFS: test failures has caused the Debian Bug report #889539, regarding pandas FTBFS: test failures to be marked as done. This means that you

Bug#895506: apertium-swe-nor FTBFS: test failure

Source: apertium-swe-nor Version: 0.2.0~r69544-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-swe-nor.html ... dh_auto_test -O--fail-missing make -j1 test VERBOSE=1 make[1]: Entering directory '/build/1st/apertium-swe-nor-0.2.0~r69544

Bug#888733: hyantesite FTBFS on most architectures: test failures

causing the upstream test suite to be run at build for the first time. If I run dh_auto_test in the previous version of the package, it fails in the same way. Thus this is not a regression in the software on these architectures, only a regression in buildability because the build now detects

Bug#893899: ITP: r-cran-libcoin -- GNU R linear test statistics for permutation inference

: GPL Programming Lang: GNU R Description : GNU R linear test statistics for permutation inference Basic infrastructure for linear test statistics and permutation inference in the framework of Strasser and Weber (1999) <http://epub.wu.ac.at/102/>. This package must not be used b

Bug#892019: marked as done (python-meshio: Installs test files to /usr/lib/python3/dist-packages)

Your message dated Thu, 08 Mar 2018 21:06:31 + with message-id <e1eu2kb-00015p...@fasolo.debian.org> and subject line Bug#892019: fixed in python-meshio 1.11.7-2 has caused the Debian Bug report #892019, regarding python-meshio: Installs test files to /usr/lib/python3/dist-pa

Bug#892288: arrayfire FTBFS on i386: test segfaults

Source: arrayfire Version: 3.3.2+dfsg1-4 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/arrayfire.html ... 98% tests passed, 2 tests failed out of 95 Total Test time (real) = 53.16 sec The following tests FAILED: 4

Bug#892019: python-meshio: Installs test files to /usr/lib/python3/dist-packages

test files to /usr/lib/python3/dist-packages, for example: /usr/lib/python3/dist-packages/test.med Patch attached. These were found as the files vary between runs. [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org

Bug#889539: pandas FTBFS: test failures

Yaroslav has just uploaded pandas 0.22.0, let's see if this problem still exists. On 7 February 2018 at 14:57, Andreas Tille wrote: > On Tue, Feb 06, 2018 at 03:51:27PM +, Lumin wrote: >> Apart from that, the pandas packaging needs a patch [2] to reduce >> autopkgtest

test

tst -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#888879: marked as done (rheolef FTBFS on several architectures: test runs forever)

Your message dated Sun, 18 Feb 2018 16:36:56 + with message-id <e1enrxq-000cnx...@fasolo.debian.org> and subject line Bug#79: fixed in rheolef 6.7-6 has caused the Debian Bug report #79, regarding rheolef FTBFS on several architectures: test runs forever to be marked a

Bug#888912: sagemath test failures with mpfr 4.0.0 and several architectures

Not a surprise as long as some dependencies are built against libmpfr4. It looks like all dependencies are now rebuilt against libmpfr6 but sagemath is still failing. https://buildd.debian.org/status/fetch.php?pkg=sagemath=amd64=8.1-2%2Bb2=1517950645=0 -- debian-science-maintainers mailing

Bug#883757: marked as done (ignition-transport: Includes "test/gtest/cmake/internal_utils.cmake" listed in Files-Excluded header)

Your message dated Fri, 09 Feb 2018 11:01:51 + with message-id <e1ek6rd-000dls...@fasolo.debian.org> and subject line Bug#883757: fixed in ignition-transport 4.0.0+dfsg-1 has caused the Debian Bug report #883757, regarding ignition-transport: Includes "test/gtest/cmake/internal_

Bug#889539: pandas FTBFS: test failures

On Tue, Feb 06, 2018 at 03:51:27PM +, Lumin wrote: > Apart from that, the pandas packaging needs a patch [2] to reduce > autopkgtest failures. As always: Please push your patches. :-) You and I are in the same position: We are team members of the maintainer team. I even have the strong

Bug#889539: pandas FTBFS: test failures

s that might be useful: https://stackoverflow.com/questions/40659212/futurewarning-elementwise-comparison-failed-returning-scalar-but-in-the-futur https://stackoverflow.com/questions/15777951/how-to-suppress-pandas-future-warning I noticed these lines [1] in the test log. The failures seem to be

Bug#888911: marked as done (giac test failures with mpfr 4.0.0 on several architectures)

Your message dated Tue, 6 Feb 2018 15:24:32 +0100 with message-id <f9d9d137-12e2-eaca-693c-3feaa27e1...@debian.org> and subject line Re: giac test failures with mpfr 4.0.0 on several architectures has caused the Debian Bug report #888911, regarding giac test failures with mpfr 4.0.0 on s

Bug#889539: pandas FTBFS: test failures

Hi Lumin, you did a really good job on latest pandas issues. Do you think you can have a look at this problem as well? BTW, to upgrade pandas to the latest upstream version python-moto is needed. I prepared the packaging (#777089) and may be there is only a minor issue to finalise this (see

Bug#888879: rheolef FTBFS on several architectures: test runs forever

Hi Pierre, as I mentioned on Debian Science maintainers list[1] this problem does not come unexpected. Pierre, could you please confirm whether you keep on maintaining this package and will check this issue? >From my uneducated perspective the test failures always existed but the test w

Bug#871208: marked as done (python-xarray: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.6 3.5" returned exit code 13)

Your message dated Sun, 04 Feb 2018 12:36:18 + with message-id <e1eijws-j6...@fasolo.debian.org> and subject line Bug#871208: fixed in python-xarray 0.9.6-1 has caused the Debian Bug report #871208, regarding python-xarray: FTBFS: dh_auto_test: pybuild --test --test-pytest -i

Bug#889539: pandas FTBFS: test failures

Source: pandas Version: 0.20.3-11 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pandas.html ... === FAILURES === TestDataFramePlots.test_boxplot_legacy

Processed: Re: Bug#888912: sagemath test failures with mpfr 4.0.0 and several architectures

Processing control commands: > block -1 by 888459 888911 Bug #888912 [src:sagemath] sagemath test failures with mpfr 4.0.0 and several architectures 888912 was not blocked by any bugs. 888912 was not blocking any bugs. Added blocking bug(s) of 888912: 888459 and 888911 -- 888912: ht

Bug#888912: sagemath test failures with mpfr 4.0.0 and several architectures

Package: src:sagemath Version: 8.2-1 Severity: serious Tags: sid buster see https://buildd.debian.org/status/package.php?p=sagemath=unstable test failures on every architecture. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http

Bug#888911: giac test failures with mpfr 4.0.0 on several architectures

Package: src:giac Version: 1.2.3.57+dfsg1-2 Severity: serious Tags: sid buster see https://buildd.debian.org/status/package.php?p=giac failing tests at least on the release architectures amd64 and armhf. -- debian-science-maintainers mailing list

Bug#888879: rheolef FTBFS on several architectures: test runs forever

Source: rheolef Version: 6.7-5 Severity: serious https://buildd.debian.org/status/package.php?p=rheolef=sid ... mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 left >/dev/null 2>/dev/null mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2

Bug#888733: hyantesite FTBFS on most architectures: test failures

Source: hyantesite Version: 1.3.0-2 Severity: serious hyantesite FTBFS on most architectures with varying test failures: https://buildd.debian.org/status/package.php?p=hyantesite -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http

Bug#881870: marked as done (normaliz: FTBFS on alpha: recipe for target 'test-v/medium.diff' failed)

Your message dated Fri, 26 Jan 2018 06:19:42 + with message-id <e1eexmu-000eub...@fasolo.debian.org> and subject line Bug#881870: fixed in normaliz 3.5.1+ds-4 has caused the Debian Bug report #881870, regarding normaliz: FTBFS on alpha: recipe for target 'test-v/medium.diff'

Bug#884294: marked as done (pandas FTBFS: test failure)

Your message dated Sun, 21 Jan 2018 09:50:00 + with message-id <e1edcgg-0006vs...@fasolo.debian.org> and subject line Bug#884294: fixed in pandas 0.20.3-11 has caused the Debian Bug report #884294, regarding pandas FTBFS: test failure to be marked as done. This means that you

Bug#884083: marked as done (ignition-math2: Source includes "test/gtest/include/gtest/gtest.h" etc. listed in Files-Excluded header)

Your message dated Sat, 13 Jan 2018 00:04:28 + with message-id <e1ea9je-000j8l...@fasolo.debian.org> and subject line Bug#884083: fixed in ignition-math2 2.9.0+dfsg1-1 has caused the Debian Bug report #884083, regarding ignition-math2: Source includes "test/gtest/include/gtest/gt

Bug#884294: pandas FTBFS: test failure

Source: pandas Version: 0.20.3-10 Severity: serious Some recent change in unstable makes pandas FTBFS: https://tests.reproducible-builds.org/debian/history/pandas.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pandas.html ... === FAILURES

Bug#884083: ignition-math2: Source includes "test/gtest/include/gtest/gtest.h" etc. listed in Files-Excluded header

Source: ignition-math2 Version: 2.8.0-4 Severity: important User: la...@debian.org Usertags: files-excluded Dear Maintainer, ignition-math2 lists "test/gtest" in the Files-Excluded field in debian/copyright but the source tree contains test/gtest/include/gtest/gtest.h etc. This might

Bug#883757: ignition-transport: Includes "test/gtest/cmake/internal_utils.cmake" listed in Files-Excluded header

Source: ignition-transport Version: 1.3.0-5 Severity: serious User: la...@debian.org Usertags: files-excluded Dear Maintainer, ignition-transport lists "test/gtest" in the Files-Excluded field in debian/copyright but the source tree contains test/gtest/cmake/internal_u

Bug#876870: marked as done (apertium-en-es FTBFS with apertium 3.4.2~r68466-2: test failure)

Your message dated Thu, 07 Dec 2017 09:33:51 + with message-id <e1emsyx-00064j...@fasolo.debian.org> and subject line Bug#876870: fixed in apertium-en-es 0.8.0~r57502-3 has caused the Debian Bug report #876870, regarding apertium-en-es FTBFS with apertium 3.4.2~r68466-2: test f

Bug#883114: admesh FTCBFS: fails running test suite despite DEB_BUILD_OPTIONS=nocheck

Source: admesh Version: 0.98.3-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap admesh fails to cross build from source, because it fails running its test suite even though the build was performed with DEB_BUILD_OPTIONS=nocheck. After honouring the option, admesh cross builds

Bug#882420: marked as done (segyio: FTBFS on s390x: Assertion failed in file: /<>/lib/test/segy.c on line: 547)

Your message dated Sat, 25 Nov 2017 15:11:33 + with message-id <e1eic7b-000gsz...@fasolo.debian.org> and subject line Bug#882420: fixed in segyio 1.3.8-1 has caused the Debian Bug report #882420, regarding segyio: FTBFS on s390x: Assertion failed in file: /<>/lib/test/segy.c

Bug#881453: marked as done (primesieve FTBFS on i386: test failures)

Your message dated Fri, 24 Nov 2017 15:07:19 + with message-id <e1eifzx-0004hb...@fasolo.debian.org> and subject line Bug#881453: fixed in primesieve 6.3+ds-1 has caused the Debian Bug report #881453, regarding primesieve FTBFS on i386: test failures to be marked as done. This means th

Bug#882420: segyio: FTBFS on s390x: Assertion failed in file: /<>/lib/test/segy.c on line: 547

From: Aaron M. Ucko <u...@debian.org> Sent: Wednesday, November 22, 2017 5:39 PM To: Debian Bug Tracking System Subject: Bug#882420: segyio: FTBFS on s390x: Assertion failed in file: /<>/lib/test/segy.c on line: 547 Source: segyio Version: 1.3.3-1 Severity: important Tags: upstream J

Bug#882420: segyio: FTBFS on s390x: Assertion failed in file: /<>/lib/test/segy.c on line: 547

=segyio=s390x=1.3.3-1=1511256490=0: 1/17 Test #1: c.segy ...***Failed0.00 sec Assertion failed in file: /<>/lib/test/segy.c on line: 547 Expected: 4.24, Actual: 4.24, diff: 0.00, eps: 0.00 starting interpret file read inline 4 Could you

Bug#881869: marked as done (FTBFS: recipe for target 'test-/5x5PF.diff' failed)

Your message dated Fri, 17 Nov 2017 17:35:23 + with message-id <e1efkxz-0003w2...@fasolo.debian.org> and subject line Bug#881869: fixed in normaliz 3.4.1+ds-2 has caused the Debian Bug report #881869, regarding FTBFS: recipe for target 'test-/5x5PF.diff' failed to be marked a

Bug#881869: FTBFS: recipe for target 'test-/5x5PF.diff' failed

Dear Aaron M. Ucko, thanks for your report. I have already filled an issue about it: https://github.com/Normaliz/Normaliz/issues/161 I hope it will be fixed quickly. Cheers, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net

Bug#881870: normaliz: FTBFS on alpha: recipe for target 'test-v/medium.diff' failed

: /<>/normaliz-3.4.1+ds/_build/../test/Makefile.classic:52: recipe for target 'test-v/medium.diff' failed As with #881869, I don't know what the diff turned out to read, but perhaps you can reproduce the problem on a porter box. Could you please take a look? Thanks! -- Aaron M. Ucko,

Bug#881869: FTBFS: recipe for target 'test-/5x5PF.diff' failed

architectures powerpc and ppc64 (but for some reason not powerpcspe) have been failing: /<>/normaliz-3.4.1+ds/_build/../test/Makefile.classic:52: recipe for target 'test-/5x5PF.diff' failed I don't know what the diff turned out to read (or even whether it's the same on all of these archite

Processed: Re: sagenb-export: FTBFS: Test failures

Processing control commands: > reassign -1 src:testpath Bug #880241 [src:sagenb-export] sagenb-export: FTBFS: Test failures Bug reassigned from package 'src:sagenb-export' to 'src:testpath'. No longer marked as found in versions sagenb-export/3.2-3. Ignoring request to alter fixed versions of

Bug#880241: sagenb-export: FTBFS: Test failures

Control: reassign -1 src:testpath Control: retitle -1 testpath does not install .egg-info or .dist-info, making it invisible to pip Control: affects -1 sagenb-export The sagenb-export FTBFS is caused by the python "testpath" module not installing a .egg-info file (or .dist-info directory) which

Bug#880147: cvc4: FTBFS on sparc64: bus error => massive test suite failure

Source: cvc4 Version: 1.5-1 Severity: important Tags: upstream Justification: fails to build from source User: debian-sp...@lists.debian.org The build of cvc4 for sparc64 (admittedly not a release architecture) encountered even more test suite failures than other non-x86 builds, as detailed

Bug#880146: cvc4: FTBFS on non-x86: test suite errors

Source: cvc4 Version: 1.5-1 Severity: important Tags: upstream Justification: fails to build from source All non-x86 builds of cvc4 to date have failed with test suite errors, as detailed at https://buildd.debian.org/status/logs.php?pkg=cvc4=1.5-1 So far, these errors have occurred on arm64

Bug#870217: marked as done (glm: FTBFS with gcc-7: Test failures)

Your message dated Tue, 24 Oct 2017 14:49:38 + with message-id <e1e70wq-000fbg...@fasolo.debian.org> and subject line Bug#870217: fixed in glm 0.9.8.4-1.1 has caused the Debian Bug report #870217, regarding glm: FTBFS with gcc-7: Test failures to be marked as done. This means that you

Bug#876890: marked as done (scalapack FTBFS on arm64: test failures)

Your message dated Fri, 29 Sep 2017 14:52:15 +0800 with message-id <1506667935.28469.3.ca...@debian.org> and subject line Re: scalapack FTBFS on arm64: test failures has caused the Debian Bug report #876890, regarding scalapack FTBFS on arm64: test failures to be marked as done. This

Bug#876890: scalapack FTBFS on arm64: test failures

On Thu, 28 Sep 2017 15:28:11 +0800 Drew Parsons <dpars...@debian.org> wrote: > > The actual FTBFS is from the openmpi test: > > OpenMPI tests failed: >20 - dpb2tim (Failed) > A test build on the porterbox succeeded. The failure in your test must have been a tr

Bug#876890: scalapack FTBFS on arm64: test failures

tory/scalapack.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sc alapack.html > > ... > The following tests FAILED: > 1 - xCbtest (Failed) > 2 - xFbtest (Failed) >75 - xssvd (Failed) > 76 - xdsvd (Failed) ... These are the mpich te

Bug#876890: scalapack FTBFS on arm64: test failures

) 83 - xcgsep (Failed) 84 - xzgsep (Failed) 91 - xssyevr (Failed) 92 - xdsyevr (Failed) 93 - xcheevr (Failed) 94 - xzheevr (Failed) Errors while running CTest Makefile:143: recipe for target 'test' failed make[2]: *** [test] Error 8 -- debian

Bug#876870: apertium-en-es FTBFS with apertium 3.4.2~r68466-2: test failure

Source: apertium-en-es Version: 0.8.0~r57502-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-en-es.html ... dh_auto_test -O--fail-missing make -j1 test VERBOSE=1 make[1]: Entering directory '/build/1st/apertium-en-es

Bug#875671: marked as done (fix test dependencies)

Your message dated Wed, 13 Sep 2017 21:24:13 + with message-id <e1dsf8n-000bjm...@fasolo.debian.org> and subject line Bug#875671: fixed in lapack 3.7.1-4 has caused the Debian Bug report #875671, regarding fix test dependencies to be marked as done. This means that you claim that the p

Bug#875671: fix test dependencies

Package: src:lapack Version: 3.7.1-3 Tags: patch dpkg-dev expects gcc ... http://launchpadlibrarian.net/336816854/lapack_3.7.1-3ubuntu1_3.7.1-3ubuntu2.diff.gz -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#873008: hfst FTBFS on big endian: FAIL: test

On Thu, 2017-09-07 at 08:44 +0200, Tino Didriksen wrote: > It's one out of a hundred tests that fails. Sounds like that particular test should have its result ignored on big-endian platforms since the code isn't written in a portable manner. Disabling or ignoring all the tests isn't appropri

Bug#873008: hfst FTBFS on big endian: FAIL: test

On 7 September 2017 at 03:15, Paul Wise wrote: > Why do the tests for hfst need to be disabled? > > I think it would be better to keep them enabled so that we can ensure > that hfst works correctly. Broken binaries are worse than FTBFS. You > can ask for removal of the existing

Bug#873008: marked as done (hfst FTBFS on big endian: FAIL: test)

Your message dated Thu, 07 Sep 2017 05:04:38 + with message-id <e1dpozw-0003tq...@fasolo.debian.org> and subject line Bug#873008: fixed in hfst 3.12.2~r3289-2 has caused the Debian Bug report #873008, regarding hfst FTBFS on big endian: FAIL: test to be marked as done. This means th

Bug#867987: marked as done (h5py: FTBFS on sparc64 due to unaliged accesses in test suite)

Your message dated Tue, 05 Sep 2017 00:05:10 + with message-id <e1dp1mc-0008ky...@fasolo.debian.org> and subject line Bug#867987: fixed in h5py 2.7.1-1 has caused the Debian Bug report #867987, regarding h5py: FTBFS on sparc64 due to unaliged accesses in test suite to be marked a

Bug#873008: hfst FTBFS on big endian: FAIL: test

That's my bad. In the confusion of bugs #824119 and #827199 , I forgot to re-disable tests for hfst. -- Tino Didriksen On 23 August 2017 at 18:38, Adrian Bunk wrote: > Source: hfst > Version: 3.12.2~r3289-1 > Severity: serious > >

Bug#873008: hfst FTBFS on big endian: FAIL: test

src/hfst-twolc/src' make[6]: Nothing to be done for 'check'. make[6]: Leaving directory '/<>/tools/src/hfst-twolc/src' Making check in test make[6]: Entering directory '/<>/tools/src/hfst-twolc/test' /usr/bin/make test1 test1.txt_fst test10 test10.txt_fst test11 test11.txt_fst test12 te

Bug#856356: marked as done (linbox FTBFS on mips/mipsel: segfault in test-charpoly)

Your message dated Sun, 20 Aug 2017 15:06:56 + with message-id <e1djrow-000a0u...@fasolo.debian.org> and subject line Bug#856356: fixed in linbox 1.4.2-5 has caused the Debian Bug report #856356, regarding linbox FTBFS on mips/mipsel: segfault in test-charpoly to be marked as done. This

Bug#862090: marked as done (mathicgb FTBFS on big endian architectures: test fails)

Your message dated Sun, 13 Aug 2017 15:19:18 + with message-id <e1dgufe-h0...@fasolo.debian.org> and subject line Bug#862090: fixed in mathicgb 1.0~git20170606-1 has caused the Debian Bug report #862090, regarding mathicgb FTBFS on big endian architectures: test fails to be marked a

Bug#871556: marked as done (libvigraimpex: several tests failing in Gridgraph Test Dimension 3)

Your message dated Sat, 12 Aug 2017 22:59:23 +0200 with message-id <088560f8-5926-35cf-2b5e-1b5171ef5...@danielstender.com> and subject line libvigraimpex: several tests failing in Gridgraph Test Dimension 3 has caused the Debian Bug report #871556, regarding libvigraimpex: several tests f

Bug#871927: xtensor-python FTBFS: test failures

Source: xtensor-python Version: 0.12.2-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xtensor-python.html ... [ RUN ] pyarray.access xtensor-python_0.12.2-1/test/test_common.hpp:321: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal

Bug#871556: libvigraimpex: several tests failing in Gridgraph Test Dimension 3

1.10.0+git20160211.167be93+dfsg/obj/test/gridgraph && ./run_test_gridgraph.sh Entering test suite Gridgraph Test Entering test suite Gridgraph Test Dimension 2 All (38) tests passed in test suite Gridgraph Test Dimension 2 Leaving test suite Gridgraph Test Dimension 2 Entering test suite Gridgraph Test Dimens

Bug#871208: python-xarray: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.6 3.5" returned exit code 13

an.png > copying images... [ 21%] _build/html/_static/2d_simple_yincrease.png > copying images... [ 24%] _build/html/_static/plotting_ways_to_use.png > copying images... [ 26%] _build/html/_static/plotting_kelvin.png > copying images... [ 29%] _build/html/_static/pl

Bug#598571: libatlas3gf-base: Build of atlas test programm xsl2blastst_pt and xsl1blastst_pt failed

t;  > I have build a custom altas library following the instructions in the README > file. Everyting went ok, but when I try to build the test program > xsl2blastst_pt and xsl1blast$ >  > make xsl2blastst_pt > gcc -o sl2blastst_pt.o -c -DL2SIZE=4194304 > -I/usr/src/atlas-3.8.3/build

Bug#870203: dune-grid FTBFS on mips: test-ug (Timeout)

Control: severity -1 important Adrian Bunk writes: > Start 31: test-ug > 31/60 Test #31: test-ug > ...***Timeout 300.02 sec Yes, saw the same issue also on PowerPC. I haven't found time to look at this yet and have asked for dune-grid

Processed: Re: Bug#870203: dune-grid FTBFS on mips: test-ug (Timeout)

Processing control commands: > severity -1 important Bug #870203 [src:dune-grid] dune-grid FTBFS on mips: test-ug (Timeout) Severity set to 'important' from 'serious' -- 870203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870203 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#870217: glm: FTBFS with gcc-7: Test failures

Source: glm Version: 0.9.8.4-1 Severity: important >From my pbuilder build log, using gcc-defaults from experimental: ... 97% tests passed, 3 tests failed out of 108 Total Test time (real) = 2.37 sec The following tests FAILED: 12 - test-core_type_mat2x4 (Failed) 15 - t

Bug#870203: dune-grid FTBFS on mips: test-ug (Timeout)

Source: dune-grid Version: 2.5.1-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=dune-grid=mips=2.5.1-1=1500401835=0 ... Start 31: test-ug 31/60 Test #31: test-ug ...***Timeout 300.02 sec Testing UGGrid<2> and UG

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

> I intentionally didn't close this bug because the tests still fail if they are enabled. Right. Well, I've reported the bug upstream [1] and at this point there's not much more than we can do. Unfortunately, Trilinos has a history of failing tests, the list of subpackages for which we have to

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

On 24/07/2017 10:40, Nico Schlömer wrote: Sounds more like a gAM bug then. Can this be closed? I intentionally didn't close this bug because the tests still fail if they are enabled. If the problem is caused by another package, then this bug should be reassigned to that package and marked

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

rsons <dpars...@debian.org> > wrote: > > > > For whatever reason, the build does not fail on the buildd (odd, my > > test ran 842 tests, buildd only runs 830). > > Ah I see, you uploaded -4 while we were testing :) > The bugserver didn't send me the bug tra

Bug#868965: seaborn: FTBFS: Test failures

--- > Ran 394 tests in 110.887s > > FAILED (SKIP=5, errors=1) > E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: > nosetests -s -v /<>/.pybuild/pythonX.Y_2.7/build/ > dh_auto_test: pybuild --test -i pytho

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

On Mon, 17 Jul 2017 10:21:03 +0800 Drew Parsons <dpars...@debian.org> wrote: >  > For whatever reason, the build does not fail on the buildd (odd, my > test ran 842 tests, buildd only runs 830).  Ah I see, you uploaded -4 while we were testing :)   The bugserver didn't send me

Processed: Re: Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

Processing commands for cont...@bugs.debian.org: > severity 868523 important Bug #868523 [src:trilinos] FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assi

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

Uploaded, please downgrade the severity of this bug once the builds are successful. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

On 16 July 2017 at 20:40, Nico Schlömer <nico.schloe...@gmail.com> wrote: > I've disabled the phalanx tests in master, and also fixed two other things. > Perhaps it's time for an upload? Doing a test build now, will upload if successful. -- debian-science-maintainers mailing list de

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

t; it's best to disable that specific test. > > Cheers, > Nico > > > [1] https://github.com/trilinos/Trilinos/issues/1332 > > On Sun, Jul 16, 2017 at 1:51 PM Graham Inggs <gin...@debian.org> wrote: > >> On 16 July 2017 at 13:12, Drew Parsons <dpars...@debian.

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

The issue was reported to upstream in May [1]. I think until we get a fix, it's best to disable that specific test. Cheers, Nico [1] https://github.com/trilinos/Trilinos/issues/1332 On Sun, Jul 16, 2017 at 1:51 PM Graham Inggs <gin...@debian.org> wrote: > On 16 July 2017 at 13

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

sure if it's the new mumps, new openmpi 2.1.1 or something else. > Full build log attached. Reproducible build history shows FTBFS since 2017-07-02: https://tests.reproducible-builds.org/debian/history/amd64/trilinos.html Although with only one test failure: The following tests FAILED: 668 - Pha

Bug#867987: h5py: FTBFS on sparc64 due to unaliged accesses in test suite

..@lists.debian.org > > Hi, > Currently h5py FTBFS on sparc64 (and has done for as long as sparc64 has > been building packages without nocheck), as the test suite crashes with > SIGBUS due to unaligned memory accesses. I have submitted a fix upstream > at the above URL; p

Bug#867987: h5py: FTBFS on sparc64 due to unaliged accesses in test suite

without nocheck), as the test suite crashes with SIGBUS due to unaligned memory accesses. I have submitted a fix upstream at the above URL; please include the patch in the Debian package. Regards, James -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Processed: Re: Bug#863707: [Pkg-openssl-devel] Bug#863707: simple-tpm-pk11: FTBFS: ./m4/test-driver: line 107: 4695 Aborted (core dumped)

Processing control commands: > reassign 864177 libssl1.1 Bug #864177 [nordugrid-arc] nordugrid-arc: FTBFS: test failure Bug reassigned from package 'nordugrid-arc' to 'libssl1.1'. No longer marked as found in versions 5.3.0-1. Ignoring request to alter fixed versions of bug #864177 to the s

Processed: Re: Bug#862090: mathicgb FTBFS on big endian architectures: test fails

Processing control commands: > forwarded -1 https://github.com/Macaulay2/mathicgb/issues/3 Bug #862090 [mathicgb] mathicgb FTBFS on big endian architectures: test fails Set Bug forwarded-to-address to 'https://github.com/Macaulay2/mathicgb/issues/3'. -- 862090: http://bugs.debian.org/cgi-

Bug#862090: mathicgb FTBFS on big endian architectures: test fails

mathicgb_1.0~git20170104-1 FTBFS on mips and other big endian architectures with following error: ... make check-TESTS make[2]: Entering directory '/«PKGBUILDDIR»' make[3]: Entering directory '/«PKGBUILDDIR»' FAIL: unittest mathicgb 1.0: ./test-suite.log

Bug#862090: mathicgb FTBFS on big endian architectures: test fails

check-TESTS > make[2]: Entering directory '/«PKGBUILDDIR»' > make[3]: Entering directory '/«PKGBUILDDIR»' > FAIL: unittest > > mathicgb 1.0: ./test-suite.log > > > # TOTAL: 1 > # PASS: 0 >

Bug#860641: marked as done (dune-localfunctions: FTBFS on i386: Test failures)

Your message dated Thu, 20 Apr 2017 18:07:47 + with message-id <e1d1gud-0001uk...@fasolo.debian.org> and subject line Bug#860641: fixed in dune-localfunctions 2.5.0-2 has caused the Debian Bug report #860641, regarding dune-localfunctions: FTBFS on i386: Test failures to be marked a

Bug#860641: dune-localfunctions: FTBFS on i386: Test failures

Source: dune-localfunctions Version: 2.5.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your

Bug#827199: marked as done (hfst: FTBFS: twolc test fails on big-endian systems)

Your message dated Thu, 23 Mar 2017 15:04:24 + with message-id <e1cr4ho-000go1...@fasolo.debian.org> and subject line Bug#827199: fixed in hfst 3.10.0~r2798-3 has caused the Debian Bug report #827199, regarding hfst: FTBFS: twolc test fails on big-endian systems to be marked a

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

rimary usecases - using little-endian everywhere. >> >> Progress? >> >> At this point this has been the last package stuck in a library >> transition (ignoring openssl), and we are in deep freeze. >> >> I think a fix is highly overdue. > > So sorry, I complet

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

On Sat, Nov 05, 2016 at 12:49:37AM +0100, Tino Didriksen wrote: > On 4 November 2016 at 20:49, Jonathan Wiltshire <j...@debian.org> wrote: > > > > > While it did successfully build in the past, that was only because the > > test > > > > suite was d

Bug#856356: linbox FTBFS on mips/mipsel: segfault in test-charpoly

Hi, Test 'test-charpoly' fails for mips and mipsel: https://github.com/linbox-team/linbox/issues/37 A workaround at this point could be to disable this test, please see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797167 Current solution for this in debian/rules file (which disables

Bug#855929: mclibs: FTBFS: Test failures

address 0x7f68e28cd740 exceeds the 32 bit address space > > or is not in the data segments > > This may result in program crash or incorrect results > > Therefore we will stop here > > > > Test result = 231 > > Makefile:482: recipe for target 'tes

Processed: Re: mclibs: FTBFS: Test failures

Processing commands for cont...@bugs.debian.org: > retitle 855929 mclibs: FTBFS: LOCB/LOCF: address 0x7f68e28cd740 exceeds the > 32 bit address space or is not in the data segments Bug #855929 [src:mclibs] mclibs: FTBFS: Test failures Changed Bug title to 'mclibs: FTBFS: LOCB/LOCF: a

Bug#856356: linbox FTBFS on mips/mipsel: segfault in test-charpoly

Source: linbox Version: 1.4.2-3 Severity: important https://buildd.debian.org/status/package.php?p=linbox=sid ... PASS: test-blas-matrix ../build-aux/test-driver: line 107: 15983 Segmentation fault "$@" > $log_file 2>&1 FAIL: test-charpoly PASS: test-ntl-lzz_pex /bin/ba

Bug#855929: mclibs: FTBFS: Test failures

0 exceeds the 32 bit address space > or is not in the data segments > This may result in program crash or incorrect results > Therefore we will stop here > !!!! > Test result = 231 > Makefile:482: recipe for target 'test' failed

Bug#848764: marked as done (theano: test failures with Numpy 1.12)

Your message dated Mon, 13 Feb 2017 17:48:36 + with message-id <e1cdkjs-0001db...@fasolo.debian.org> and subject line Bug#848764: fixed in theano 0.8.2-4 has caused the Debian Bug report #848764, regarding theano: test failures with Numpy 1.12 to be marked as done. This means that you

Bug#848764: theano: test failures with Numpy 1.12

Hi Daniel, the remaining numpy-1.12 failurtes can be resolved with this patch: https://github.com/Theano/Theano/commit/a95f8af1b4c54a8ffa77fcd5f44cfdcb1772cf22 Cheers Ole -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#848859: [bug #25503] test failures

Update of bug #25503 (project getfem): Status:None => Fixed Assigned to:None => renard Open/Closed:Open => Closed

  1   2   3   4   >