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 big-endian architectures, I added a patch [2] and forwarded it upstream. I uploaded 0.22.0-3 including these changes, and as of this writing, builds have succeeded on s390x, ppc64el, amd64 and i386. Regards Graham [1] https://salsa.debian.org/science-team/pandas/commit/2971b1a4336d54def88857853e24274503b9cf55 [2] https://salsa.debian.org/science-team/pandas/commit/27e71d47e891547e3e492b1e25494bf2b4504a49 -- 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#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 claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 889539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 self = @slow def test_boxplot_legacy(self): df = DataFrame(randn(6, 4), index=list(string.ascii_letters[:6]), columns=['one', 'two', 'three', 'four']) df['indic'] = ['foo', 'bar'] * 3 df['indic2'] = ['foo', 'bar', 'foo'] * 2 _check_plot_works(df.boxplot, return_type='dict') _check_plot_works(df.boxplot, column=[ 'one', 'two'], return_type='dict') # _check_plot_works adds an ax so catch warning. see GH #13188 with tm.assert_produces_warning(UserWarning): _check_plot_works(df.boxplot, column=['one', 'two'], by='indic') _check_plot_works(df.boxplot, column='one', by=['indic', 'indic2']) with tm.assert_produces_warning(UserWarning): _check_plot_works(df.boxplot, by='indic') with tm.assert_produces_warning(UserWarning): > _check_plot_works(df.boxplot, by=['indic', 'indic2']) ../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_boxplot_method.py:57: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python2.7/contextlib.py:24: in __exit__ self.gen.next() _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expected_warning = , filter_level = 'always' clear = None, check_stacklevel = True @contextmanager def assert_produces_warning(expected_warning=Warning, filter_level="always", clear=None, check_stacklevel=True): """ Context manager for running code that expects to raise (or not raise) warnings. Checks that code raises the expected warning and only the expected warning. Pass ``False`` or ``None`` to check that it does *not* raise a warning. Defaults to ``exception.Warning``, baseclass of all Warnings. (basically a wrapper around ``warnings.catch_warnings``). >>> import warnings >>> with assert_produces_warning(): ... warnings.warn(UserWarning()) ... >>> with assert_produces_warning(False): ... warnings.warn(RuntimeWarning()) ... Traceback (most recent call last): ... AssertionError: Caused unexpected warning(s): ['RuntimeWarning']. >>> with assert_produces_warning(UserWarning): ... warnings.warn(RuntimeWarning()) Traceback (most recent call last): ... AssertionError: Did not see expected warning of class 'UserWarning'. ..warn:: This is *not* thread-safe. """ with warnings.catch_warnings(record=True) as w: if clear is not None: # make sure that we are clearning these warnings # if they have happened before # to guarantee that we will catch them if not is_list_like(clear): clear = [clear] for m in clear: try: m.__warningregistry__.clear() except: pass saw_warning = False warnings.simplefilter(filter_level) yield w extra_warnings = [] for actual_warning in w: if (expected_warning and issubclass(actual_warning.category, e
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' echo "Såg hon inte orden?" | apertium -d . swe-nno | tee .test-mt Såg kummen ikkje orda? 1c1 < Såg ho ikkje orda? --- > Såg kummen ikkje orda? make[1]: *** [Makefile:878: test] Error 1 -- 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#888733: hyantesite FTBFS on most architectures: test failures
Package: hyantesite Version: 1.3.0-2 Followup-For: Bug #888733 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic ubuntu-patch Dear maintainers, Looking into this build failure (which is also reproducible in Ubuntu), I see that it's a consequence of the packaging changes in -2 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 that the package is broken. Attached is a patch that would allow ignoring the test failures on architectures other than amd64 and armel in the near term, until they are fixed upstream. An alternative solution would be to request removal of the broken binaries from the archive on other architectures, depending on how serious this breakage is. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru hyantesite-1.3.0/debian/rules hyantesite-1.3.0/debian/rules --- hyantesite-1.3.0/debian/rules 2018-01-25 03:49:37.0 -0800 +++ hyantesite-1.3.0/debian/rules 2018-04-07 17:22:25.0 -0700 @@ -3,8 +3,19 @@ export DEB_BUILD_MAINT_OPTIONS=hardening=+all +DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) + +ifeq (,$(filter amd64 armel,$(DEB_HOST_ARCH))) +ALLOW_FAILING_TESTS := true +else +ALLOW_FAILING_TESTS := false +endif + %: dh $@ override_dh_auto_configure: dh_auto_configure -- --enable-doc + +override_dh_auto_test: + dh_auto_test || $(ALLOW_FAILING_TESTS) -- 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#893899: ITP: r-cran-libcoin -- GNU R linear test statistics for permutation inference
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-libcoin Version : 1.0-1 Upstream Author : Torsten Hothorn * URL : https://cran.r-project.org/package=libcoin * License : 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 by end-users. CRAN package 'coin' implements all user interfaces and is ready to be used by anyone. Remark: This package is needed to run the full test suite of r-cran-coin (see #882865). It will be maintained by the r-pkg team at https://salsa.debian.org/r-pkg-team/r-cran-libcoin -- 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#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
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-packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
892019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-meshio
Version: 1.11.7-1
Severity: serious
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed
that python-meshio installs 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 / chris-lamb.co.uk
`-
--- a/debian/rules 2018-03-04 08:29:37.637307710 +
--- b/debian/rules 2018-03-04 08:43:11.509093514 +
@@ -6,6 +6,9 @@
export PYBUILD_NAME=meshio
export PYBUILD_DESTDIR_python3=debian/python3-$(PYBUILD_NAME)
+# Don't install files generated by the testsuite.
+export PYBUILD_AFTER_TEST := find {build_dir} -type f -maxdepth 1 -delete
+
%:
dh $@ --with python3 --buildsystem=pybuild
--- End Message ---
--- Begin Message ---
Source: python-meshio
Source-Version: 1.11.7-2
We believe that the bug you reported is fixed in the latest version of
python-meshio, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ghislain Antony Vaillant (supplier of updated
python-meshio package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 06 Mar 2018 20:17:14 +
Source: python-meshio
Binary: python3-meshio meshio-tools
Architecture: source
Version: 1.11.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Ghislain Antony Vaillant
Description:
meshio-tools - command-line tools for meshio
python3-meshio - library for reading and writing mesh data (Python 3)
Closes: 892019
Changes:
python-meshio (1.11.7-2) unstable; urgency=medium
.
* Prevent install of files under dist-packages.
Thanks to Chris Lamb for the patch (Closes: #892019)
Checksums-Sha1:
1b549ea663b760b29c7c4194bbe92390932c6124 2343 python-meshio_1.11.7-2.dsc
bc82ee2ad69bb19e2a5c7879d16c7f68b01f66a2 3604
python-meshio_1.11.7-2.debian.tar.xz
959aad0b1dbe34277d29b69a44ebbe5f952341fa 7501
python-meshio_1.11.7-2_amd64.buildinfo
Checksums-Sha256:
02816c1061e8e70ead2ff3baee639ae6c871069bad3b5018cc6fe4d78e83e70b 2343
python-meshio_1.11.7-2.dsc
76101cf8648fdb3523937a34cbc58fcc6b9e2e6c145556088c1864323d6ead89 3604
python-meshio_1.11.7-2.debian.tar.xz
d3ba644e554a6e8b1c04667bb267125b69bae2dfce8fb80144f2022cc474770b 7501
python-meshio_1.11.7-2_amd64.buildinfo
Files:
1447336f5ae9b2698d5ef227f21faba6 2343 python optional
python-meshio_1.11.7-2.dsc
9bc6b0a7e96a4467b480fb57923cf22b 3604 python optional
python-meshio_1.11.7-2.debian.tar.xz
7ac7c1a3c9f74370b4ef1634530134e8 7501 python optional
python-meshio_1.11.7-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlqhn7EACgkQLOzpNQ7O
vkrCmhAAmWKesixUWcqH3uWhqj5VRS8k5W8Fvitiojw1Hg7ABwj0LIpEbEO5qSzx
qw5DGb/JfzlUmg85wa5hv/4zVNDGiqrrA+N/Dtdg3Nh8NIDLD78VclyewK/ghqGi
3QVM74TeSMQX+U6UCKQyw0qdU/upnGOObhzBs4tXQwKMJXA33P2f0ACnI/WE2MqF
Q0Xl/hHKlT6TiL3aLgvysDSh5ArB/4BfMOkyHlS6NAoBHRGbL8PiicCGgoQ4Glrh
XGM1kHcaO6/F3xPr9jsBmjGH8DQltt4RGGya5xxQcM/pOwLzfxv/M4ZW7LGsc09x
PQly8sfF36HsOBtXUsXbBmbW3/4AsKKbRPBqt5yo5xHmWkOxNDgLaWKmCjmvHrog
fMqIrGud3c8kYnq5D7PtFd67cVbaB/MCFpfothzGMvd0pKqu+7xSwoG/kMsO8phg
VnNwYED6OoqmeAEt3VK16noa5ikTX2DiRe/aw4hrCzrxl2zW6SDZ5xacEXe9sL/Y
uv0WCA+4aLVj0WiJ8M5M37Lr+8SRi345K/X07928ZTLZ4Rmh6KVVP2dN4/QDKv7W
8opXb6AhJALLceNvF7JEfuf6WsnDtR8f6tbiwlkFlox4uVdvENMQC+5YO7sYp8PN
3DhSAQSuJ3
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 - Test_assign_cpu (SEGFAULT) 43 - Test_index_cpu (SEGFAULT) Errors while running CTest Makefile:143: recipe for target 'test' failed make[2]: *** [test] Error 8 Whatever broke it was not yet in unstable on 2017-12-31, but likely entered buster before 2018-01-31: https://tests.reproducible-builds.org/debian/history/arrayfire.html -- 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#892019: python-meshio: Installs test files to /usr/lib/python3/dist-packages
Source: python-meshio
Version: 1.11.7-1
Severity: serious
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed
that python-meshio installs 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 / chris-lamb.co.uk
`-
--- a/debian/rules 2018-03-04 08:29:37.637307710 +
--- b/debian/rules 2018-03-04 08:43:11.509093514 +
@@ -6,6 +6,9 @@
export PYBUILD_NAME=meshio
export PYBUILD_DESTDIR_python3=debian/python3-$(PYBUILD_NAME)
+# Don't install files generated by the testsuite.
+export PYBUILD_AFTER_TEST := find {build_dir} -type f -maxdepth 1 -delete
+
%:
dh $@ --with python3 --buildsystem=pybuild
--
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#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 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 impression, that you are the more competent > team member than me in terms of pandas. So please do not be shy. ;-) > > Thanks a lot and feel to keep on pushing promising patches > > Andreas. > >> [2] >> diff --git a/debian/tests/control b/debian/tests/control >> index 38521c8..ab54101 100644 >> --- a/debian/tests/control >> +++ b/debian/tests/control >> @@ -15,6 +15,7 @@ Depends: python-all, >> python-xlwt, >> python-bs4, >> python-html5lib, >> + python-pytest, >> xauth, >> xvfb >> >> @@ -29,5 +30,6 @@ Depends: python3-all, >> python3-tk, >> python3-tz, >> python3-bs4, >> + python3-pytest, >> xauth, >> xvfb > > -- > http://fam-tille.de -- Best, -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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 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 as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 79: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rheolef Version: 6.7-5 Severity: serious https://buildd.debian.org/status/package.php?p=rheolef&suite=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 left >/dev/null 2>/dev/null mpirun -np 3 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 left >/dev/null 2>/dev/null mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 right >/dev/null 2>/dev/null mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 right >/dev/null 2>/dev/null E: Build killed with signal TERM after 150 minutes of inactivity I've reproduced this on i386, two processes are running forever (aborted after 6 hours on a fast CPU) with 100% CPU. Backtraces: Thread 3 (Thread 0xf50ffb40 (LWP 29032)): #0 0xf7ed6db9 in __kernel_vsyscall () #1 0xf70fabd3 in __GI___poll (fds=0xf47005d0, nfds=2, timeout=360) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0xf5caed4a in poll (__timeout=360, __nfds=2, __fds=0xf47005d0) at /usr/include/i386-linux-gnu/bits/poll2.h:46 #3 poll_dispatch (base=0x578eb9c0, tv=0xf50f9bfc) at poll.c:165 #4 0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, flags=) at event.c:1630 #5 0xf5c6b3bd in progress_engine (obj=0x578eb950) at runtime/opal_progress_threads.c:105 #6 0xf5df6316 in start_thread (arg=0xf50ffb40) at pthread_create.c:465 #7 0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 2 (Thread 0xf5ac5b40 (LWP 29031)): #0 0xf7ed6db9 in __kernel_vsyscall () #1 0xf71053fa in __GI_epoll_pwait (epfd=7, events=0x578ea930, maxevents=32, timeout=-1, set=0x0) at ../sysdeps/unix/sysv/linux/epoll_pwait.c:42 #2 0xf710569a in epoll_wait (epfd=7, events=0x578ea930, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #3 0xf5ca199a in epoll_dispatch (base=0x578ea7a0, tv=0x0) at epoll.c:407 #4 0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, flags=) at event.c:1630 #5 0xf5af23eb in progress_engine (obj=0x578ea7a0) at src/util/progress_threads.c:52 #6 0xf5df6316 in start_thread (arg=0xf5ac5b40) at pthread_create.c:465 #7 0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 1 (Thread 0xf5b4fe00 (LWP 29002)): #0 0xf7ed67f5 in ?? () #1 0xf7ed6b43 in __vdso_clock_gettime () #2 0xf7112961 in __GI___clock_gettime (clock_id=1, tp=0xffb74194) at ../sysdeps/unix/clock_gettime.c:115 #3 0xf5cc3297 in opal_timer_linux_get_usec_clock_gettime () at timer_linux_component.c:197 #4 0xf5c669c3 in opal_progress () at runtime/opal_progress.c:197 #5 0xf74b5e05 in sync_wait_st (sync=) at ../opal/threads/wait_sync.h:80 #6 ompi_request_default_wait_all (count=2, requests=0xffb742e4, statuses=0x0) at request/req_wait.c:221 #7 0xf750640d in ompi_coll_base_allreduce_intra_recursivedoubling (sbuf=0x57951030, rbuf=0x57a9b400, count=2, dtype=0xf7565140 , op=0xf7573e60 , comm=0xf7569520 , module=0x57976fa0) at base/coll_base_allreduce.c:225 #8 0xe991f640 in ompi_coll_tuned_allreduce_intra_dec_fixed (sbuf=0x57951030, rbuf=0x57a9b400, count=2, dtype=0xf7565140 , op=0xf7573e60 , comm=0xf7569520 , module=0x57976fa0) at coll_tuned_decision_fixed.c:66 #9 0xf74c5b77 in PMPI_Allreduce (sendbuf=0x57951030, recvbuf=0x57a9b400, count=2, datatype=0xf7565140 , op=0xf7573e60 , comm=0xf7569520 ) at pallreduce.c:107 #10 0xf7b476cf in boost::mpi::detail::all_reduce_impl > (comm=..., in_values=0x57951030, n=n@entry=2, out_values=0x57a9b400) at /usr/include/boost/mpi/collectives/all_reduce.hpp:36 #11 0xf7b58fc0 in boost::mpi::all_reduce > (out_values=, n=2, in_values=, comm=..., op=...) at /usr/include/boost/mpi/collectives/all_reduce.hpp:93 #12 rheolef::mpi_assembly_begin, rheolef::heap_allocator > >, rheolef::disarray_rep >::message_type, rheolef::apply_iterator >, rheolef::first_op > > > (stash=..., first_stash_idx=..., last_stash_idx=..., ownership=..., receive=..., send=...) at ../../include/rheole
Bug#888912: marked as done (sagemath test failures with mpfr 4.0.0 and several architectures)
Your message dated Sun, 11 Feb 2018 23:50:34 + with message-id and subject line Bug#888912: fixed in sagemath 8.1-3 has caused the Debian Bug report #888912, regarding sagemath test failures with mpfr 4.0.0 and several architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 888912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sagemath Version: 8.2-1 Severity: serious Tags: sid buster see https://buildd.debian.org/status/package.php?p=sagemath&suite=unstable test failures on every architecture. --- End Message --- --- Begin Message --- Source: sagemath Source-Version: 8.1-3 We believe that the bug you reported is fixed in the latest version of sagemath, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Hansen (supplier of updated sagemath package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 11 Feb 2018 21:20:28 + Source: sagemath Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr Architecture: source Version: 8.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Tobias Hansen Description: sagemath - Open Source Mathematical Software sagemath-common - Open Source Mathematical Software - architecture-independent file sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; Valen sagemath-doc-de - Open Source Mathematical Software - documentation (German) sagemath-doc-en - Open Source Mathematical Software - documentation (English) sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; Casti sagemath-doc-fr - Open Source Mathematical Software - documentation (French) sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian) sagemath-doc-it - Open Source Mathematical Software - documentation (Italian) sagemath-doc-ja - Open Source Mathematical Software - documentation (Japanese) sagemath-doc-pt - Open Source Mathematical Software - documentation (Portuguese) sagemath-doc-ru - Open Source Mathematical Software - documentation (Russian) sagemath-doc-tr - Open Source Mathematical Software - documentation (Turkish) sagemath-jupyter - Open Source Mathematical Software - Jupyter kernel Closes: 888912 Changes: sagemath (8.1-3) unstable; urgency=medium . [ Tobias Hansen ] * Update Vcs-* links for salsa. * New patches: - u0-version-mpfr-4.0.patch Fixes for libmpfr 4.0. - u0-version-matplotlib-2.1.0.patch New dependencies: - python-subprocess32 - python-backports.functools-lru-cache * Modified patches: - dt-more-fix-test-cases.patch Fix ordering issue in two tests in the documentation. . [ Ximin Luo ] * Tests now pass fine after fixes in other packages. (Closes: #888912) * Modified patches: - dt-more-fix-test-cases.patch Ignore sigabrt in sage_object.pyx doctest. * Add dbg packages to the pkg.sagemath.dbg build-profile to make stack traces work. * Touch the dummy spkg file to avoid rebuilds in some cases. Checksums-Sha1: da3d5c5c97a1f506e2e434c371c512061a06b145 6813 sagemath_8.1-3.dsc 5d65c9398852d707469002b5606e9780f2c13d98 87168 sagemath_8.1-3.debian.tar.xz 38110b32f4c89cde6539c618b271ae8ff456f440 28264 sagemath_8.1-3_source.buildinfo Checksums-Sha256: 8c9c43beb06e0e812db552147930d1aa50a4266001ab40b6ec1565e0437103dd 6813 sagemath_8.1-3.dsc bee3f0f0724ab17c546417fe348e9ac11d68e5b3399426f51d38abcef65cd0cd 87168 sagemath_8.1-3.debian.tar.xz 7d7befe56dc3b71fa24b80b2b9a013b9e741754c462bbbccbf501fce37ca716c 28264 sagemath_8.1-3_source.buildinfo Files: 8ff2b0361ddba17a4a69eba91209df86 6813 math optional sagemath_8.1-3.dsc 28c4d6a43181d668d6e0c10ae64cfed6 87168 math optional sagemath_8.1-3.debian.tar.xz 9190b69a2085f7fac9dfe019463d4993 28264 math opti
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&arch=amd64&ver=8.1-2%2Bb2&stamp=1517950645&raw=0 -- 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#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 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_utils.cmake" listed in Files-Excluded header to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 883757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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_utils.cmake. This is probably a DFSG violation, or at the upstream tarball was not repacked as intended. Alternatively, the field is simply out of date. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: ignition-transport Source-Version: 4.0.0+dfsg-1 We believe that the bug you reported is fixed in the latest version of ignition-transport, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 883...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jose Luis Rivero (supplier of updated ignition-transport package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Feb 2018 14:04:13 + Source: ignition-transport Binary: libignition-transport4 libignition-transport-dev libignition-transport4-dev Architecture: source all amd64 Version: 4.0.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jose Luis Rivero Description: libignition-transport-dev - transitional package libignition-transport4 - Ignition Robotics Transport Library - Shared library libignition-transport4-dev - Ignition Robotics transport Library - Development files Closes: 883757 888017 Changes: ignition-transport (4.0.0+dfsg-1) unstable; urgency=medium . [ Jose Luis Rivero ] * New upstream version 4.0.0+dfsg (Closes: #883757) (Closes: #888017) . [ Anton Gladky ] * Switch to compat-level 11 * Set Standards-Version: 4.1.3 * Update VCS-fields (move to salsa) Checksums-Sha1: 89786b7038de29a3e75184bc9f7bcc4cce8aeb95 2549 ignition-transport_4.0.0+dfsg-1.dsc de598e7b48d0379a7d3efbcd0f93174acde85497 194328 ignition-transport_4.0.0+dfsg.orig.tar.xz 8219c1fa55ff47b99b9efdd92e6d43c484387a19 4576 ignition-transport_4.0.0+dfsg-1.debian.tar.xz 0e26773114ca725c24766a3c0bfb3b624dc891e5 9121 ignition-transport_4.0.0+dfsg-1_amd64.buildinfo 3b187ab2fdf3b9c91e624aabbff47ef9222c662b 5056 libignition-transport-dev_4.0.0+dfsg-1_all.deb 9bbee59560779ec7d6ec6c33608edbb16d27de86 1865092 libignition-transport4-dbgsym_4.0.0+dfsg-1_amd64.deb d6673c1bf813dbeaebf6a62bee36091f911b7857 42404 libignition-transport4-dev_4.0.0+dfsg-1_amd64.deb 9b426a4aec83e70acf4622ef8f387267955aeb6c 133624 libignition-transport4_4.0.0+dfsg-1_amd64.deb Checksums-Sha256: de1dbfc99c2de11b549b3a02d2fe34743f1db893b3b82e1a7fb346c2f850 2549 ignition-transport_4.0.0+dfsg-1.dsc 18c3104694614f80f99ff295309d771d2f0ef61718f2647f760e23965d62ef6c 194328 ignition-transport_4.0.0+dfsg.orig.tar.xz 005e2212ef1f59e5dd926351d4a0f587d7517fdee4e953c60619774877f2a174 4576 ignition-transport_4.0.0+dfsg-1.debian.tar.xz 47892d93f804b4d91d23a093a479d8cc0fd6dc7881ac565509ec82df2d8d73cc 9121 ignition-transport_4.0.0+dfsg-1_amd64.buildinfo 10873be0d741c313733a4e4c103993f19e76b3da08323173e88de37b1609ab03 5056 libignition-transport-dev_4.0.0+dfsg-1_all.deb 49f140d75a0c5f62b3800c97bf8c8c4cf43e7adbfcad3207826500c826ce35f4 1865092 libignition-transport4-dbgsym_4.0.0+dfsg-1_amd64.deb e7dfd6408eb4a6455bb3d4382d7a4c9d7eaa5070396e2e36226183814cc3acf2 42404 libignition-transport4-dev_4.0.0+dfsg-1_amd64.deb 91633b478fe693728bd764030578fec616ddeacddc2b0aa309001ac66e7e0b63 133624 libignition-transport4_4.0.0+dfsg-1_amd64.deb Files: 5bde0
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 impression, that you are the more competent team member than me in terms of pandas. So please do not be shy. ;-) Thanks a lot and feel to keep on pushing promising patches Andreas. > [2] > diff --git a/debian/tests/control b/debian/tests/control > index 38521c8..ab54101 100644 > --- a/debian/tests/control > +++ b/debian/tests/control > @@ -15,6 +15,7 @@ Depends: python-all, > python-xlwt, > python-bs4, > python-html5lib, > + python-pytest, > xauth, > xvfb > > @@ -29,5 +30,6 @@ Depends: python3-all, > python3-tk, > python3-tz, > python3-bs4, > + python3-pytest, > xauth, > xvfb -- http://fam-tille.de -- 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#889539: pandas FTBFS: test failures
Hi Andreas, On 6 February 2018 at 11:10, Andreas Tille wrote: > you did a really good job on latest pandas issues. Do you think you can > have a look at this problem as well? I found no related upsteam issue about the failed tests. However there are some links 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 numpy issues again according to the stackoverflow answers. Apart from that, the pandas packaging needs a patch [2] to reduce autopkgtest failures. > 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 [1]). It might be a sensible strategy > To upgrade to latest pandas upstream to not spent to much time on the > old code - however, I have no idea about compatibility issues of all of > its rdepends. I checked and tried to build that package. Feedbacks were sent in another mail. I think the 0.20.3-12 upload is not necessary as long as we manage to build the new pandas before the removal, because there is no obvious bug in pandas itself -- the patch for -12 will be workarounds to those external problems. [1] debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/dtypes/test_missing.py::test_array_equivalent_compat /usr/lib/python2.7/dist-packages/numpy/core/numeric.py:2604: FutureWarning: elementwise == comparison failed and returning scalar instead; this will raise an error or perform elementwise comparison in the future. return bool(asarray(a1 == a2).all()) debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/frame/test_analytics.py::TestDataFrameAnalytics::()::test_corr_int_and_boolean /usr/lib/python2.7/dist-packages/scipy/stats/stats.py:3577: RuntimeWarning: invalid value encountered in double_scalars size * (size - 1) * (size - 2)) debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_boxplot_method.py::TestDataFramePlots::()::test_boxplot_legacy /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_boxplot_method.py::TestDataFramePlots::()::test_boxplot_axis_limits /usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py:57: FutureWarning: reshape is deprecated and will raise in a subsequent release. Please use .values.reshape(...) instead return getattr(obj, method)(*args, **kwds) debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_datetimelike.py::TestTSPlot::()::test_irreg_hf /usr/lib/python2.7/dist-packages/matplotlib/cbook/deprecation.py:106: MatplotlibDeprecationWarning: Adding an axes using the same arguments as a previous axes currently reuses the earlier instance. In a future version, a new instance will always be created and returned. Meanwhile, this warning can be suppressed, and the future behavior ensured, by passing a unique label to each axes instance. warnings.warn(message, mplDeprecation, stacklevel
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 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 several architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 888911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. --- End Message --- --- Begin Message --- Version: 1.2.3.57+dfsg1-2+b4 now fixed, built using mpfr4 4.0.1 rc2.--- End Message --- -- 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#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 [1]). It might be a sensible strategy To upgrade to latest pandas upstream to not spent to much time on the old code - however, I have no idea about compatibility issues of all of its rdepends. Kind regards Andreas. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777089#129 -- http://fam-tille.de -- 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: 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 were simply not run before. Thus a first course of action might be to ask ftpmaster for removal of those architectures where rheolef does not build and reduce severity of the bug to say "important". Please note that I do not have any time resources to work on this package. Kind regards Andreas. [1] https://lists.alioth.debian.org/pipermail/debian-science-maintainers/2018-January/057544.html On Tue, Jan 30, 2018 at 10:24:18PM +0200, Adrian Bunk wrote: > Source: rheolef > Version: 6.7-5 > Severity: serious > > https://buildd.debian.org/status/package.php?p=rheolef&suite=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 > left >/dev/null 2>/dev/null > mpirun -np 3 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 > left >/dev/null 2>/dev/null > mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 > right >/dev/null 2>/dev/null > mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 > right >/dev/null 2>/dev/null > E: Build killed with signal TERM after 150 minutes of inactivity > > > I've reproduced this on i386, two processes are running > forever (aborted after 6 hours on a fast CPU) with 100% CPU. > > Backtraces: > > Thread 3 (Thread 0xf50ffb40 (LWP 29032)): > #0 0xf7ed6db9 in __kernel_vsyscall () > #1 0xf70fabd3 in __GI___poll (fds=0xf47005d0, nfds=2, timeout=360) at > ../sysdeps/unix/sysv/linux/poll.c:29 > #2 0xf5caed4a in poll (__timeout=360, __nfds=2, __fds=0xf47005d0) at > /usr/include/i386-linux-gnu/bits/poll2.h:46 > #3 poll_dispatch (base=0x578eb9c0, tv=0xf50f9bfc) at poll.c:165 > #4 0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, > flags=) at event.c:1630 > #5 0xf5c6b3bd in progress_engine (obj=0x578eb950) at > runtime/opal_progress_threads.c:105 > #6 0xf5df6316 in start_thread (arg=0xf50ffb40) at pthread_create.c:465 > #7 0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 > > Thread 2 (Thread 0xf5ac5b40 (LWP 29031)): > #0 0xf7ed6db9 in __kernel_vsyscall () > #1 0xf71053fa in __GI_epoll_pwait (epfd=7, events=0x578ea930, maxevents=32, > timeout=-1, set=0x0) > at ../sysdeps/unix/sysv/linux/epoll_pwait.c:42 > #2 0xf710569a in epoll_wait (epfd=7, events=0x578ea930, maxevents=32, > timeout=-1) > at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 > #3 0xf5ca199a in epoll_dispatch (base=0x578ea7a0, tv=0x0) at epoll.c:407 > #4 0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, > flags=) at event.c:1630 > #5 0xf5af23eb in progress_engine (obj=0x578ea7a0) at > src/util/progress_threads.c:52 > #6 0xf5df6316 in start_thread (arg=0xf5ac5b40) at pthread_create.c:465 > #7 0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 > > Thread 1 (Thread 0xf5b4fe00 (LWP 29002)): > #0 0xf7ed67f5 in ?? () > #1 0xf7ed6b43 in __vdso_clock_gettime () > #2 0xf7112961 in __GI___clock_gettime (clock_id=1, tp=0xffb74194) at > ../sysdeps/unix/clock_gettime.c:115 > #3 0xf5cc3297 in opal_timer_linux_get_usec_clock_gettime () at > timer_linux_component.c:197 > #4 0xf5c669c3 in opal_progress () at runtime/opal_progress.c:197 > #5 0xf74b5e05 in sync_wait_st (sync=) at > ../opal/threads/wait_sync.h:80 > #6 ompi_request_default_wait_all (count=2, requests=0xffb742e4, > statuses=0x0) at request/req_wait.c:221 > #7 0xf750640d in ompi_coll_base_allreduce_intra_recursivedoubling > (sbuf=0x57951030, rbuf=0x57a9b400, count=2, > dtype=0xf7565140 , op=0xf7573e60 , > comm=0xf7569520 , > module=0x57976fa0) at base/coll_base_allreduce.c:225 > #8 0xe991f640 in ompi_coll_tuned_allreduce_intra_dec_fixed (sbuf=0x57951030, > rbuf=0x57a9b400, count=2, > dtype=0xf7565140 , op=0xf7573e60 , > comm=0xf7569520 , > module=0x57976fa0) at coll_tuned_decision_fixed.c:66 > #9 0xf74c5b77 in PMPI_Allreduce (sendbuf=0x57951030, recvbuf=0x57a9b400, > count=2, > datatype=0xf7565140 , op=0xf7573e60 , > comm=0xf7569520 ) > at pallreduce.c:107 > #10 0xf7b476cf in boost::mpi::detail::all_reduce_impl std::plus > (comm=..., > in_values=0x57951030, n=n@entry=2, out_values=0x57a9b400) at > /usr/include/boost/mpi/collectives/all_reduce.hpp:36 > #11 0xf7b58fc0 in boost::mpi::all_reduce int> > (out_values=, n=2, &
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
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
python{version} -p "3.6 3.5" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
871208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 0.9.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees . _build/html
> Running Sphinx v1.5.6
> making output directory...
> python exec: /usr/bin/python3
> sys.path: ['/usr/share/sphinx/scripts/python3', '/<>',
> '/usr/lib/python35.zip', '/usr/lib/python3.5',
> '/usr/lib/python3.5/plat-x86_64-linux-gnu', '/usr/lib/python3.5/lib-dynload',
> '/usr/local/lib/python3.5/dist-packages', '/usr/lib/python3/dist-packages']
> numpy: 1.12.1, /usr/lib/python3/dist-packages/numpy/__init__.py
> scipy: 0.18.1, /usr/lib/python3/dist-packages/scipy/__init__.py
> pandas: 0.20.3, /usr/lib/python3/dist-packages/pandas/__init__.py
> matplotlib: 2.0.0, /usr/lib/python3/dist-packages/matplotlib/__init__.py
> dask: 0.15.1, /usr/lib/python3/dist-packages/dask/__init__.py
> ipython: 5.1.0, /usr/lib/python3/dist-packages/IPython/__init__.py
> seaborn: 0.8.0, /usr/lib/python3/dist-packages/seaborn/__init__.py
> cartopy: 0.14.2, /usr/lib/python3/dist-packages/cartopy/__init__.py
> netCDF4: 1.2.9, /usr/lib/python3/dist-packages/netCDF4/__init__.py
> xarray: 0.9.2, /<>/xarray/__init__.py
> loading pickled environment... not yet created
> [autosummary] generating autosummary for: api-hidden.rst, api.rst,
> combining.rst, computation.rst, dask.rst, data-structures.rst, examples.rst,
> examples/monthly-means.rst, examples/multidimensional-coords.rst,
> examples/quick-overview.rst, ..., indexing.rst, installing.rst,
> internals.rst, io.rst, pandas.rst, plotting.rst, reshaping.rst,
> time-series.rst, whats-new.rst, why-xarray.rst
> [autosummary] generating autosummary for:
> /<>/doc/generated/xarray.DataArray.T.rst,
> /<>/doc/generated/xarray.DataArray.__getitem__.rst,
> /<>/doc/generated/xarray.DataArray.__setitem__.rst,
> /<>/doc/generated/xarray.DataArray.all.rst,
> /<>/doc/generated/xarray.DataArray.any.rst,
> /<>/doc/generated/xarray.DataArray.argmax.rst,
> /<>/doc/generated/xarray.DataArray.argmin.rst,
> /<>/doc/generated/xarray.DataArray.argsort.rst,
> /<>/doc/generated/xarray.DataArray.assign_attrs.rst,
> /<>/doc/generated/xarray.DataArray.assign_coords.rst, ...,
> /<>/doc/generated/xarray.ufuncs.sign.rst,
> /<>/doc/generated/xarray.ufuncs.signbit.rst,
> /<>/doc/generated/xarray.ufuncs.sin.rst,
> /<>/doc/generated/xarray.ufuncs.sinh.rst,
> /<>/doc/generated/xarray.ufuncs.sqrt.rst,
> /<>/doc/generated/xarray.ufuncs.square.rst,
> /<>/doc/generated/xarray.ufuncs.tan.rst,
> /<>/doc/generated/xarray.ufuncs.tanh.rst,
> /<>/doc/generated/xarray.ufuncs.trunc.rst,
> /<>/doc/generated/xarray.zeros_like.rst
> loading intersphinx inventory from /usr/share/doc/python3/html/objects.inv...
> loading intersphinx inventory from
> /usr/share/doc/python-pandas-doc/html/objects.inv...
> loading intersphinx inventory from
> /usr/share/doc/python-numpy-doc/html/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 24 source files that are out of date
> updating environment: 322 added, 0 changed, 0 removed
> reading sources... [ 0%] api
> reading sources... [ 0%] api-hidden
> reading sources... [ 0%] combining
> reading sources... [ 1%] computation
> reading sources... [ 1%] dask
> reading sources... [ 1%] data-structures
> reading sources... [ 2%] examples
> reading sources... [ 2%] examples/monthly-means
> reading sources... [ 2%] examples/multidimens
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
self =
@slow
def test_boxplot_legacy(self):
df = DataFrame(randn(6, 4),
index=list(string.ascii_letters[:6]),
columns=['one', 'two', 'three', 'four'])
df['indic'] = ['foo', 'bar'] * 3
df['indic2'] = ['foo', 'bar', 'foo'] * 2
_check_plot_works(df.boxplot, return_type='dict')
_check_plot_works(df.boxplot, column=[
'one', 'two'], return_type='dict')
# _check_plot_works adds an ax so catch warning. see GH #13188
with tm.assert_produces_warning(UserWarning):
_check_plot_works(df.boxplot, column=['one', 'two'],
by='indic')
_check_plot_works(df.boxplot, column='one', by=['indic', 'indic2'])
with tm.assert_produces_warning(UserWarning):
_check_plot_works(df.boxplot, by='indic')
with tm.assert_produces_warning(UserWarning):
> _check_plot_works(df.boxplot, by=['indic', 'indic2'])
../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_boxplot_method.py:57:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python2.7/contextlib.py:24: in __exit__
self.gen.next()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
expected_warning = , filter_level = 'always'
clear = None, check_stacklevel = True
@contextmanager
def assert_produces_warning(expected_warning=Warning, filter_level="always",
clear=None, check_stacklevel=True):
"""
Context manager for running code that expects to raise (or not raise)
warnings. Checks that code raises the expected warning and only the
expected warning. Pass ``False`` or ``None`` to check that it does *not*
raise a warning. Defaults to ``exception.Warning``, baseclass of all
Warnings. (basically a wrapper around ``warnings.catch_warnings``).
>>> import warnings
>>> with assert_produces_warning():
... warnings.warn(UserWarning())
...
>>> with assert_produces_warning(False):
... warnings.warn(RuntimeWarning())
...
Traceback (most recent call last):
...
AssertionError: Caused unexpected warning(s): ['RuntimeWarning'].
>>> with assert_produces_warning(UserWarning):
... warnings.warn(RuntimeWarning())
Traceback (most recent call last):
...
AssertionError: Did not see expected warning of class 'UserWarning'.
..warn:: This is *not* thread-safe.
"""
with warnings.catch_warnings(record=True) as w:
if clear is not None:
# make sure that we are clearning these warnings
# if they have happened before
# to guarantee that we will catch them
if not is_list_like(clear):
clear = [clear]
for m in clear:
try:
m.__warningregistry__.clear()
except:
pass
saw_warning = False
warnings.simplefilter(filter_level)
yield w
extra_warnings = []
for actual_warning in w:
if (expected_warning and issubclass(actual_warning.category,
expected_warning)):
saw_warning = True
if check_stacklevel and issubclass(actual_warning.category,
(FutureWarning,
DeprecationWarning)):
from inspect import getframeinfo, stack
caller = getframeinfo(stack()[2][0])
msg = ("Warning not set with correct stacklevel. "
"File where warning is raised: {0} != {1}. "
"Warning message: {2}".format(
actual_warning.filename, caller.filename,
actual_warning.message))
assert actual_warning.filename == caller.filename, msg
else:
extra_warnings.append(actual_warning.category.__name__)
if expected_warning:
assert saw_warning, ("Did not see expected warning of class %r."
% expected_warning.__name__)
assert not extra_warnings, ("Caused unexpected warning(s): %r."
>
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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#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&suite=unstable test failures on every architecture. -- 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#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 debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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&suite=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 left >/dev/null 2>/dev/null mpirun -np 3 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 left >/dev/null 2>/dev/null mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 right >/dev/null 2>/dev/null mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 right >/dev/null 2>/dev/null E: Build killed with signal TERM after 150 minutes of inactivity I've reproduced this on i386, two processes are running forever (aborted after 6 hours on a fast CPU) with 100% CPU. Backtraces: Thread 3 (Thread 0xf50ffb40 (LWP 29032)): #0 0xf7ed6db9 in __kernel_vsyscall () #1 0xf70fabd3 in __GI___poll (fds=0xf47005d0, nfds=2, timeout=360) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0xf5caed4a in poll (__timeout=360, __nfds=2, __fds=0xf47005d0) at /usr/include/i386-linux-gnu/bits/poll2.h:46 #3 poll_dispatch (base=0x578eb9c0, tv=0xf50f9bfc) at poll.c:165 #4 0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, flags=) at event.c:1630 #5 0xf5c6b3bd in progress_engine (obj=0x578eb950) at runtime/opal_progress_threads.c:105 #6 0xf5df6316 in start_thread (arg=0xf50ffb40) at pthread_create.c:465 #7 0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 2 (Thread 0xf5ac5b40 (LWP 29031)): #0 0xf7ed6db9 in __kernel_vsyscall () #1 0xf71053fa in __GI_epoll_pwait (epfd=7, events=0x578ea930, maxevents=32, timeout=-1, set=0x0) at ../sysdeps/unix/sysv/linux/epoll_pwait.c:42 #2 0xf710569a in epoll_wait (epfd=7, events=0x578ea930, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #3 0xf5ca199a in epoll_dispatch (base=0x578ea7a0, tv=0x0) at epoll.c:407 #4 0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, flags=) at event.c:1630 #5 0xf5af23eb in progress_engine (obj=0x578ea7a0) at src/util/progress_threads.c:52 #6 0xf5df6316 in start_thread (arg=0xf5ac5b40) at pthread_create.c:465 #7 0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108 Thread 1 (Thread 0xf5b4fe00 (LWP 29002)): #0 0xf7ed67f5 in ?? () #1 0xf7ed6b43 in __vdso_clock_gettime () #2 0xf7112961 in __GI___clock_gettime (clock_id=1, tp=0xffb74194) at ../sysdeps/unix/clock_gettime.c:115 #3 0xf5cc3297 in opal_timer_linux_get_usec_clock_gettime () at timer_linux_component.c:197 #4 0xf5c669c3 in opal_progress () at runtime/opal_progress.c:197 #5 0xf74b5e05 in sync_wait_st (sync=) at ../opal/threads/wait_sync.h:80 #6 ompi_request_default_wait_all (count=2, requests=0xffb742e4, statuses=0x0) at request/req_wait.c:221 #7 0xf750640d in ompi_coll_base_allreduce_intra_recursivedoubling (sbuf=0x57951030, rbuf=0x57a9b400, count=2, dtype=0xf7565140 , op=0xf7573e60 , comm=0xf7569520 , module=0x57976fa0) at base/coll_base_allreduce.c:225 #8 0xe991f640 in ompi_coll_tuned_allreduce_intra_dec_fixed (sbuf=0x57951030, rbuf=0x57a9b400, count=2, dtype=0xf7565140 , op=0xf7573e60 , comm=0xf7569520 , module=0x57976fa0) at coll_tuned_decision_fixed.c:66 #9 0xf74c5b77 in PMPI_Allreduce (sendbuf=0x57951030, recvbuf=0x57a9b400, count=2, datatype=0xf7565140 , op=0xf7573e60 , comm=0xf7569520 ) at pallreduce.c:107 #10 0xf7b476cf in boost::mpi::detail::all_reduce_impl > (comm=..., in_values=0x57951030, n=n@entry=2, out_values=0x57a9b400) at /usr/include/boost/mpi/collectives/all_reduce.hpp:36 #11 0xf7b58fc0 in boost::mpi::all_reduce > (out_values=, n=2, in_values=, comm=..., op=...) at /usr/include/boost/mpi/collectives/all_reduce.hpp:93 #12 rheolef::mpi_assembly_begin, rheolef::heap_allocator > >, rheolef::disarray_rep >::message_type, rheolef::apply_iterator >, rheolef::first_op > > > (stash=..., first_stash_idx=..., last_stash_idx=..., ownership=..., receive=..., send=...) at ../../include/rheolef/mpi_assembly_begin.h:113 #13 0xf7b5a346 in rheolef::disarray_rep >::dis_entry_assembly_begin > (this=0x57acab70, my_set_op=...) at ../../include/rheolef/disarray_mpi.icc:223 #14 rheolef::disarray >::dis_entry_assembly_begin (this=) at ../../include/rheolef/disarray.h:592 #15 rheolef::disarray >::dis_entry_assembly (this=) at ../../include/rheolef/disarray.h:594 #16 rheolef::geo_rep::set_element_side_index (this=, side_dim=) at geo_mpi_get.cc:461 #17 0xf7b5f25a in rheolef::geo_rep::get (this=, ips=...) at geo_mpi_get.cc:965 #18 0xf7b60a48 in rheolef::geo_rep::load (this=, filename=..., comm=...) at geo_mpi_get.cc:989 #19 0xf7b3030a in rheolef::geo_load (name=...) at geo.cc:172 #20 0x56592bf8 in rheolef::geo_basic::geo_basic (comm=..., name="\360\265\225W\030\000\000\000\030\000\000\000\227@YV\320, "\320K\267\377\000\200\355\367\354\202\355\367\350\210\355
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://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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 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' failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 881870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: normaliz Version: 3.4.1+ds-1 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-al...@lists.debian.org Usertags: alpha Builds of normaliz for alpha (admittedly not a release architecture) have been failing lately: /<>/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, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: normaliz Source-Version: 3.5.1+ds-4 We believe that the bug you reported is fixed in the latest version of normaliz, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated normaliz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Jan 2018 05:45:25 + Source: normaliz Binary: normaliz libnormaliz3 libnormaliz-dev libnormaliz-dev-common normaliz-bin normaliz-doc Architecture: source Version: 3.5.1+ds-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jerome Benoit Description: libnormaliz-dev - math computing tools for affine monoids, rational polytopes and c libnormaliz-dev-common - math computing tools for affine monoids, rational polytopes and c libnormaliz3 - math computing tools for affine monoids, rational polytopes and c normaliz - math computing tools for affine monoids, rational polytopes and c normaliz-bin - math computing tools for affine monoids, rational polytopes and c normaliz-doc - math computing tools for affine monoids, rational polytopes and c Closes: 881870 886703 Changes: normaliz (3.5.1+ds-4) unstable; urgency=medium . * FTBFS fix release: Closes: #881870), disable OMP support on alpha arch. * Debianization: - debian/rules, see above; - debian/patches/*: - d/p/upstream-reproducible-doc.patch , introduce (Closes: #886703; - debian/copyright, format URI, secure. Checksums-Sha1: df614b9ee015e61e5c8d977ffd2b6e9dd72aabc4 3247 normaliz_3.5.1+ds-4.dsc 0a73285a53915a5cab881b7c7432dc439a659672 6148 normaliz_3.5.1+ds-4.debian.tar.xz b136896203be7cfb4fe277e50d710f4fb29e7c3f 6280 normaliz_3.5.1+ds-4_source.buildinfo Checksums-Sha256: ff32876bcc9320f6f90cff618a646a778dbfe29482ac05bbba122338f809dc36 3247 normaliz_3.5.1+ds-4.dsc 43e81b5c24a38a23cb5a20fec3854652c4e8ac55699b9fdb42ab309cf6d6f25d 6148 normaliz_3.5.1+ds-4.debian.tar.xz a0d4433cc263cbb729ca95e4d11e8ce60fbfce699362dd8d35aee9b27550f38b 6280 normaliz_3.5.1+ds-4_source.buildinfo Files: 092e7b934438bc3685adede2dbc26240 3247 math optional normaliz_3.5.1+ds-4.dsc 41611e61c2ec91e3b7edd8dee6e644d2 6148 math optional normaliz_3.5.1+ds-4.debian.tar.xz 14b0d9715c3864ca89cb798315c16ac2 6280 math optional normaliz_3.5.1+ds-4_source.buildinfo -BEGIN PGP SIGNATURE- iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAlpqxRkVHGNhbGN1bHVz QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLyn8f/24Hkmgnssv5DGNtQpcLzqVRHofO c3ESE5ds8STSy/pKrSTSCNXPvso8/+uVbnKUsGOkI4tVLLC8Lz9I2xVTodaXFyYa XiPJs9+SDmW2WEIkGbpiIw3nMEpvOZj2gxOgAa4mlQ/UiBc57mHiu7HnCVnBogZa GgH956eA6jKDRHntlaZHDwaTk5qFuc/xpjWdrPjPkurlAxQE5t8s3eDKKWzb4eKX 8Lq3BZMAwLzDthEsvIyRhIiL1e8RRZARcEQpP2+P+ES1PaWiu15bAf1Di+1ltB/8 DJ2tcSQBBerQbpGrlOE3z8u+QeEyFsDa91Nf9D/799dCM5IGnTQx1+Yv7hQy2Eyh +HXgFTzAQjYY7Zw8PK82RadYZHYw5O5na
Bug#884294: marked as done (pandas FTBFS: test failure)
Your message dated Sun, 21 Jan 2018 09:50:00 +
with message-id
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 claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
884294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 ===
_ TestSafeSort.test_unsortable _
self =
def test_unsortable(self):
# GH 13714
arr = np.array([1, 2, datetime.now(), 0, 3], dtype=object)
if compat.PY2 and not pd._np_version_under1p10:
# RuntimeWarning: tp_compare didn't return -1 or -2 for exception
with tm.assert_produces_warning(RuntimeWarning):
> pytest.raises(TypeError, algos.safe_sort, arr)
../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/test_algos.py:131:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python2.7/contextlib.py:24: in __exit__
self.gen.next()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
expected_warning = , filter_level = 'always'
clear = None, check_stacklevel = True
@contextmanager
def assert_produces_warning(expected_warning=Warning, filter_level="always",
clear=None, check_stacklevel=True):
"""
Context manager for running code that expects to raise (or not raise)
warnings. Checks that code raises the expected warning and only the
expected warning. Pass ``False`` or ``None`` to check that it does *not*
raise a warning. Defaults to ``exception.Warning``, baseclass of all
Warnings. (basically a wrapper around ``warnings.catch_warnings``).
>>> import warnings
>>> with assert_produces_warning():
... warnings.warn(UserWarning())
...
>>> with assert_produces_warning(False):
... warnings.warn(RuntimeWarning())
...
Traceback (most recent call last):
...
AssertionError: Caused unexpected warning(s): ['RuntimeWarning'].
>>> with assert_produces_warning(UserWarning):
... warnings.warn(RuntimeWarning())
Traceback (most recent call last):
...
AssertionError: Did not see expected warning of class 'UserWarning'.
..warn:: This is *not* thread-safe.
"""
with warnings.catch_warnings(record=True) as w:
if clear is not None:
# make sure that we are clearning these warnings
# if they have happened before
# to guarantee that we will catch them
if not is_list_like(clear):
clear = [clear]
for m in clear:
try:
m.__warningregistry__.clear()
except:
pass
saw_warning = False
warnings.simplefilter(filter_level)
yield w
extra_warnings = []
for actual_warning in w:
if (expected_warning and issubclass(actual_warning.category,
expected_warning)):
saw_warning = True
if check_stacklevel and issubclass(actual_warning.category,
(FutureWarning,
DeprecationWarning)):
from inspect import getframeinfo, stack
caller = getframeinfo(stack()[2][0])
msg = ("Warning not set with correct stacklevel. "
"File where warning is raised: {0} != {1}. "
"Warning message: {2}".format(
actual_warning.filename, caller.filename,
actual_warning.message))
assert
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 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/gtest.h" etc. listed in Files-Excluded header to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 884083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 be a DFSG violation, or at least the upstream tarball was not repacked as intended. Alternatively, the field is simply out of date. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: ignition-math2 Source-Version: 2.9.0+dfsg1-1 We believe that the bug you reported is fixed in the latest version of ignition-math2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 884...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jose Luis Rivero (supplier of updated ignition-math2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 Jan 2018 17:38:47 + Source: ignition-math2 Binary: libignition-math2 libignition-math2-dev Architecture: source Version: 2.9.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jose Luis Rivero Description: libignition-math2 - Ignition Robotics Math Library - Shared library libignition-math2-dev - Ignition Robotics Math Library - Development files Closes: 884083 Changes: ignition-math2 (2.9.0+dfsg1-1) unstable; urgency=medium . [ Jose Luis Rivero ] * Imported Upstream version 2.9.0 (Closes: #884083) * debhelper 11 . [ Andreas Tille ] * Removed -dbg package since it is autogenerated Checksums-Sha1: 701427d5afccf2372bc45b2d3224548bc395cce1 2302 ignition-math2_2.9.0+dfsg1-1.dsc 05c64f3596e989d2d37d6befbfadf47aad27af29 207081 ignition-math2_2.9.0+dfsg1.orig.tar.bz2 76caf836295b9202702aeda56a83f6bf961434ae 6648 ignition-math2_2.9.0+dfsg1-1.debian.tar.xz 98c5fd61dd8d45e1a5ff1f75cd5d7f7a9d5b27ab 14199 ignition-math2_2.9.0+dfsg1-1_source.buildinfo Checksums-Sha256: b9ebbf8d62c69dc12a13e8c24ab79f8560810deda42c211370d668ee2ba7f358 2302 ignition-math2_2.9.0+dfsg1-1.dsc 4238d69366b5634589bf897cd4fe4a47da8da89590fe78cd46252384f9ba3d8d 207081 ignition-math2_2.9.0+dfsg1.orig.tar.bz2 6263da8c784f4314a3196f00b1e41cc542dff86c4266bb0be0dc648383952378 6648 ignition-math2_2.9.0+dfsg1-1.debian.tar.xz 31d7dd9af5221cf2f93c218d71532069186853c822bc5d40194e73d9e1a57141 14199 ignition-math2_2.9.0+dfsg1-1_source.buildinfo Files: d0088e6fa16b89d6b619afaafae4e11e 2302 science optional ignition-math2_2.9.0+dfsg1-1.dsc a33a3c814adb072fb935cc90ae3ec375 207081 science optional ignition-math2_2.9.0+dfsg1.orig.tar.bz2 e50989916a603379cf6b52de821577e7 6648 science optional ignition-math2_2.9.0+dfsg1-1.debian.tar.xz 8f7e1c47d60d3ef6a3eb36c0d8b038e1 14199 science optional ignition-math2_2.9.0+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlpZSh4OHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtF8VA//TLawv7zQggPXEGcCsApJjOuRKKgDhiPbp5XP S9KTuN9hZskXMVKaa89ew4Di+vOBBDDNOw18hk0xctong6LcyUjTeQ4xZiDH8MIC hnzVFnZS8900UjlSk6/gFmxg0raqlAaFt7zhI5uwCyMNR3+OhCd1QVTMHP6xVHew bkBpbNo8D41Ld1P8pa5cdNVl42V4+HIms72KtmcghGlAkkmauj6c7GlZDXWPYj25 gMp1xa4JVEGrXBqCTNlERAE8GnZ+ElYgfYf7z060NUx3YYU7SrQujAo2DUuSvqYE 2r6GxNmPb0W/9Ure5SaZJcK1CSwPfpLge8GdyciT3gILAccYruT+DJCrRC54+CTl BBABWBsAko0+VVM81UbSTG8JI8qeOG9xjuIivrZV14icQO+oenIv69nMMnIXF773 TNlG9UhqkMMJldjnqW1CoqyhIzxkJW2jWAgCBFVnvhqxDI8m7W6XjdgCFk2X5Vel LNm6kEATCXen1tLWZ0EansHpQxUdy7qADEs835RPMKVGRZ1Ww+zvUndxOH5Eww6u E12kqeZNUmp/SfeXtOeUsfQsIksXOauPn5b8no
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 ===
_ TestSafeSort.test_unsortable _
self =
def test_unsortable(self):
# GH 13714
arr = np.array([1, 2, datetime.now(), 0, 3], dtype=object)
if compat.PY2 and not pd._np_version_under1p10:
# RuntimeWarning: tp_compare didn't return -1 or -2 for exception
with tm.assert_produces_warning(RuntimeWarning):
> pytest.raises(TypeError, algos.safe_sort, arr)
../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/test_algos.py:131:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python2.7/contextlib.py:24: in __exit__
self.gen.next()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
expected_warning = , filter_level = 'always'
clear = None, check_stacklevel = True
@contextmanager
def assert_produces_warning(expected_warning=Warning, filter_level="always",
clear=None, check_stacklevel=True):
"""
Context manager for running code that expects to raise (or not raise)
warnings. Checks that code raises the expected warning and only the
expected warning. Pass ``False`` or ``None`` to check that it does *not*
raise a warning. Defaults to ``exception.Warning``, baseclass of all
Warnings. (basically a wrapper around ``warnings.catch_warnings``).
>>> import warnings
>>> with assert_produces_warning():
... warnings.warn(UserWarning())
...
>>> with assert_produces_warning(False):
... warnings.warn(RuntimeWarning())
...
Traceback (most recent call last):
...
AssertionError: Caused unexpected warning(s): ['RuntimeWarning'].
>>> with assert_produces_warning(UserWarning):
... warnings.warn(RuntimeWarning())
Traceback (most recent call last):
...
AssertionError: Did not see expected warning of class 'UserWarning'.
..warn:: This is *not* thread-safe.
"""
with warnings.catch_warnings(record=True) as w:
if clear is not None:
# make sure that we are clearning these warnings
# if they have happened before
# to guarantee that we will catch them
if not is_list_like(clear):
clear = [clear]
for m in clear:
try:
m.__warningregistry__.clear()
except:
pass
saw_warning = False
warnings.simplefilter(filter_level)
yield w
extra_warnings = []
for actual_warning in w:
if (expected_warning and issubclass(actual_warning.category,
expected_warning)):
saw_warning = True
if check_stacklevel and issubclass(actual_warning.category,
(FutureWarning,
DeprecationWarning)):
from inspect import getframeinfo, stack
caller = getframeinfo(stack()[2][0])
msg = ("Warning not set with correct stacklevel. "
"File where warning is raised: {0} != {1}. "
"Warning message: {2}".format(
actual_warning.filename, caller.filename,
actual_warning.message))
assert actual_warning.filename == caller.filename, msg
else:
extra_warnings.append(actual_warning.category.__name__)
if expected_warning:
assert saw_warning, ("Did not see expected warning of class %r."
>% expected_warning.__name__)
E AssertionError: Did not see expected warning of class
'RuntimeWarning'.
../debian/tmp/usr/lib/python2.7/dist-packages/pandas/util/testing.py:2655:
AssertionError
=== warnings summary ===
debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/dtypes/test_missing.py::test_array_equivalent_compat
/usr/lib/python2.7/dist-packages/numpy/core/numeric.py:2604: FutureWarning:
elementwise == comparison failed and returning scalar instead; this will raise
an error or perform elementwise comparison in the future.
return bool(asarray(a
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 be a DFSG violation, or at least the upstream tarball was not repacked as intended. Alternatively, the field is simply out of date. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- -- 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#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_utils.cmake. This is probably a DFSG violation, or at the upstream tarball was not repacked as intended. Alternatively, the field is simply out of date. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- -- 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#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 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 failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 876870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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-0.8.0~r57502' echo "Fue un malentendido." | apertium -d . es-en | tee .test-mt It went a misunderstanding. 1c1 < It was a misunderstanding. --- > It went a misunderstanding. Makefile:784: recipe for target 'test' failed make[1]: *** [test] Error 1 --- End Message --- --- Begin Message --- Source: apertium-en-es Source-Version: 0.8.0~r57502-3 We believe that the bug you reported is fixed in the latest version of apertium-en-es, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated apertium-en-es package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 07 Dec 2017 14:07:11 +0530 Source: apertium-en-es Binary: apertium-en-es Architecture: source all Version: 0.8.0~r57502-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Kartik Mistry Description: apertium-en-es - Apertium translation data for the English-Spanish pair Closes: 876870 Changes: apertium-en-es (0.8.0~r57502-3) unstable; urgency=medium . * Added patch to fix FTBFS in test suites. Thanks to Andreas Moog. (Closes: #876870) * debian/control: + Updated Standards-Version to 4.1.2 Checksums-Sha1: 8d52905e3d63e3f09da5f0fedcae911fd5eab066 2174 apertium-en-es_0.8.0~r57502-3.dsc 98f22a2d1868929ba621fd22927d356e54fc04af 2852 apertium-en-es_0.8.0~r57502-3.debian.tar.xz 71a404b458fd5a7a3fd86b402c49995da0a9fd66 2137020 apertium-en-es_0.8.0~r57502-3_all.deb 180b570aa40a4838bdc913d0c37cb2e85676e800 6201 apertium-en-es_0.8.0~r57502-3_amd64.buildinfo Checksums-Sha256: e4535d57fad681cd871fb040c29d35b63f4fcad35bceebd9ff6e19fa6968 2174 apertium-en-es_0.8.0~r57502-3.dsc 7393313337b10cc9e26c6a79fbf04954b7a713f71067406845f8967c62755fb3 2852 apertium-en-es_0.8.0~r57502-3.debian.tar.xz 0fb97da03f0eeda3cf939071063ba3376f7d6f78ef45c16ae5dd6a89f5d79ca1 2137020 apertium-en-es_0.8.0~r57502-3_all.deb 5aeef6e3dee8e9fdfe654b396071fe50f93e308d6387498da6c318eff8e5c5c0 6201 apertium-en-es_0.8.0~r57502-3_amd64.buildinfo Files: 4833e194674f553944fe57102e576a33 2174 science optional apertium-en-es_0.8.0~r57502-3.dsc 1585d8fe8e994f94c421ed6b638ab221 2852 science optional apertium-en-es_0.8.0~r57502-3.debian.tar.xz 9c46142ff6bf45d7e7a3cd8f6085d439 2137020 science optional apertium-en-es_0.8.0~r57502-3_all.deb 3d0a63db32cb001119713e2c6fc7f9e1 6201 science optional apertium-en-es_0.8.0~r57502-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAlopBG0ACgkQAsHT8ng6 pN7q6xAAqH0bgKdvf5et4QOExT41iWcV9ke81LWyKynuNqpx7f6JnHo+z3bPXA/Y ixKbCQFwYx+9oan6dzPdBxEiI4wO/AlaiW8Sj5CLermqnaJKLQGf0/426RY79Vw8 217LNMgN9YuCfqdYHjVSDb8k7V96z/Bz8fWrUFplF7bfbFT4DFBPFSecYHq8s9m3 lIP+TqQ3r4ui4tfpYOltGpzE1ruv0h+Ix71WGUNeH+Pw0XdtCIMBILFG+pSraJT2 5+pUOzICLdPQo2O5c7mHvXC/wmHUtv9PKXMjop0SowVV8BX2EAXxDyfpg+tNt03r pOKirca9kszfmuR3BK1aDg4GhFlyc4eEAZpKY5MkxzIuY0KNquC0aP0BpUS9iqEY KKm+xWZ3M00Mya1w3vrNH1+pRpLFDYSv66Q6Kj1qcaS5iLpjLhb01X5+ZU2+miLo rA0G7+URAZ3QvyNTAXIm0yFx3pl9r5M4y4Paw6mQFMKjn0k/3N6NkmkLz7uKgKqU 46vRAYJ2bihi3JrHE8CFpEWrU2IVgqAZ2vOtSfi3pLWmsy5/P4tX6awWGReZr9xL yI4yB0GPZUlwV02bv0mPqk/AH2aumwIN5KVHDp+iEXIe8F0HQu8BRcZvycgM4lzx nvCEBoTYptaJIr9lPfF8xKf2qLMBW9LYaOpgmKKOFwo+TcypY38= =VaOe -END PGP SIGNATURE End Message --- -- debian-science-maintainers mai
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 successfully. Please consider applying the attached patch. Helmut diff --minimal -Nru admesh-0.98.3/debian/changelog admesh-0.98.3/debian/changelog --- admesh-0.98.3/debian/changelog 2017-11-25 14:16:13.0 +0100 +++ admesh-0.98.3/debian/changelog 2017-11-29 21:27:57.0 +0100 @@ -1,3 +1,10 @@ +admesh (0.98.3-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Honour DEB_BUILD_OPTIONS=nocheck. (Closes: #-1) + + -- Helmut Grohne Wed, 29 Nov 2017 21:27:57 +0100 + admesh (0.98.3-2) unstable; urgency=medium [ Graham Inggs ] diff --minimal -Nru admesh-0.98.3/debian/rules admesh-0.98.3/debian/rules --- admesh-0.98.3/debian/rules 2017-11-25 14:13:59.0 +0100 +++ admesh-0.98.3/debian/rules 2017-11-29 21:27:57.0 +0100 @@ -5,5 +5,7 @@ %: dh $@ --with autoreconf +ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),) override_dh_auto_test: ./debian/regression_test/regression_test +endif -- 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#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 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 on line: 547 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 882420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: segyio Version: 1.3.3-1 Severity: important Tags: upstream Justification: fails to build from source User: debian-s...@lists.debian.org Usertags: s390x The build of segyio for s390x failed with a strange error, per the below excerpt from https://buildd.debian.org/status/fetch.php?pkg=segyio&arch=s390x&ver=1.3.3-1&stamp=1511256490&raw=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 please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: segyio Source-Version: 1.3.8-1 We believe that the bug you reported is fixed in the latest version of segyio, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jørgen Kvalsvik (supplier of updated segyio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Nov 2017 13:02:52 +0100 Source: segyio Binary: libsegyio1 libsegyio-dev segyio-bin python3-segyio Architecture: source Version: 1.3.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jørgen Kvalsvik Description: libsegyio-dev - SEG-Y read/write library for seismic processing (development) libsegyio1 - SEG-Y read/write library for seismic processing (runtime) python3-segyio - SEG-Y read/write library for seismic processing (python3 bindings segyio-bin - SEG-Y read/write library for seismic processing (shell utilities) Closes: 882420 882421 Changes: segyio (1.3.8-1) unstable; urgency=medium . * New upstream release * Builds on platforms where long is 32bit (Closes: #882420) * Builds on sparc64 (Closes: #882421) * Upgrade to Standards-Version 4.1.1 * Add libc6-dev to tests dependencies * Add python3-setuptools and python3-setuptools-scm to build dependencies * Remove pycmake licence entry Checksums-Sha1: a3c466b6bdd5e2ac1be3b2683c28e112e20aa70a 2291 segyio_1.3.8-1.dsc 24c699cd8ceb44e69233a36075e2a439bd3404a3 131190 segyio_1.3.8.orig.tar.gz 24583638a32bb9e1ca3bcb927e40f152a2234679 2904 segyio_1.3.8-1.debian.tar.xz 86d5967171f8d2b337e0d52a3fc8c710e2b066a8 8708 segyio_1.3.8-1_amd64.buildinfo Checksums-Sha256: dd3dc3b413c6cd4836df265d9516d9bf8172c02452c8010b43557201e0ec6eac 2291 segyio_1.3.8-1.dsc 8e8b1548818eab47ebaba55e1a7081c8aac0e24e6c9132688db74245e933e512 131190 segyio_1.3.8.orig.tar.gz 35a3f8cd1ef4ce95fd464ef79e02a147d4f47148361fffe6435cfab9c35e5429 2904 segyio_1.3.8-1.debian.tar.xz 9713badacccf873457718e87c7b80bf8562d59d648f4c60e745d781b8feaf0cc 8708 segyio_1.3.8-1_amd64.buildinfo Files: 09b71fc999b94a6ea2232159e35ee7a4 2291 science optional segyio_1.3.8-1.dsc 6982a71791239ef442434297522ec84c 131190 science optional segyio_1.3.8.orig.tar.gz 3ec1098219e1ac76c087d396af6f8f07 2904 science optional segyio_1.3.8-1.debian.tar.xz e06e4b35cb1245c84e3a84b43fc13af4 8708 science optional segyio_1.3.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAloZdmsACgkQLOzpNQ7O vkoFlBAAq4Awc/hYy+G3uAeNfhl+D38J31gpY6pvXgPJ2VLGvleJGw3FT7uFh5SS Gc8Y6sLcAAgaMp42jeHRo7AcN0IGXtljs3b9Qjo3wj8aqyDojdc8CI7d5lOuSeCl d6gFI7FKdSZCG8Wd93nlUPSXK6HfnJG74OSjBDGAZas+t6ZWUI7dKoH6NULaBgHH qJ97nAnW1JK9MnlXNzYivXTBovfStwltWI0CYlkR7dehutoMCTg0REqksn/NpP0x VQycNzNbv7296PnJGA8a3CL0Ag2qSk2VwU4cm5ymYs7f
Bug#881453: marked as done (primesieve FTBFS on i386: test failures)
Your message dated Fri, 24 Nov 2017 15:07:19 + with message-id 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 that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 881453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: primesieve Version: 6.2+ds-1 Severity: serious Tags: patch https://buildd.debian.org/status/fetch.php?pkg=primesieve&arch=i386&ver=6.2%2Bds-1&stamp=1510442732&raw=0 ... dh_auto_test -a -O--builddirectory=_build cd _build && make -j4 test ARGS\+=-j4 make[1]: Entering directory '/<>/primesieve-6.2+ds/_build' Running tests... /usr/bin/ctest --force-new-ctest-process -j4 Test project /<>/primesieve-6.2+ds/_build Start 1: atomic Start 2: count_primes1 Start 3: count_primes2 Start 4: count_primes3 1/24 Test #1: atomic ... Passed0.28 sec 2/24 Test #2: count_primes1 Passed0.30 sec Start 5: count_quadruplets Start 6: count_quintuplets 3/24 Test #5: count_quadruplets .... Passed0.90 sec 4/24 Test #6: count_quintuplets Passed1.08 sec Start 7: count_sextuplets Start 8: count_triplets 5/24 Test #8: count_triplets ... Passed0.89 sec 6/24 Test #7: count_sextuplets . Passed1.11 sec Start 9: count_twins Start 10: cpu_info 7/24 Test #10: cpu_info . Passed 0.31 sec Start 11: floorPow2 8/24 Test #11: floorPow2 ***Failed0.21 sec floorPow2(1) = 1 OK floorPow2(2) = 2 OK floorPow2(3) = 2 OK floorPow2(4) = 4 OK floorPow2(5) = 4 OK floorPow2(6) = 4 OK floorPow2(7) = 4 OK floorPow2(8) = 8 ERROR Start 12: generate_n_primes1 9/24 Test #9: count_twins .. Passed0.94 sec Start 13: generate_primes1 10/24 Test #13: generate_primes1 . Passed0.30 sec Start 14: ilog2 11/24 Test #14: ilog2 ***Failed0.30 sec ilog2(1) = 0 OK ilog2(2) = 1 OK ilog2(3) = 1 OK ilog2(4) = 2 OK ilog2(5) = 2 OK ilog2(6) = 2 OK ilog2(7) = 2 OK ilog2(8) = 3 ERROR Start 15: isqrt 12/24 Test #15: isqrt Passed 0.89 sec Start 16: next_prime1 13/24 Test #16: next_prime1 .. Passed3.21 sec Start 17: nth_prime1 14/24 Test #17: nth_prime1 ... Passed3.52 sec Start 18: nth_prime2 15/24 Test #12: generate_n_primes1 ... Passed 15.50 sec Start 19: nth_prime3 16/24 Test #3: count_primes2 Passed 22.85 sec Start 20: prev_prime1 17/24 Test #18: nth_prime2 ... Passed 16.06 sec Start 21: generate_n_primes2 18/24 Test #21: generate_n_primes2 ... Passed0.61 sec Start 22: generate_primes2 19/24 Test #4: count_primes3 Passed 29.38 sec Start 23: next_prime2 20/24 Test #19: nth_prime3 ... Passed 23.31 sec Start 24: prev_prime2 21/24 Test #20: prev_prime1 .. Passed 22.00 sec 22/24 Test #24: prev_prime2 .. Passed3.24 sec 23/24 Test #22: generate_primes2 ..... Passed 19.13 sec 24/24 Test #23: next_prime2 .. Passed 21.86 sec 92% tests passed, 2 tests failed out of 24 Total Test time (real) = 51.51 sec The following tests FAILED: 11 - floorPow2 (Failed) 14 - ilog2 (Failed) Errors while running CTest Makefile:121: recipe for target 'test' failed make[1]: *** [test] Error 8 This can be fixed with: --- debian/rules.old2017-11-12 00:16:05.0 + +++ debian/rules2017-11-12 00:17:52.0 + @@ -17,6 +17,11 @@ CXXFLAGS := $(subst -O2,-O3,$(CXXFLAGS)) endif +ifeq ($(DEB_HOST_ARCH),i386) +CFLAGS += -ffloat-store +CXXFLAGS += -ffloat-store +endif + default: @uscan --no-conf --dehs --report || true --- End Message --- --- Begin Message --- Source: primesieve Source-Version: 6.3+ds-1 We believe that the bug you reported is fixed in the latest version of primesieve, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and th
Bug#882420: segyio: FTBFS on s390x: Assertion failed in file: /<>/lib/test/segy.c on line: 547
From: Aaron M. Ucko 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 Justification: fails to build from source User: debian-s...@lists.debian.org Usertags: s390x The build of segyio for s390x failed with a strange error, per the below excerpt from https://buildd.debian.org/status/fetch.php?pkg=segyio&arch=s390x&ver=1.3.3-1&stamp=1511256490&raw=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 please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu Hi, I've patched this in upstream and in the alioth git repo https://anonscm.debian.org/cgit/debian-science/packages/segyio.git/commit/?id=1b05cb8db357bb0bc091674693657c2182cece99 but I've yet to upload it as some minor details are missing still. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorized use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you -- 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#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 Justification: fails to build from source User: debian-s...@lists.debian.org Usertags: s390x The build of segyio for s390x failed with a strange error, per the below excerpt from https://buildd.debian.org/status/fetch.php?pkg=segyio&arch=s390x&ver=1.3.3-1&stamp=1511256490&raw=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 please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- 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#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 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 as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 881869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: normaliz Version: 3.4.1+ds-1 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-powe...@lists.debian.org Usertags: powerpc ppc64 ppc64el Builds of normaliz 3.4 for arm64, ppc64el, s390x, and the non-release 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 architectures!), but perhaps you can reproduce the problem on a porter box. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: normaliz Source-Version: 3.4.1+ds-2 We believe that the bug you reported is fixed in the latest version of normaliz, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated normaliz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2017 15:07:15 + Source: normaliz Binary: normaliz libnormaliz3 libnormaliz-dev libnormaliz-dev-common normaliz-bin normaliz-doc Architecture: source Version: 3.4.1+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jerome Benoit Description: libnormaliz-dev - math computing tools for affine monoids, rational polytopes and c libnormaliz-dev-common - math computing tools for affine monoids, rational polytopes and c libnormaliz3 - math computing tools for affine monoids, rational polytopes and c normaliz - math computing tools for affine monoids, rational polytopes and c normaliz-bin - math computing tools for affine monoids, rational polytopes and c normaliz-doc - math computing tools for affine monoids, rational polytopes and c Closes: 881869 881883 Changes: normaliz (3.4.1+ds-2) unstable; urgency=medium . * Debianization: - debian/control: - Breaks+Replaces field, add (Closes: #881883); - debian/patches/*: - d/p/upstream-test-extremely_sensitive_tests-neutralize.patch, introduce and submit (Closes: #881869); - d/p/debianization.patch, refresh. Checksums-Sha1: da507b56087d5049a693bccceeed4ad225829b1b 3078 normaliz_3.4.1+ds-2.dsc 0124cc9064f51c79c6de576467e743a2c24210ca 5308 normaliz_3.4.1+ds-2.debian.tar.xz f28ce53f2b3fa2d8a0efd0ec6269162fc63706f2 6113 normaliz_3.4.1+ds-2_source.buildinfo Checksums-Sha256: 38e5caf365ead46680b1e8125c4af0a08639705fae196811ac3bc944148b1b33 3078 normaliz_3.4.1+ds-2.dsc 8ff408e76da049b6947405fa131e4579ada12972619d8e9d963b8199cfa58fe0 5308 normaliz_3.4.1+ds-2.debian.tar.xz 5d496f45e619469e2096074fca64fcd3ca905c01e7d659e0b08f9c4fc83b3c64 6113 normaliz_3.4.1+ds-2_source.buildinfo Files: 1382f97eb267605ee216499b49c3c139 3078 math optional normaliz_3.4.1+ds-2.dsc 0dbe861d76dc5eb3dc6e640a124f792f 5308 math optional normaliz_3.4.1+ds-2.debian.tar.xz bee8633a420dc9dad41e4c121a8a4d84 6113 math optional normaliz_3.4.1+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAloO/T8VHGNhbGN1bHVz QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLIsIgAK0tDyiZGxEWKcYgl3XqvYRl63zq YffAFQQv6v1wiJL5JlkRxAC+AVyIzCQWTnezLFmqZaeltNj0bpO8Ya/7N5mKcAXb Enegw+QZ0zJawYJ0AFCrieu+mKHo2rz5m6icBCZYgAYOtDrjiudp0GF/nSD77SF7 ZDIGOF19i8YRJQxGMYsGFTB2DZhZg0Jswreju14gIBzmQx+ILgdpb3mohLZivpbn n/Tn2HP7F93s6GQj7vEDXwjJHr5G
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 AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B signature.asc Description: OpenPGP digital signature -- 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#881870: normaliz: FTBFS on alpha: recipe for target 'test-v/medium.diff' failed
Source: normaliz Version: 3.4.1+ds-1 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-al...@lists.debian.org Usertags: alpha Builds of normaliz for alpha (admittedly not a release architecture) have been failing lately: /<>/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, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- 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#881869: FTBFS: recipe for target 'test-/5x5PF.diff' failed
Source: normaliz Version: 3.4.1+ds-1 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-powe...@lists.debian.org Usertags: powerpc ppc64 ppc64el Builds of normaliz 3.4 for arm64, ppc64el, s390x, and the non-release 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 architectures!), but perhaps you can reproduce the problem on a porter box. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- 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#881453: primesieve FTBFS on i386: test failures
Source: primesieve Version: 6.2+ds-1 Severity: serious Tags: patch https://buildd.debian.org/status/fetch.php?pkg=primesieve&arch=i386&ver=6.2%2Bds-1&stamp=1510442732&raw=0 ... dh_auto_test -a -O--builddirectory=_build cd _build && make -j4 test ARGS\+=-j4 make[1]: Entering directory '/<>/primesieve-6.2+ds/_build' Running tests... /usr/bin/ctest --force-new-ctest-process -j4 Test project /<>/primesieve-6.2+ds/_build Start 1: atomic Start 2: count_primes1 Start 3: count_primes2 Start 4: count_primes3 1/24 Test #1: atomic ... Passed0.28 sec 2/24 Test #2: count_primes1 Passed0.30 sec Start 5: count_quadruplets Start 6: count_quintuplets 3/24 Test #5: count_quadruplets .... Passed0.90 sec 4/24 Test #6: count_quintuplets Passed1.08 sec Start 7: count_sextuplets Start 8: count_triplets 5/24 Test #8: count_triplets ... Passed0.89 sec 6/24 Test #7: count_sextuplets . Passed1.11 sec Start 9: count_twins Start 10: cpu_info 7/24 Test #10: cpu_info . Passed 0.31 sec Start 11: floorPow2 8/24 Test #11: floorPow2 ***Failed0.21 sec floorPow2(1) = 1 OK floorPow2(2) = 2 OK floorPow2(3) = 2 OK floorPow2(4) = 4 OK floorPow2(5) = 4 OK floorPow2(6) = 4 OK floorPow2(7) = 4 OK floorPow2(8) = 8 ERROR Start 12: generate_n_primes1 9/24 Test #9: count_twins .. Passed0.94 sec Start 13: generate_primes1 10/24 Test #13: generate_primes1 . Passed0.30 sec Start 14: ilog2 11/24 Test #14: ilog2 ***Failed0.30 sec ilog2(1) = 0 OK ilog2(2) = 1 OK ilog2(3) = 1 OK ilog2(4) = 2 OK ilog2(5) = 2 OK ilog2(6) = 2 OK ilog2(7) = 2 OK ilog2(8) = 3 ERROR Start 15: isqrt 12/24 Test #15: isqrt Passed 0.89 sec Start 16: next_prime1 13/24 Test #16: next_prime1 .. Passed3.21 sec Start 17: nth_prime1 14/24 Test #17: nth_prime1 ... Passed3.52 sec Start 18: nth_prime2 15/24 Test #12: generate_n_primes1 ... Passed 15.50 sec Start 19: nth_prime3 16/24 Test #3: count_primes2 Passed 22.85 sec Start 20: prev_prime1 17/24 Test #18: nth_prime2 ... Passed 16.06 sec Start 21: generate_n_primes2 18/24 Test #21: generate_n_primes2 ... Passed0.61 sec Start 22: generate_primes2 19/24 Test #4: count_primes3 Passed 29.38 sec Start 23: next_prime2 20/24 Test #19: nth_prime3 ... Passed 23.31 sec Start 24: prev_prime2 21/24 Test #20: prev_prime1 .. Passed 22.00 sec 22/24 Test #24: prev_prime2 .. Passed3.24 sec 23/24 Test #22: generate_primes2 ..... Passed 19.13 sec 24/24 Test #23: next_prime2 .. Passed 21.86 sec 92% tests passed, 2 tests failed out of 24 Total Test time (real) = 51.51 sec The following tests FAILED: 11 - floorPow2 (Failed) 14 - ilog2 (Failed) Errors while running CTest Makefile:121: recipe for target 'test' failed make[1]: *** [test] Error 8 This can be fixed with: --- debian/rules.old2017-11-12 00:16:05.0 + +++ debian/rules2017-11-12 00:17:52.0 + @@ -17,6 +17,11 @@ CXXFLAGS := $(subst -O2,-O3,$(CXXFLAGS)) endif +ifeq ($(DEB_HOST_ARCH),i386) +CFLAGS += -ffloat-store +CXXFLAGS += -ffloat-store +endif + default: @uscan --no-conf --dehs --report || true -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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 to the same values previously set > retitle -1 testpath does not install .egg-info or .dist-info, making it > invisible to pip Bug #880241 [src:testpath] sagenb-export: FTBFS: Test failures Changed Bug title to 'testpath does not install .egg-info or .dist-info, making it invisible to pip' from 'sagenb-export: FTBFS: Test failures'. > affects -1 sagenb-export Bug #880241 [src:testpath] testpath does not install .egg-info or .dist-info, making it invisible to pip Added indication that 880241 affects sagenb-export -- 880241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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#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 makes it invisible to pip. It then tries downloading testpath from the internet, causing the below error. Upstream testpath uses their own custom tool "flit" to generate a .dist-info directory - which you can see the contents of by running `pip install testpath` then looking in ~/.local/lib/python2.7/site-packages/testpath-0.3.1.dist-info/. An alternative to packaging flit and then modifying testpath to use flit, would be to simply add ~/.local/lib/python2.7/site-packages/testpath-0.3.1.dist-info/METADATA to our Debian packaging and install it in /usr/lib/pythonX.Y/dist-packages/testpath-0.3.1.egg-info, etc X On Mon, 30 Oct 2017 20:32:00 +0100 Lucas Nussbaum wrote: > Source: sagenb-export > Version: 3.2-3 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20171030 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): > > r = adapter.send(request, **kwargs) > > File > > "/<>/.tox/python3/share/python-wheels/CacheControl-0.11.7-py2.py3-none-any.whl/cachecontrol/adapter.py", > > line 47, in send > > resp = super(CacheControlAdapter, self).send(request, **kw) > > File > > "/<>/.tox/python3/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/adapters.py", > > line 423, in send > > timeout=timeout > > File > > "/<>/.tox/python3/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", > > line 643, in urlopen > > _stacktrace=sys.exc_info()[2]) > > File > > "/<>/.tox/python3/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/util/retry.py", > > line 315, in increment > > total -= 1 > > TypeError: unsupported operand type(s) for -=: 'Retry' and 'int' > > > > python3 installed: > > bleach==2.0.0,decorator==4.1.2,entrypoints==0.2.3.post1,html5lib==0.9,ipykernel==4.6.1,ipython==5.5.0,ipython-genutils==0.2.0,Jinja2==2.9.6,jsonschema==2.5.1,jupyter-client==5.1.0,jupyter-core==4.3.0,MarkupSafe==1.0,mistune==0.8,nbconvert==5.3.1,nbformat==4.4.0,notebook==4.2.3,pandocfilters==1.4.2,pexpect==4.2.1,pickleshare==0.7.4,pkg-resources==0.0.0,pluggy==0.4.0,prompt-toolkit==1.0.14,py==1.4.34,Pygments==2.2.0,python-dateutil==2.6.1,pyzmq==16.0.2,simplegeneric==0.8.1,six==1.11.0,terminado==0.6,tornado==4.5.1,tox==2.5.0,traitlets==4.3.2,virtualenv==15.1.0,wcwidth==0.1.7,webencodings==0.5 > > ___ summary > > > > ERROR: python: InvocationError: /<>/.tox/python/bin/pip > > install /<>/.tox/dist/sagenb_export-3.2.zip (see > > /<>/.tox/python/log/python-1.log) > > ERROR: python3: InvocationError: /<>/.tox/python3/bin/pip > > install /<>/.tox/dist/sagenb_export-3.2.zip (see > > /<>/.tox/python3/log/python3-1.log) > > debian/rules:30: recipe for target 'override_dh_auto_test' failed > > The full build log is available from: >http://aws-logs.debian.net/2017/10/30/sagenb-export_3.2-3_unstable.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. > > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- 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#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 at https://buildd.debian.org/status/fetch.php?pkg=cvc4&arch=sparc64&ver=1.5-1&stamp=1509309061&raw=0 Most if not all of these failures stemmed from bus errors, which generally correspond to unaligned memory access attempts. Could you please take a look? Thanks! FTR, the overall testing summary was === TESTING SUMMARY = 150 TOTAL, 6 PASS, 144 FAIL /.../production/test/regress/regress0/test-suite.log 32 TOTAL, 32 FAIL /.../production/test/regress/regress0/arith/test-suite.log 14 TOTAL, 14 FAIL /.../production/test/regress/regress0/arith/integers/test-suite.log 32 TOTAL, 32 FAIL /.../production/test/regress/regress0/arrays/test-suite.log 37 TOTAL, 37 FAIL /.../production/test/regress/regress0/aufbv/test-suite.log 11 TOTAL, 11 FAIL /.../production/test/regress/regress0/auflia/test-suite.log 86 TOTAL, 86 FAIL /.../production/test/regress/regress0/bv/test-suite.log 65 TOTAL, 65 FAIL /.../production/test/regress/regress0/bv/core/test-suite.log 62 TOTAL, 1 PASS, 61 FAIL /.../production/test/regress/regress0/datatypes/test-suite.log 18 TOTAL, 18 FAIL /.../production/test/regress/regress0/decision/test-suite.log 8 TOTAL, 8 FAIL /.../production/test/regress/regress0/expect/test-suite.log 56 TOTAL, 56 FAIL /.../production/test/regress/regress0/fmf/test-suite.log 4 TOTAL, 4 FAIL /.../production/test/regress/regress0/lemmas/test-suite.log 29 TOTAL, 29 FAIL /.../production/test/regress/regress0/nl/test-suite.log 4 TOTAL, 4 FAIL /.../production/test/regress/regress0/parser/test-suite.log 18 TOTAL, 18 FAIL /.../production/test/regress/regress0/precedence/test-suite.log 16 TOTAL, 16 FAIL /.../production/test/regress/regress0/preprocess/test-suite.log 24 TOTAL, 24 FAIL /.../production/test/regress/regress0/push-pop/test-suite.log 21 TOTAL, 21 FAIL /.../production/test/regress/regress0/push-pop/arith/test-suite.log 51 TOTAL, 51 FAIL /.../production/test/regress/regress0/push-pop/boolean/test-suite.log 74 TOTAL, 74 FAIL /.../production/test/regress/regress0/quantifiers/test-suite.log 93 TOTAL, 93 FAIL /.../production/test/regress/regress0/rels/test-suite.log 7 TOTAL, 7 FAIL /.../production/test/regress/regress0/rewriterules/test-suite.log 39 TOTAL, 39 FAIL /.../production/test/regress/regress0/sep/test-suite.log 68 TOTAL, 68 FAIL /.../production/test/regress/regress0/sets/test-suite.log 70 TOTAL, 70 FAIL /.../production/test/regress/regress0/strings/test-suite.log 33 TOTAL, 33 FAIL /.../production/test/regress/regress0/sygus/test-suite.log 27 TOTAL, 27 FAIL /.../production/test/regress/regress0/tptp/test-suite.log 33 TOTAL, 33 FAIL /.../production/test/regress/regress0/uf/test-suite.log 20 TOTAL, 20 FAIL /.../production/test/regress/regress0/uflia/test-suite.log 20 TOTAL, 20 FAIL /.../production/test/regress/regress0/uflra/test-suite.log 47 TOTAL, 47 FAIL /.../production/test/regress/regress0/unconstrained/test-suite.log 5 TOTAL, 2 PASS, 3 FAIL /.../production/test/system/test-suite.log 4 TOTAL, 4 PASSin unit === TESTING SUMMARY = -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- 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#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&ver=1.5-1 So far, these errors have occurred on arm64, ppc64el, s390x, and the non-release architectures powerpc, ppc64, and sparc64. On almost all of these architectures, the testing summary took the form === TESTING SUMMARY = 150 TOTAL, 136 PASS, 14 FAIL /.../production/test/regress/regress0/test-suite.log 32 TOTAL, 32 PASS in regress/regress0/arith 14 TOTAL, 14 PASS in regress/regress0/arith/integers 32 TOTAL, 12 PASS, 20 FAIL /.../production/test/regress/regress0/arrays/test-suite.log 37 TOTAL, 31 PASS, 6 FAIL /.../production/test/regress/regress0/aufbv/test-suite.log 11 TOTAL, 11 PASS in regress/regress0/auflia 86 TOTAL, 60 PASS, 26 FAIL /.../production/test/regress/regress0/bv/test-suite.log 65 TOTAL, 4 PASS, 61 FAIL /.../production/test/regress/regress0/bv/core/test-suite.log 62 TOTAL, 62 PASS in regress/regress0/datatypes 18 TOTAL, 12 PASS, 6 FAIL /.../production/test/regress/regress0/decision/test-suite.log [long run of fully successful tests elided] 33 TOTAL, 9 PASS, 24 FAIL /.../production/test/regress/regress0/uf/test-suite.log [shorter run of fully successful tests elided] === TESTING SUMMARY = The one exception was sparc64, which encountered many more errors; I'll report a separate bug for that architecture. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- 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#870217: marked as done (glm: FTBFS with gcc-7: Test failures)
Your message dated Tue, 24 Oct 2017 14:49:38 + with message-id 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 claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 870217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 - test-core_type_mat3x4 (Failed) 18 - test-core_type_mat4x4 (Failed) Errors while running CTest Makefile:98: recipe for target 'test' failed make[2]: *** [test] Error 8 make[2]: Leaving directory '/build/glm-0.9.8.4/obj-x86_64-linux-gnu' debian/rules:22: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/build/glm-0.9.8.4' debian/rules:7: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler --- End Message --- --- Begin Message --- Source: glm Source-Version: 0.9.8.4-1.1 We believe that the bug you reported is fixed in the latest version of glm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 870...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated glm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 22 Oct 2017 15:21:32 +0200 Source: glm Binary: libglm-dev libglm-doc Architecture: source Version: 0.9.8.4-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Tobias Frost Description: libglm-dev - C++ library for OpenGL GLSL type-based mathematics libglm-doc - documentation for the OpenGL Mathematics (GLM) library Closes: 870217 Changes: glm (0.9.8.4-1.1) unstable; urgency=medium . * Non-maintainer upload. * Cherrypick patch from upstream for FTBFS for GCC-7 (Closes: #870217) * Replace priority extra with optional. Fixes linitian: priority-extra-is-replaced-by-priority-optional * Remove Testsuite: autopkgtest from d/control as it is no longer needed. Fixes lintian unnecessary-testsuite-autopkgtest-header Checksums-Sha1: a6083f2f1f4720e9e74539a771fb9bf3d7e9fa8e 2055 glm_0.9.8.4-1.1.dsc eeb2a5039912b597f5b1bc828464c9977d9ad630 5912 glm_0.9.8.4-1.1.debian.tar.xz 469ecbbbf920edaa0959be28f39137e3bd7bbbd7 6691 glm_0.9.8.4-1.1_source.buildinfo Checksums-Sha256: 591269666263fd4b72df3b665533e5e41fda7ee0af90137c7fd9f07e6e68fa9d 2055 glm_0.9.8.4-1.1.dsc 649471b75bb82bce992c2ce8978b69a52a0d5180900484d8640c09b8453eba8d 5912 glm_0.9.8.4-1.1.debian.tar.xz e7eb5fcecc7ee5740fe5b9f761b9730d6c0fe6f15860dd422cc4df558e77131b 6691 glm_0.9.8.4-1.1_source.buildinfo Files: c6c9bf927c33569feac48c21e5af7019 2055 libs optional glm_0.9.8.4-1.1.dsc 4c8ec22bd8e452bd7e10449583839d79 5912 libs optional glm_0.9.8.4-1.1.debian.tar.xz 3f848f67ca1883b743efa578d7d4d229 6691 libs optional glm_0.9.8.4-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlnsnosACgkQkWT6HRe9 XTYX7w/+MlyXvIzvEK7nUnCqIJq6tpj+kU8TFCCe9tv10c4VLxbtbCxJZbEpyDFE W763XH8gc6m3Q2x2Tjtpjg3rt+SNMyEdRN7djP9cdlHIkygT/O8a7vqx7jdQmcS6 L3q4ps4roqrGLZLvf6EqfpAqia28t40omVJZ0tQTOKy635pwDPs6NxNz5AavDEXW Lp9N52Gs3pH22gUB3QNzeY/ogV0jIna6pRJmyQ3RRIYatQvD7upnFmMu2LCb1pHk oj1bCfaQteNyqAUHc90SZrU/gpEZceuwvh5Imd0ynRcPW4fvtdBZIdH4PmC5L0Hp +V9sBwkjLT0S1KwRUMQ44KqgNolk8MmSDFYtuqnZIX8mAdoqnZUETj/E+K+g3QdD yGsXOrqZCgj1pBChhUJD9CChgZkBpjL89j7ZiSfVWw5EL+ZEGqegnxf8eIrf0XWJ wj9BXRGq8TgZc+CQnbp+eGuTpqU6QE6SzCoo2MKC0652iM6Wzyn3I9p9TeJxzbIo h2V0ds7YtHkuK+6f6inWdBZU50/49Byqth8KLHVQfxFFuK3zT9YNXcPhkMoCFLc7 9AO0t3Uvvd78gKyegS5EWYOSwtUMpcPqX4++Ft6kvzlwZEV7FznT7YEIZKgP7YCN NYOWhwjunOQRm+hSoY+OA+REvPMxmYBQay1IqMPz9tACZL+u3U0= =FIxd -END PGP SIGNATURE--
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 means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 876890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scalapack Version: 2.0.2-3 Severity: serious Some recent change in unstable makes scalapack FTBFS on arm64: https://tests.reproducible-builds.org/debian/history/scalapack.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/scalapack.html ... The following tests FAILED: 1 - xCbtest (Failed) 2 - xFbtest (Failed) 75 - xssvd (Failed) 76 - xdsvd (Failed) 77 - xssep (Failed) 78 - xdsep (Failed) 79 - xcsep (Failed) 80 - xzsep (Failed) 81 - xsgsep (Failed) 82 - xdgsep (Failed) 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 --- End Message --- --- Begin Message --- On Thu, 28 Sep 2017 16:25:28 +0800 Drew Parsons wrote: > > A test build on the porterbox succeeded. The failure in your test must > have been a transitory openmpi problem. > > Please file scalapack for another test on arm64. Build succeeded, 2017-09-28 11:12 arm64_3/1299, so closing this bug. Drew --- End Message --- -- 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#876890: scalapack FTBFS on arm64: test failures
On Thu, 28 Sep 2017 15:28:11 +0800 Drew Parsons 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 transitory openmpi problem. Please file scalapack for another test on arm64. Drew -- 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#876890: scalapack FTBFS on arm64: test failures
On Tue, 26 Sep 2017 21:09:03 +0300 Adrian Bunk wrote: > Source: scalapack > Version: 2.0.2-3 > Severity: serious > > Some recent change in unstable makes scalapack FTBFS on arm64: > > https://tests.reproducible-builds.org/debian/history/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 test failures, which are common and therefore ignored. The actual FTBFS is from the openmpi test: OpenMPI tests failed: 20 - dpb2tim (Failed) -- 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#876890: scalapack FTBFS on arm64: test failures
Source: scalapack Version: 2.0.2-3 Severity: serious Some recent change in unstable makes scalapack FTBFS on arm64: https://tests.reproducible-builds.org/debian/history/scalapack.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/scalapack.html ... The following tests FAILED: 1 - xCbtest (Failed) 2 - xFbtest (Failed) 75 - xssvd (Failed) 76 - xdsvd (Failed) 77 - xssep (Failed) 78 - xdsep (Failed) 79 - xcsep (Failed) 80 - xzsep (Failed) 81 - xsgsep (Failed) 82 - xdgsep (Failed) 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-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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-0.8.0~r57502' echo "Fue un malentendido." | apertium -d . es-en | tee .test-mt It went a misunderstanding. 1c1 < It was a misunderstanding. --- > It went a misunderstanding. Makefile:784: recipe for target 'test' failed make[1]: *** [test] Error 1 -- 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#875671: marked as done (fix test dependencies)
Your message dated Wed, 13 Sep 2017 21:24:13 +
with message-id
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 problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
875671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: lapack
Source-Version: 3.7.1-4
We believe that the bug you reported is fixed in the latest version of
lapack, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sébastien Villemot (supplier of updated lapack package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 13 Sep 2017 22:50:38 +0200
Source: lapack
Binary: liblapack3 liblapacke liblapacke-dev libtmglib3 libtmglib-dev
liblapack-dev liblapack-pic liblapack-test liblapack-doc libblas3 libblas-dev
libblas-test liblapack-doc-man
Architecture: source
Version: 3.7.1-4
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team
Changed-By: Sébastien Villemot
Description:
libblas-dev - Basic Linear Algebra Subroutines 3, static library
libblas-test - Basic Linear Algebra Subroutines 3, testing programs
libblas3 - Basic Linear Algebra Reference implementations, shared library
liblapack-dev - Library of linear algebra routines 3 - static version
liblapack-doc - Library of linear algebra routines 3 - documentation
liblapack-doc-man - Transitional package for BLAS and LAPACK manpages
liblapack-pic - Library of linear algebra routines 3 - static PIC version
liblapack-test - Library of linear algebra routines 3 - testing programs
liblapack3 - Library of linear algebra routines 3 - shared version
liblapacke - Library of linear algebra routines 3 - C lib shared version
liblapacke-dev - Library of linear algebra routines 3 - Headers
libtmglib-dev - test matrix generators of LAPACK - development files
libtmglib3 - test matrix generators of LAPACK - shared version
Closes: 875671
Changes:
lapack (3.7.1-4) unstable; urgency=low
.
* Add gcc in the dependency list of {blas,lapack}-testsuite autopkgtests.
This is needed by dpkg-architecture.
Thanks to Matthias Klose (Closes: #875671)
Checksums-Sha1:
91943fb6f15b1de4d8ce26f351e08fea9008fac4 2809 lapack_3.7.1-4.dsc
0f3dfd9b757ceeaa94c8eadc9815471b5ed6641b 20824 lapack_3.7.1-4.debian.tar.xz
0c9f7090b6cca320ff539b4698155690acf0169e 12144 lapack_3.7.1-4_amd64.buildinfo
Checksums-Sha256:
e8eeb000df5c057f83ca6fd07866da73fdce453f84442765bcec50c441b7b67c 2809
lapack_3.7.1-4.dsc
e257f7b2699ef2f4ec4df7b1da77f2ca2a86866d6efdc5207bb7d023553480c6 20824
lapack_3.7.1-4.debian.tar.xz
556859178805b884072fa617f8bfbd074d273ecddaf69afe6b7b291377c45b9c 12144
lapack_3.7.1-4_amd64.buildinfo
Files:
6c8ab874279038db4e1334361c8460bd 2809 libs optional lapack_3.7.1-4.dsc
1cbc693c2a266ef9836f1200e697b80c 20824 libs optional
lapack_3.7.1-4.debian.tar.xz
34a13f52cc8a60291de20d72d9c7b139 12144 libs optional
lapack_3.7.1-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlm5nLAACgkQLOzpNQ7O
vkqqHw/+NyH8NdpujD/4w3UkTW5HRMXh7V4nkGqrKWDFrSGpS3GTgKACNL6DWcCF
4FWI9xkGjVtgo4cn2rZXl8ReBjHRmmaD8QEsdUvQ0JblewgMhZiFptJhNTMKVJ3D
Fa2e5EJTM9jm44A+Ogr3ANSHfwmJDx296xtI58x+QIN8/L5/txnuLUoMA+spbzqM
uO+Ppv61UHSt7vRCBdr2J0MfCvi8U+xha+L3vY4KyGlZe3noVyN9sSgJQuwWKImH
jVzh22jDDxBMOEji0Hg7HZEvRKz/VxMqbC25BLi94E9IXnlFycN1Om+04fwUQkKK
/M7TOEqNukKvo0TvkX7UuksyD1MiCvqSsL5zyhzO0crkD0zkS5EyA+Nwx529TT4J
bWqvEWaNRS3+wmFlztsj2P0b7Px6ecnBfmdxatb/0Da0ICrhExTJBzYUUXITOA3y
0Q8cpazMRXMdD8sQGbITCIleAazu3NrFx+0TEkDiksFaIKxaMY6O1aW0RcmefydN
DrHPfWMXtQhMCQKpE7Wo7cVmVabVO8U4TsIk3+2uM1Pqpmudg5QF95Ail/QCVfrq
suQBzwtqAYxmH8eXSSegaXshGp9fN57UOVIOE/14P2fDt8oS3zCEMxxWs64wqy7N
8mK2rRWqdWauyMfppzavOfYWYbZbeKo876iAAfd0Q/NTe6c4jPs=
=i2AG
-END PGP SIGNATURE End Message
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 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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 appropriate. > It's more that some of the file formats are not endian-neutral (e.g. > OpenFST). For the purpose of working with HFST locally and exchanging > the neutral files, it works fine. Should be pretty easy to fix that, except OpenFST developers refused: https://bugs.debian.org/707826 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part -- 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#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 binaries from the architectures > where the FTBFS happens by using `reportbug ftp.debian.org`. The binaries are not broken, though. It's one out of a hundred tests that fails. It's more that some of the file formats are not endian-neutral (e.g. OpenFST). For the purpose of working with HFST locally and exchanging the neutral files, it works fine. -- Tino Didriksen -- 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#873008: marked as done (hfst FTBFS on big endian: FAIL: test)
Your message dated Thu, 07 Sep 2017 05:04:38 + with message-id 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 that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 873008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hfst Version: 3.12.2~r3289-1 Severity: serious https://buildd.debian.org/status/package.php?p=hfst&suite=sid ... Making check in tools make[3]: Entering directory '/<>/tools' Making check in src make[4]: Entering directory '/<>/tools/src' Making check in hfst-proc make[5]: Entering directory '/<>/tools/src/hfst-proc' make[5]: Nothing to be done for 'check'. make[5]: Leaving directory '/<>/tools/src/hfst-proc' Making check in hfst-twolc make[5]: Entering directory '/<>/tools/src/hfst-twolc' Making check in src make[6]: Entering directory '/<>/tools/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 test12.txt_fst test13 test13.txt_fst test14 test14.txt_fst test15 test15.txt_fst test16 test16.txt_fst test17 test17.txt_fst test18 test18.txt_fst test19 test19.txt_fst test2 test2.txt_fst test20 test20.txt_fst test21 test21.txt_fst test22 test22.txt_fst test23 test23.txt_fst test24 test24.txt_fst test25 test25.txt_fst test26 test26.txt_fst test27 test27.txt_fst test28 test28.txt_fst test29 test29.txt_fst test3 test3.txt_fst test30 test30.txt_fst test31 test31.txt_fst test32 test32.txt_fst test33 test33.txt_fst test34 test34.txt_fst test35 test35.txt_fst test36 test36.txt_fst test37 test37.txt_fst test38 test38.txt_fst test39 test39.txt_fst test4 test4.txt_fst test40 test40.txt_fst test41 test41.txt_fst test42 test42.txt_fst test43 test43.txt_fst test44 test44.txt_fst test45 test45.txt_fst test46 test46.txt_fst test47 test47.txt_fst test48 test48.txt_fst test49 test49.txt_fst test5 test5.txt_fst tes t51 test51.txt_fst test52 test52.txt_fst test53 test53.txt_fst test54 test54.txt_fst test55 test55.txt_fst test56 test56.txt_fst test57 test57.txt_fst test58 test58.txt_fst test59 test59.txt_fst test6 test6.txt_fst test60 test60.txt_fst test61 test61.txt_fst test62 test62.txt_fst test7 test7.txt_fst test8 test8.txt_fst test9 test9.txt_fst make[7]: Entering directory '/<>/tools/src/hfst-twolc/test' make[7]: Nothing to be done for 'test1'. make[7]: Nothing to be done for 'test1.txt_fst'. make[7]: Nothing to be done for 'test10'. make[7]: Nothing to be done for 'test10.txt_fst'. make[7]: Nothing to be done for 'test11'. make[7]: Nothing to be done for 'test11.txt_fst'. make[7]: Nothing to be done for 'test12'. make[7]: Nothing to be done for 'test12.txt_fst'. make[7]: Nothing to be done for 'test13'. make[7]: Nothing to be done for 'test13.txt_fst'. make[7]: Nothing to be done for 'test14'. make[7]: Nothing to be done for 'test14.txt_fst'. make[7]: Nothing to be done for 'test15'. make[7]: Nothing to be done for 'test15.txt_fst'. make[7]: Nothing to be done for 'test16'. make[7]: Nothing to be done for 'test16.txt_fst'. make[7]: Nothing to be done for 'test17'. make[7]: Nothing to be done for 'test17.txt_fst'. make[7]: Nothing to be done for 'test18'. make[7]: Nothing to be done for 'test18.txt_fst'. make[7]: Nothing to be done for 'test19'. make[7]: Nothing to be done for 'test19.txt_fst'. make[7]: Nothing to be done for 'test2'. make[7]: Nothing to be done for 'test2.txt_fst'. make[7]: Nothing to be done for 'test20'. make[7]: Nothing to be done for 'test20.txt_fst'. make[7]: Nothing to be done for 'test21'. make[7]: Nothing to be done for 'test21.txt_fst'. make[7]: Nothing to be done for 'test22'. make[7]: Nothing to be done for 'test22.txt_fst'. make[7]: Nothing to be done for 'test23'. make[7]: Nothing to be done for 'test23.txt_fst'. make[7]: Nothing to be done for 'test24'. m
Bug#873008: hfst FTBFS on big endian: FAIL: test
On Thu, 24 Aug 2017 14:27:17 +0200 Tino Didriksen wrote: > I forgot to re-disable tests for hfst. 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 binaries from the architectures where the FTBFS happens by using `reportbug ftp.debian.org`. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part -- 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#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 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 as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 867987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: h5py Version: 2.7.0-1 Tags: upstream patch Forwarded: https://github.com/h5py/h5py/pull/904 User: debian-sp...@lists.debian.org Usertags: sparc64 X-Debbugs-Cc: debian-sp...@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; please include the patch in the Debian package. Regards, James --- End Message --- --- Begin Message --- Source: h5py Source-Version: 2.7.1-1 We believe that the bug you reported is fixed in the latest version of h5py, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 867...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ghislain Antony Vaillant (supplier of updated h5py package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 03 Sep 2017 18:17:55 +0200 Source: h5py Binary: python-h5py python-h5py-dbg python3-h5py python3-h5py-dbg python-h5py-doc Architecture: source Version: 2.7.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Ghislain Antony Vaillant Description: python-h5py - general-purpose Python interface to hdf5 (Python 2) python-h5py-dbg - debug extensions for h5py (Python 2) python-h5py-doc - documentation for h5py python3-h5py - general-purpose Python interface to hdf5 (Python 3) python3-h5py-dbg - debug extensions for h5py (Python 3) Closes: 867987 Changes: h5py (2.7.1-1) unstable; urgency=medium . * Switch from git-dpm to gbp * New upstream version 2.7.1 (Closes: #867987) * Update the patch queue - Drop patch numbering, rename 0001-Disable-usage-of-rpath.patch to No-rpath.patch - New patch No-intersphinx.patch, disable useless intersphinx mapping * Update copyright information and dates * Normalize the package descriptions * Build the docs using the upstream Makefile * Use DEB_BUILD_OPTIONS for the nodoc guards * Bump the standards version to 4.1.0 Checksums-Sha1: b2174575f0a9312d03b9424a9f5f961a5009a7ef 2702 h5py_2.7.1-1.dsc 6117361bbc01b5ffe3516e6b8ac0f83656726249 264225 h5py_2.7.1.orig.tar.gz fbefc13bb1909d305f736aff8b0b1505cfcc0ae8 7104 h5py_2.7.1-1.debian.tar.xz e09b1695da85edf959975c9024459cb5f754eb3b 7137 h5py_2.7.1-1_source.buildinfo Checksums-Sha256: 27eb81c73b8bd1b56c86bcbd59c3c45052e6870d4a21b57649d9a1f67641531e 2702 h5py_2.7.1-1.dsc 180a688311e826ff6ae6d3bda9b5c292b90b28787525ddfcb10a29d5ddcae2cc 264225 h5py_2.7.1.orig.tar.gz 7cc6f987068b4aafcd196377b4b5140517efad308aa02d97ac2d2cc580bccf7e 7104 h5py_2.7.1-1.debian.tar.xz 59791ed422b072a930daf990f76b0c7419db8c05c3f22414c5b9a5a848c2a359 7137 h5py_2.7.1-1_source.buildinfo Files: d0025882fcd21600b8057931154d7c5b 2702 python optional h5py_2.7.1-1.dsc da630aebe3ab9fa218ac405a218e95e0 264225 python optional h5py_2.7.1.orig.tar.gz 622c3f88e6b745699fd0b485d5009cad 7104 python optional h5py_2.7.1-1.debian.tar.xz 146bd42fd881ee9bd83bf3d825409520 7137 python optional h5py_2.7.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEj1g0K+q+HvQ3lVH7sZN3DBhqHH0FAlmt5voACgkQsZN3DBhq HH2G3Q/9ErPme51xzq8QUp6kZRUQBrWx84kikOrukRTPoE8iSIUI4551aDojYS0r RtF40D6NbOsIu2+WobW/SzFFF1wumOsdfk+qnxl744FEwLkZ1fQxWZTMGwgh9UEo RCGwL/7geXqLZlwOBD3pVHr1HaiAwjhtW3afnbzcuakF8PHc+vYPRlYeeiybkGI0 8ruiQ7uFkszp/pizZppWHhsgEpuqOHQFRMaE5I14I3pZjRPfvdcTSzUgtl+P6JNi lF9jRHO1e1q0798/XNW7uikJ5duA8NNKi0gaZiBemIud8QrrHHv5QSP5sSPluEod we30H7VM2/qcUxop4FqC++AUCoIqFbX9YJne9QaREmzuUPgqPngcTeN+C6u3bHBx 2n1Gw4EKzpOapTQTQFJ6GcVyaK2Qc+4M7FviOyoOIVCdaGCpWmwbGprCIHDJMy8y 8NqnmY+N9xdlRvXopVCv6RDrh5z2A6wIltWfnYniZOUyxLErq3Kb5ilBm9igEdNU
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 > > https://buildd.debian.org/status/package.php?p=hfst&suite=sid > -- 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#873008: hfst FTBFS on big endian: FAIL: test
Source: hfst Version: 3.12.2~r3289-1 Severity: serious https://buildd.debian.org/status/package.php?p=hfst&suite=sid ... Making check in tools make[3]: Entering directory '/<>/tools' Making check in src make[4]: Entering directory '/<>/tools/src' Making check in hfst-proc make[5]: Entering directory '/<>/tools/src/hfst-proc' make[5]: Nothing to be done for 'check'. make[5]: Leaving directory '/<>/tools/src/hfst-proc' Making check in hfst-twolc make[5]: Entering directory '/<>/tools/src/hfst-twolc' Making check in src make[6]: Entering directory '/<>/tools/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 test12.txt_fst test13 test13.txt_fst test14 test14.txt_fst test15 test15.txt_fst test16 test16.txt_fst test17 test17.txt_fst test18 test18.txt_fst test19 test19.txt_fst test2 test2.txt_fst test20 test20.txt_fst test21 test21.txt_fst test22 test22.txt_fst test23 test23.txt_fst test24 test24.txt_fst test25 test25.txt_fst test26 test26.txt_fst test27 test27.txt_fst test28 test28.txt_fst test29 test29.txt_fst test3 test3.txt_fst test30 test30.txt_fst test31 test31.txt_fst test32 test32.txt_fst test33 test33.txt_fst test34 test34.txt_fst test35 test35.txt_fst test36 test36.txt_fst test37 test37.txt_fst test38 test38.txt_fst test39 test39.txt_fst test4 test4.txt_fst test40 test40.txt_fst test41 test41.txt_fst test42 test42.txt_fst test43 test43.txt_fst test44 test44.txt_fst test45 test45.txt_fst test46 test46.txt_fst test47 test47.txt_fst test48 test48.txt_fst test49 test49.txt_fst test5 test5.txt_fst tes t51 test51.txt_fst test52 test52.txt_fst test53 test53.txt_fst test54 test54.txt_fst test55 test55.txt_fst test56 test56.txt_fst test57 test57.txt_fst test58 test58.txt_fst test59 test59.txt_fst test6 test6.txt_fst test60 test60.txt_fst test61 test61.txt_fst test62 test62.txt_fst test7 test7.txt_fst test8 test8.txt_fst test9 test9.txt_fst make[7]: Entering directory '/<>/tools/src/hfst-twolc/test' make[7]: Nothing to be done for 'test1'. make[7]: Nothing to be done for 'test1.txt_fst'. make[7]: Nothing to be done for 'test10'. make[7]: Nothing to be done for 'test10.txt_fst'. make[7]: Nothing to be done for 'test11'. make[7]: Nothing to be done for 'test11.txt_fst'. make[7]: Nothing to be done for 'test12'. make[7]: Nothing to be done for 'test12.txt_fst'. make[7]: Nothing to be done for 'test13'. make[7]: Nothing to be done for 'test13.txt_fst'. make[7]: Nothing to be done for 'test14'. make[7]: Nothing to be done for 'test14.txt_fst'. make[7]: Nothing to be done for 'test15'. make[7]: Nothing to be done for 'test15.txt_fst'. make[7]: Nothing to be done for 'test16'. make[7]: Nothing to be done for 'test16.txt_fst'. make[7]: Nothing to be done for 'test17'. make[7]: Nothing to be done for 'test17.txt_fst'. make[7]: Nothing to be done for 'test18'. make[7]: Nothing to be done for 'test18.txt_fst'. make[7]: Nothing to be done for 'test19'. make[7]: Nothing to be done for 'test19.txt_fst'. make[7]: Nothing to be done for 'test2'. make[7]: Nothing to be done for 'test2.txt_fst'. make[7]: Nothing to be done for 'test20'. make[7]: Nothing to be done for 'test20.txt_fst'. make[7]: Nothing to be done for 'test21'. make[7]: Nothing to be done for 'test21.txt_fst'. make[7]: Nothing to be done for 'test22'. make[7]: Nothing to be done for 'test22.txt_fst'. make[7]: Nothing to be done for 'test23'. make[7]: Nothing to be done for 'test23.txt_fst'. make[7]: Nothing to be done for 'test24'. make[7]: Nothing to be done for 'test24.txt_fst'. make[7]: Nothing to be done for 'test25'. make[7]: Nothing to be done for 'test25.txt_fst'. make[7]: Nothing to be done for 'test26'. make[7]: Nothing to be done for 'test26.txt_fst'. make[7]: Nothing to be done for 'test27'. make[7]: Nothing to be done for 'test27.txt_fst'. make[7]: Nothing to be done for 'test28'. make[7]: Nothing to be done for 'test28.txt_fst'. make[7]: Nothing to be done for 'test29'. make[7]: Nothing to be done for 'test29.txt_fst'. make[7]: Nothing to be done for 'test3'. make[7]: Nothing to be done for 'test3.txt_fst'. make[7]: Nothing to be done for 'test30'. make[7]: Nothing to be do
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 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 means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 856356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linbox Version: 1.4.2-3 Severity: important https://buildd.debian.org/status/package.php?p=linbox&suite=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/bash ../libtool --tag=CXX --mode=link g++ -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat -Werror=format-security ../linbox/liblinbox.la -Wl,-z,relro -Wl,-z,now -fopenmp -o test-toeplitz-det test-toeplitz-det.o -lntl -lmpfr -liml -fopenmp -lblas -llapack -lgivaro -lgmpxx -lgmp -Wl,-z,relro -Wl,-z,now -fopenmp libtool: link: g++ -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -fopenmp -o .libs/test-toeplitz-det test-toeplitz-det.o -fopenmp -Wl,-z -Wl,relro -Wl,-z -Wl,now -fopenmp ../linbox/.libs/liblinbox.so -lntl -lmpfr -liml -lblas -llapack -lgivaro -lgmpxx -lgmp -fopenmp PASS: test-toeplitz-det /bin/bash ../libtool --tag=CXX --mode=link g++ -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat -Werror=format-security ../linbox/liblinbox.la -Wl,-z,relro -Wl,-z,now -fopenmp -o test-solve test-solve.o -lntl -lmpfr -liml -fopenmp -lblas -llapack -lgivaro -lgmpxx -lgmp -Wl,-z,relro -Wl,-z,now -fopenmp libtool: link: g++ -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -fopenmp -o .libs/test-solve test-solve.o -fopenmp -Wl,-z -Wl,relro -Wl,-z -Wl,now -fopenmp ../linbox/.libs/liblinbox.so -lntl -lmpfr -liml -lblas -llapack -lgivaro -lgmpxx -lgmp -fopenmp PASS: test-solve /bin/bash ../libtool --tag=CXX --mode=link g++ -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat -Werror=format-security ../linbox/liblinbox.la -Wl,-z,relro -Wl,-z,now -fopenmp -o test-regression test-regression.o -lntl -lmpfr -liml -fopenmp -lblas -llapack -lgivaro -lgmpxx -lgmp -Wl,-z,relro -Wl,-z,now -fopenmp libtool: link: g++ -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -fopenmp -o .libs/test-regression test-regression.o -fopenmp -Wl,-z -Wl,relro -Wl,-z -Wl,now -fopenmp ../linbox/.libs/liblinbox.so -lntl -lmpfr -liml -lblas -llapack -lgivaro -lgmpxx -lgmp -fopenmp PASS: test-regression LinBox 1.4.2: tests/test-suite.log # TOTAL: 15 # PASS: 14 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-charpoly === FAIL test-charpoly (exit status: 139) Testsuite summary for LinBox 1.4.2 # TOTAL: 15 # PASS: 14 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ==== See tests/test-suite.log Please report to linbox-...@googlegroups.com Makefile:2260: recipe for target 'test-suite.log' failed make[5]: *** [test-suite.log] Error 1 --- End Message --- --- Begin Message --- Source: linbox Source-Version: 1.4.2-5 We believe that the bug you reported is fixed in the latest version of linbox, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 856...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated linbox package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.or
Bug#871927: marked as done (xtensor-python FTBFS: test failures)
Your message dated Tue, 15 Aug 2017 07:50:18 + with message-id and subject line Bug#871927: fixed in xtensor-python 0.12.4-1 has caused the Debian Bug report #871927, regarding xtensor-python FTBFS: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 871927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 to: vec(2, 1) Which is: 9 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:316: row_major access xtensor-python_0.12.2-1/test/test_common.hpp:332: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:327: column_major access xtensor-python_0.12.2-1/test/test_common.hpp:343: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:338: central_major access xtensor-python_0.12.2-1/test/test_common.hpp:354: Failure Expected: vec(2, 0, 0) Which is: 16 To be equal to: vec(2, 0) Which is: -1 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:349: unit_shape access [ FAILED ] pyarray.access (0 ms) [ RUN ] pyarray.indexed_access xtensor-python_0.12.2-1/test/test_common.hpp:390: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 9 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:385: row_major access xtensor-python_0.12.2-1/test/test_common.hpp:400: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:395: column_major access xtensor-python_0.12.2-1/test/test_common.hpp:410: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:405: central_major access xtensor-python_0.12.2-1/test/test_common.hpp:422: Failure Expected: vec(2, 0, 0) Which is: 16 To be equal to: vec[id1] Which is: -1 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:415: unit_shape access [ FAILED ] pyarray.indexed_access (0 ms) ... [ RUN ] pytensor.access xtensor-python_0.12.2-1/test/test_common.hpp:321: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 9 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:316: row_major access xtensor-python_0.12.2-1/test/test_common.hpp:332: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:327: column_major access xtensor-python_0.12.2-1/test/test_common.hpp:343: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:338: central_major access xtensor-python_0.12.2-1/test/test_common.hpp:354: Failure Expected: vec(2, 0, 0) Which is: 16 To be equal to: vec(2, 0) Which is: -1 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:349: unit_shape access [ FAILED ] pytensor.access (1 ms) [ RUN ] pytensor.indexed_access xtensor-python_0.12.2-1/test/test_common.hpp:390: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 9 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:385: row_major access xtensor-python_0.12.2-1/test/test_common.hpp:400: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:395: column_major access xtensor-python_0.12.2-1/test/test_common.hpp:410: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:405: central_major access xtensor-python_0.12.2-1/test/test_common.hpp:422: Failure Expected: vec(2, 0, 0) Which is: 16 To be equal to: vec[id1] Which is: -1 Google Test trace: xtensor-python_0.12.2-1/test
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
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 as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
862090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mathicgb
Version: 1.0~git20170104-1
Severity: important
Tags: sid + patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch
Hello,
Package 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
>
>
> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: unittest
> ==
> ...
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=mathicgb&arch=mips&ver=1.0~git20170104-1&stamp=1486639289&raw=0
On upstream this issue is resolved with proposed commit:
https://github.com/Macaulay2/mathicgb/pull/9/commits/d8ae074c7f7655c3b85c2089cd7a05a98a70a46a
I have attached the patch.
With this patch package builds successfully on mips and mipsel.
Regards,
Radovan--- mathicgb-1.0~git20170104.orig/src/mathicgb/MonoMonoid.hpp
+++ mathicgb-1.0~git20170104/src/mathicgb/MonoMonoid.hpp
@@ -582,13 +582,9 @@ public:
MATHICGB_ASSERT(i == varCount() / 2 || access(a, i*2+1) >= 0);
uint64 A, B, AB;
- // We have to use std::memcpy here because just casting to a int64 breaks
- // the strict aliasing rule which implies undefined behavior. Both MSVC and
- // gcc don't actually call memcpy here. MSVC is a tiny bit slower for this
- // code than for casting while GCC seems to be exactly the same speed.
- std::memcpy(&A, ptr(a, i*2), 8);
- std::memcpy(&B, ptr(b, i*2), 8);
- std::memcpy(&AB, ptr(ab, i*2), 8);
+ A = *ptr(a, i*2) | (((uint64)*ptr(a, i*2 + 1)) << 32);
+ B = *ptr(b, i*2) | (((uint64)*ptr(b, i*2 + 1)) << 32);
+ AB = *ptr(ab, i*2) | (((uint64)*ptr(ab, i*2 + 1)) << 32);
orOfXor |= AB ^ (A + B);
}
MATHICGB_ASSERT((orOfXor == 0) == isProductOf(a, b, ab));
@@ -608,11 +604,11 @@ public:
uint64 orOfXor = 0;
for (VarIndex i = varCount() / 2; i != beforeEntriesIndexBegin(); --i) {
uint64 A1, A2, B, A1B, A2B;
- std::memcpy(&A1, ptr(a1, i*2), 8);
- std::memcpy(&A2, ptr(a2, i*2), 8);
- std::memcpy(&B, ptr(b, i*2), 8);
- std::memcpy(&A1B, ptr(a1b, i*2), 8);
- std::memcpy(&A2B, ptr(a2b, i*2), 8);
+ A1 = *ptr(a1, i*2) | (((uint64)*ptr(a1, i*2 + 1)) << 32);
+ A2 = *ptr(a2, i*2) | (((uint64)*ptr(a2, i*2 + 1)) << 32);
+ B = *ptr(b, i*2) | (((uint64)*ptr(b, i*2 + 1)) << 32);
+ A1B = *ptr(a1b, i*2) | (((uint64)*ptr(a1b, i*2 + 1)) << 32);
+ A2B = *ptr(a2b, i*2) | (((uint64)*ptr(a2b, i*2 + 1)) << 32);
orOfXor |= (A1B ^ (A1 + B)) | (A2B ^ (A2 + B));
}
MATHICGB_ASSERT
--- End Message ---
--- Begin Message ---
Source: mathicgb
Source-Version: 1.0~git20170606-1
We believe that the bug you reported is fixed in the latest version of
mathicgb, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 862...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Doug Torrance (supplier of updated mathicgb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 12 Aug 2017 18:33:51 -0400
Source: mathicgb
Binary: mathicgb libmathicgb-dev libmathicgb0
Architecture: source
Version: 1.0~git20170606-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Doug
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 failing in Gridgraph Test Dimension 3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 871556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvigraimpex Version: 1.10.0+git20160211.167be93+dfsg-3 Severity: serious Justification: fails to build from source (but built successfully in the past) With the latest upload there are FTBFS problems on some archs. Running test_gridgraph cd /<>/libvigraimpex-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 Dimension 3 Failure in NeighborhoodTests::testIndirectNeighborhood() Assertion failed: neighborOffsets[k] == -neighborOffsets[neighborCount-1-k] [(-1, -1, -1) != (-1, 1, -1)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:183) Failure in (&GridGraphTests::template testNeighborIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: target(*e, g) == *n [(1, -1, 0) != (1, -1, 0)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:744) Failure in (&GridGraphTests::template testNeighborIterator)() Assertion failed: source(*e, g) == *j [(0, -2, 0) != (0, 0, 0)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:743) Failure in (&GridGraphTests::template testBackNeighborIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: target(*e, g) == *n [(0, -1, 0) != (0, -1, 0)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:940) Failure in (&GridGraphTests::template testBackNeighborIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: target(*e, g) == *n [(0, -1, 0) != (0, -1, 0)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:940) Failure in (&GridGraphTests::template testEdgeIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: !(e == lemon::INVALID) (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1062) Failure in (&GridGraphTests::template testEdgeIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: !(e == lemon::INVALID) (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1062) Failure in (&GridGraphTests::template testArcIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: !(e == lemon::INVALID) (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1143) Failure in (&GridGraphTests::template testArcIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: !(e == lemon::INVALID) (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1143) 9 of 38 tests failed in test suite Gridgraph Test Dimension 3 Leaving test suite Gridgraph Test Dimension 3 9 of 76 tests failed in test suite Gridgraph Test Leaving test suite Gridgraph Test test/gridgraph/CMakeFiles/test_gridgraph.dir/build.make:123: recipe for target 'test/gridgraph/test_gridgraph' failed make[5]: *** [test/gridgraph/test_gridgraph] Error 1 make[
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 to: vec(2, 1) Which is: 9 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:316: row_major access xtensor-python_0.12.2-1/test/test_common.hpp:332: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:327: column_major access xtensor-python_0.12.2-1/test/test_common.hpp:343: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:338: central_major access xtensor-python_0.12.2-1/test/test_common.hpp:354: Failure Expected: vec(2, 0, 0) Which is: 16 To be equal to: vec(2, 0) Which is: -1 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:349: unit_shape access [ FAILED ] pyarray.access (0 ms) [ RUN ] pyarray.indexed_access xtensor-python_0.12.2-1/test/test_common.hpp:390: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 9 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:385: row_major access xtensor-python_0.12.2-1/test/test_common.hpp:400: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:395: column_major access xtensor-python_0.12.2-1/test/test_common.hpp:410: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:405: central_major access xtensor-python_0.12.2-1/test/test_common.hpp:422: Failure Expected: vec(2, 0, 0) Which is: 16 To be equal to: vec[id1] Which is: -1 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:415: unit_shape access [ FAILED ] pyarray.indexed_access (0 ms) ... [ RUN ] pytensor.access xtensor-python_0.12.2-1/test/test_common.hpp:321: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 9 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:316: row_major access xtensor-python_0.12.2-1/test/test_common.hpp:332: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:327: column_major access xtensor-python_0.12.2-1/test/test_common.hpp:343: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec(2, 1) Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:338: central_major access xtensor-python_0.12.2-1/test/test_common.hpp:354: Failure Expected: vec(2, 0, 0) Which is: 16 To be equal to: vec(2, 0) Which is: -1 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:349: unit_shape access [ FAILED ] pytensor.access (1 ms) [ RUN ] pytensor.indexed_access xtensor-python_0.12.2-1/test/test_common.hpp:390: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 9 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:385: row_major access xtensor-python_0.12.2-1/test/test_common.hpp:400: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:395: column_major access xtensor-python_0.12.2-1/test/test_common.hpp:410: Failure Expected: vec(2, 1, 0) Which is: 20 To be equal to: vec[index1] Which is: 2 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:405: central_major access xtensor-python_0.12.2-1/test/test_common.hpp:422: Failure Expected: vec(2, 0, 0) Which is: 16 To be equal to: vec[id1] Which is: -1 Google Test trace: xtensor-python_0.12.2-1/test/test_common.hpp:415: unit_shape access [ FAILED ] pytensor.indexed_access (0 ms) ... [==] 32 tests from 3 test cases ran. (2 ms total) [ PASSED ] 28 tests. [ FAILED ] 4 tests, listed below: [ FAILED ] pyarray.access [ FAILED ] pyarray.indexed_access [ FAILED ] pytensor.access [ FAILED ] pytensor.indexed_access 4 FAILED TESTS test/CMakeFiles/xtest.dir/build.make:60: recipe for target 'test/CMakeFiles/xtest' failed make[5]: *** [test/CMakeFiles/xtest] Error 1 -- 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#871556: libvigraimpex: several tests failing in Gridgraph Test Dimension 3
Source: libvigraimpex Version: 1.10.0+git20160211.167be93+dfsg-3 Severity: serious Justification: fails to build from source (but built successfully in the past) With the latest upload there are FTBFS problems on some archs. Running test_gridgraph cd /<>/libvigraimpex-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 Dimension 3 Failure in NeighborhoodTests::testIndirectNeighborhood() Assertion failed: neighborOffsets[k] == -neighborOffsets[neighborCount-1-k] [(-1, -1, -1) != (-1, 1, -1)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:183) Failure in (&GridGraphTests::template testNeighborIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: target(*e, g) == *n [(1, -1, 0) != (1, -1, 0)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:744) Failure in (&GridGraphTests::template testNeighborIterator)() Assertion failed: source(*e, g) == *j [(0, -2, 0) != (0, 0, 0)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:743) Failure in (&GridGraphTests::template testBackNeighborIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: target(*e, g) == *n [(0, -1, 0) != (0, -1, 0)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:940) Failure in (&GridGraphTests::template testBackNeighborIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: target(*e, g) == *n [(0, -1, 0) != (0, -1, 0)] (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:940) Failure in (&GridGraphTests::template testEdgeIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: !(e == lemon::INVALID) (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1062) Failure in (&GridGraphTests::template testEdgeIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: !(e == lemon::INVALID) (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1062) Failure in (&GridGraphTests::template testArcIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: !(e == lemon::INVALID) (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1143) Failure in (&GridGraphTests::template testArcIterator)() Unexpected Contract exception: Precondition violation! Index out of bounds (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array.hxx:999) Last checkpoint: !(e == lemon::INVALID) (/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/gridgraph/test.cxx:1143) 9 of 38 tests failed in test suite Gridgraph Test Dimension 3 Leaving test suite Gridgraph Test Dimension 3 9 of 76 tests failed in test suite Gridgraph Test Leaving test suite Gridgraph Test test/gridgraph/CMakeFiles/test_gridgraph.dir/build.make:123: recipe for target 'test/gridgraph/test_gridgraph' failed make[5]: *** [test/gridgraph/test_gridgraph] Error 1 make[5]: *** Deleting file 'test/gridgraph/test_gridgraph' make[5]: Leaving directory '/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj' CMakeFiles/Makefile2:1895: recipe for target 'test/gridgraph/CMakeFiles/test_gridgraph.dir/all' failed DS -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- 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#871208: python-xarray: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.6 3.5" returned exit code 13
ng output... [ 79%] generated/xarray.ufuncs.arcsin > writing output... [ 79%] generated/xarray.ufuncs.arcsinh > writing output... [ 79%] generated/xarray.ufuncs.arctan > writing output... [ 80%] generated/xarray.ufuncs.arctan2 > writing output... [ 80%] generated/xarray.ufuncs.arctanh > writing output... [ 80%] generated/xarray.ufuncs.ceil > writing output... [ 81%] generated/xarray.ufuncs.conj > writing output... [ 81%] generated/xarray.ufuncs.copysign > writing output... [ 81%] generated/xarray.ufuncs.cos > writing output... [ 81%] generated/xarray.ufuncs.cosh > writing output... [ 82%] generated/xarray.ufuncs.deg2rad > writing output... [ 82%] generated/xarray.ufuncs.degrees > writing output... [ 82%] generated/xarray.ufuncs.exp > writing output... [ 83%] generated/xarray.ufuncs.expm1 > writing output... [ 83%] generated/xarray.ufuncs.fabs > writing output... [ 83%] generated/xarray.ufuncs.fix > writing output... [ 84%] generated/xarray.ufuncs.floor > writing output... [ 84%] generated/xarray.ufuncs.fmax > writing output... [ 84%] generated/xarray.ufuncs.fmin > writing output... [ 85%] generated/xarray.ufuncs.fmod > writing output... [ 85%] generated/xarray.ufuncs.frexp > writing output... [ 85%] generated/xarray.ufuncs.hypot > writing output... [ 86%] generated/xarray.ufuncs.imag > writing output... [ 86%] generated/xarray.ufuncs.iscomplex > writing output... [ 86%] generated/xarray.ufuncs.isfinite > writing output... [ 86%] generated/xarray.ufuncs.isinf > writing output... [ 87%] generated/xarray.ufuncs.isnan > writing output... [ 87%] generated/xarray.ufuncs.isreal > writing output... [ 87%] generated/xarray.ufuncs.ldexp > writing output... [ 88%] generated/xarray.ufuncs.log > writing output... [ 88%] generated/xarray.ufuncs.log10 > writing output... [ 88%] generated/xarray.ufuncs.log1p > writing output... [ 89%] generated/xarray.ufuncs.log2 > writing output... [ 89%] generated/xarray.ufuncs.logaddexp > writing output... [ 89%] generated/xarray.ufuncs.logaddexp2 > writing output... [ 90%] generated/xarray.ufuncs.logical_and > writing output... [ 90%] generated/xarray.ufuncs.logical_not > writing output... [ 90%] generated/xarray.ufuncs.logical_or > writing output... [ 90%] generated/xarray.ufuncs.logical_xor > writing output... [ 91%] generated/xarray.ufuncs.maximum > writing output... [ 91%] generated/xarray.ufuncs.minimum > writing output... [ 91%] generated/xarray.ufuncs.nextafter > writing output... [ 92%] generated/xarray.ufuncs.rad2deg > writing output... [ 92%] generated/xarray.ufuncs.radians > writing output... [ 92%] generated/xarray.ufuncs.real > writing output... [ 93%] generated/xarray.ufuncs.rint > writing output... [ 93%] generated/xarray.ufuncs.sign > writing output... [ 93%] generated/xarray.ufuncs.signbit > writing output... [ 94%] generated/xarray.ufuncs.sin > writing output... [ 94%] generated/xarray.ufuncs.sinh > writing output... [ 94%] generated/xarray.ufuncs.sqrt > writing output... [ 95%] generated/xarray.ufuncs.square > writing output... [ 95%] generated/xarray.ufuncs.tan > writing output... [ 95%] generated/xarray.ufuncs.tanh > writing output... [ 95%] generated/xarray.ufuncs.trunc > writing output... [ 96%] generated/xarray.zeros_like > writing output... [ 96%] groupby > writing output... [ 96%] index > writing output... [ 97%] indexing > writing output... [ 97%] installing > writing output... [ 97%] internals > writing output... [ 98%] io > writing output... [ 98%] pandas > writing output... [ 98%] plotting > writing output... [ 99%] reshaping > writing output... [ 99%] time-series > writing output... [ 99%] whats-new > writing output... [100%] why-xarray > > /<>/doc/whats-new.rst:1758: WARNING: unknown document: tutorial > generating indices... genindex > writing additional pages... search > copying images... [ 2%] _static/dataset-diagram.png > copying images... [ 4%] _build/html/_static/plotting_seaborn_palette.png > copying images... [ 7%] _static/dask_array.png > copying images... [ 9%] _build/html/_static/plotting_listed_levels.png > copying images... [ 12%] > examples/../_build/html/_static/xarray_multidimensional_coords_10_1.png > copying images... [ 14%] _build/html/_static/plotting_robust2.png > copying images... [ 17%] _build/html/_static/2d_simple.png > copying images... [ 19%] > examples/../_build/html/_static/examples_tmin_tmax_plot_mean.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/plotting_example_sin3.png > copying images... [ 31%] _build/html/_static/plot_facet_iterator.png > copying images
Bug#598571: libatlas3gf-base: Build of atlas test programm xsl2blastst_pt and xsl1blastst_pt failed
Dear Ferran, A long time ago, you reported the following bug report against the Debian package for ATLAS: On Thu, 30 Sep 2010 10:11:21 +0200 Ferran Obón Santacana wrote: > Package: libatlas3gf-base > Version: 3.8.3-27+custom1 > Severity: normal > > 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/atlas-base/include > -I/usr/src/atlas-3.8.3/build/atlas-base/../..//include > -I/usr/src/atlas-3.8.3/bu$ > /usr/src/atlas-3.8.3/build/atlas-base/../..//bin/l2blastst.c:149:29: error: > atlas_ptlvl2.h: No such file or directory > make: *** [sl2blastst_pt.o] Error 1 > > I can however compile other test programs (the non threaded ones) and also > "xsl3blastst_pt". Consider me at hand for any future "work" you may need from > me. I tried to replicate your problem with a recent version of the ATLAS package, and the program that you mentioned compiled fine. Is this still an issue for you? Or can I close this bug report? Best, -- ⢀⣴⠾⠻⢶⣦ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org -- 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#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 and rdeps to be removed from mips and powerpc for now (#869688). I'm downgrading the bug as the removal will make this non-RC. Ansgar -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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.org with problems -- 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#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 - test-core_type_mat3x4 (Failed) 18 - test-core_type_mat4x4 (Failed) Errors while running CTest Makefile:98: recipe for target 'test' failed make[2]: *** [test] Error 8 make[2]: Leaving directory '/build/glm-0.9.8.4/obj-x86_64-linux-gnu' debian/rules:22: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/build/glm-0.9.8.4' debian/rules:7: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler -- 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#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&arch=mips&ver=2.5.1-1&stamp=1500401835&raw=0 ... Start 31: test-ug 31/60 Test #31: test-ug ...***Timeout 300.02 sec Testing UGGrid<2> and UGGrid<3> with red/green refinement DimX=1, DimY=1, DimZ=1 DimX=1, DimY=1, DimZ=1 WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 1 are not being tested! Lifetime / consistency check for entities, codim 0 WARNING! Requested check of first 32 entities, but grid view only contains 11 entities SKIPPING lifetime / consistency check for missing entities, codim 1 Lifetime / consistency check for entities, codim 2 WARNING! Requested check of first 32 entities, but grid view only contains 16 entities Intersection Lifetime / consistency check WARNING! Requested check of intersections for first 32 elements, but grid view only contains 11 elements Lifetime / consistency check for entities, codim 0 WARNING! Requested check of first 32 entities, but grid view only contains 11 entities SKIPPING lifetime / consistency check for missing entities, codim 1 Lifetime / consistency check for entities, codim 2 WARNING! Requested check of first 32 entities, but grid view only contains 16 entities Intersection Lifetime / consistency check WARNING! Requested check of intersections for first 32 elements, but grid view only contains 11 elements WARNING: Entities for codim 2 are not being tested! WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 2 are not being tested! WARNING: Entities for codim 1 are not being tested! Lifetime / consistency check for entities, codim 0 SKIPPING lifetime / consistency check for missing entities, codim 1 SKIPPING lifetime / consistency check for missing entities, codim 2 Lifetime / consistency check for entities, codim 3 Intersection Lifetime / consistency check Lifetime / consistency check for entities, codim 0 SKIPPING lifetime / consistency check for missing entities, codim 1 SKIPPING lifetime / consistency check for missing entities, codim 2 Lifetime / consistency check for entities, codim 3 Intersection Lifetime / consistency check WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 1 are not being tested! Lifetime / consistency check for entities, codim 0 WARNING! Requested check of first 32 entities, but grid view only contains 18 entities SKIPPING lifetime / consistency check for missing entities, codim 1 Lifetime / consistency check for entities, codim 2 WARNING! Requested check of first 32 entities, but grid view only contains 21 entities Intersection Lifetime / consistency check WARNING! Requested check of intersections for first 32 elements, but grid view only contains 18 elements Lifetime / consistency check for entities, codim 0 WARNING! Requested check of first 32 entities, but grid view only contains 18 entities SKIPPING lifetime / consistency check for missing entities, codim 1 Lifetime / consistency check for entities, codim 2 WARNING! Requested check of first 32 entities, but grid view only contains 21 entities Intersection Lifetime / consistency check WARNING! Requested check of intersections for first 32 elements, but grid view only contains 18 elements WARNING: Entities for codim 2 are not being tested! WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 2 are not being tested! WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 2 are not being tested! WARNING: Entities for codim 1 are not being tested! Lifetime / consistency check for entities, codim 0 SKIPPING lifetime / consistency check for missing entities, codim 1 SKIPPING lifetime / consistency check for missing entities, codim 2 Lifetime / consistency check for entities, codim 3 Intersection Lifetime / consistency check Lifetime / consistency check for entities, codim 0 SKIPPING lifetime / consistency check for missing entities, codim 1 SKIPPING lifetime / consistency check for missing entities, codim 2 Lifetime / consistency check for entities, codim 3 Intersection Lifetime / consistency check WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 1 are not being tested! WARNING: Entities for codim 1 are not being tested! Lifetime / consistency check for entities, codim 0 SKIPPING lifetime / consistency check for missing entities, codim 1 Lifetime / consistency check for entities, codim 2 Intersection Lifetime / consistency check Lifetime / consistency check for entities, codim 0 SKIPPING lifetime / consistency check for missing entities, codim 1 Lifetime / consistency check for entities, codim 2 Intersection Lifetime / consistency check WARNING: Entities for codim 2 are not being tested! WARNING: Entities for
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 disable them is long: ``` -DAmesos2_ENABLE_TESTS:BOOL=OFF \ -DAnasazi_ENABLE_TESTS:BOOL=OFF \ -DBelos_ENABLE_TESTS:BOOL=OFF \ -DDomi_ENABLE_TESTS:BOOL=OFF \ -DEpetra_ENABLE_TESTS:BOOL=OFF \ -DIfpack_ENABLE_TESTS:BOOL=OFF \ -DIsorropia_ENABLE_TESTS:BOOL=OFF \ -DMueLu_ENABLE_TESTS:BOOL=OFF \ -DNOX_ENABLE_TESTS:BOOL=OFF \ -DPhalanx_ENABLE_TESTS:BOOL=OFF \ -DPiro_ENABLE_TESTS:BOOL=OFF \ -DShyLU_ENABLE_TESTS:BOOL=OFF \ -DShyLUCore_ENABLE_TESTS:BOOL=OFF \ -DStratimikos_ENABLE_TESTS:BOOL=OFF \ -DTeko_ENABLE_TESTS:BOOL=OFF \ -DTeuchos_ENABLE_TESTS:BOOL=OFF \ -DTeuchosComm_ENABLE_TESTS:BOOL=OFF \ -DTeuchosCore_ENABLE_TESTS:BOOL=OFF \ -DXpetra_ENABLE_TESTS:BOOL=OFF \ -DZoltan_ENABLE_TESTS:BOOL=OFF \ -DZoltan2_ENABLE_TESTS:BOOL=OFF \ ``` Not all of those disables are associated with upstream bugs, unfortunately, but then again it's probably a Sisyphean task to do so. As usual for those bugs, either they are fixed immediately or never. Cheers, Nico [1] https://github.com/trilinos/Trilinos/issues/1332 On Mon, Jul 24, 2017 at 10:53 AM Graham Inggs wrote: > 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 that it affects trilinos. > -- 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 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 that it affects trilinos. -- 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
> Still comes out corrupted in the gnome Archive Manager, but extracts fine on the command line. Sounds more like a gAM bug then. Can this be closed? Cheers, Nico On Mon, Jul 17, 2017 at 4:33 AM Drew Parsons wrote: > On Mon, 17 Jul 2017 10:21:03 +0800 Drew Parsons > 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 traffic. > > > Adding my build log again, the first attachment appears corrupted. > > Still comes out corrupted in the gnome Archive Manager, but extracts > fine on the command line. > > -- 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#868965: seaborn: FTBFS: Test failures
Source: seaborn
Version: 0.7.1-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mod = load_module(part_fqname, fh, filename, desc)
> File
> "/<>/.pybuild/pythonX.Y_2.7/build/seaborn/tests/test_utils.py",
> line 349, in
> @network(url="https://github.com/mwaskom/seaborn-data";)
> File "/usr/lib/python2.7/dist-packages/pandas/util/testing.py", line 2194,
> in dec
> return decorator(f, *args, **kwargs)
> File "/usr/lib/python2.7/dist-packages/pandas/util/testing.py", line 2363,
> in network
> from pytest import skip
> ImportError: No module named pytest
>
> --
> 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 python{version} -p 2.7 returned exit code 13
> debian/rules:28: recipe for target 'override_dh_auto_test' failed
The full build log is available from:
http://aws-logs.debian.net/2017/07/19/seaborn_0.7.1-4_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
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 Mon, 17 Jul 2017 10:21:03 +0800 Drew Parsons 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 traffic. > Adding my build log again, the first attachment appears corrupted. Still comes out corrupted in the gnome Archive Manager, but extracts fine on the command line. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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 assistance. -- 868523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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
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 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 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
I've disabled the phalanx tests in master, and also fixed two other things. Perhaps it's time for an upload? Cheers, Nico On Sun, Jul 16, 2017 at 2:16 PM Nico Schlömer wrote: > 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 wrote: > >> On 16 July 2017 at 13:12, Drew Parsons wrote: >> > Testing trilinos build on a porterbox for the mumps 5.1.1 transition. >> > >> > The following tests FAILED: >> > 617 - ML_MLP_NonSym_MPI_4 (Failed) >> > 668 - Phalanx_dag_manager_MPI_1 (Failed) >> > >> > Not 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 - Phalanx_dag_manager_MPI_1 (Failed) >> >> -- 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
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 wrote: > On 16 July 2017 at 13:12, Drew Parsons wrote: > > Testing trilinos build on a porterbox for the mumps 5.1.1 transition. > > > > The following tests FAILED: > > 617 - ML_MLP_NonSym_MPI_4 (Failed) > > 668 - Phalanx_dag_manager_MPI_1 (Failed) > > > > Not 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 - Phalanx_dag_manager_MPI_1 (Failed) > > -- 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 13:12, Drew Parsons wrote: > Testing trilinos build on a porterbox for the mumps 5.1.1 transition. > > The following tests FAILED: > 617 - ML_MLP_NonSym_MPI_4 (Failed) > 668 - Phalanx_dag_manager_MPI_1 (Failed) > > Not 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 - Phalanx_dag_manager_MPI_1 (Failed) -- 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#867987: h5py: FTBFS on sparc64 due to unaliged accesses in test suite
On Mon, 10 Jul 2017 22:18:53 +0100 James Clarke wrote: > Source: h5py > Version: 2.7.0-1 > Tags: upstream patch > Forwarded: https://github.com/h5py/h5py/pull/904 > User: debian-sp...@lists.debian.org > Usertags: sparc64 > X-Debbugs-Cc: debian-sp...@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; please include the patch in the Debian package. > > Regards, > James It looks like upstream is planning to make a new release soon, so I'll probably wait for it. Thanks for working on this, James. Cheers, Ghis -- 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#867987: h5py: FTBFS on sparc64 due to unaliged accesses in test suite
Source: h5py Version: 2.7.0-1 Tags: upstream patch Forwarded: https://github.com/h5py/h5py/pull/904 User: debian-sp...@lists.debian.org Usertags: sparc64 X-Debbugs-Cc: debian-sp...@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; please include the patch in the Debian package. Regards, James -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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 same values previously set > reassign 864186 libssl1.1 Bug #864186 [src:xtensor-python] xtensor-python FTBFS: [ FATAL ] gtest-port.h:2044:: pthread_key_delete(key_)failed with error 22 Bug reassigned from package 'src:xtensor-python' to 'libssl1.1'. No longer marked as found in versions xtensor-python/0.12.1-1. Ignoring request to alter fixed versions of bug #864186 to the same values previously set > forcemerge -1 864177 864186 Bug #863707 [libssl1.1] simple-tpm-pk11: FTBFS: ./m4/test-driver: line 107: 4695 Aborted (core dumped) Bug #864177 [libssl1.1] nordugrid-arc: FTBFS: test failure Added indication that 864177 affects src:simple-tpm-pk11 Marked as found in versions openssl/1.1.0f-1. Bug #864186 [libssl1.1] xtensor-python FTBFS: [ FATAL ] gtest-port.h:2044:: pthread_key_delete(key_)failed with error 22 Added indication that 864186 affects src:simple-tpm-pk11 Marked as found in versions openssl/1.1.0f-1. Merged 863707 864177 864186 > affects -1 src:nordugrid-arc src:xtensor-python Bug #863707 [libssl1.1] simple-tpm-pk11: FTBFS: ./m4/test-driver: line 107: 4695 Aborted (core dumped) Bug #864177 [libssl1.1] nordugrid-arc: FTBFS: test failure Bug #864186 [libssl1.1] xtensor-python FTBFS: [ FATAL ] gtest-port.h:2044:: pthread_key_delete(key_)failed with error 22 Added indication that 863707 affects src:nordugrid-arc and src:xtensor-python Added indication that 864177 affects src:nordugrid-arc and src:xtensor-python Added indication that 864186 affects src:nordugrid-arc and src:xtensor-python -- 863707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863707 864177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864177 864186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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-bin/bugreport.cgi?bug=862090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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#862090: mathicgb FTBFS on big endian architectures: test fails
Control: forwarded -1 https://github.com/Macaulay2/mathicgb/issues/3 On 05/08/2017 07:15 AM, Radovan Birdic wrote: Package: mathicgb Version: 1.0~git20170104-1 Severity: important Tags: sid + patch Justification: FTBFS User: debian-m...@lists.debian.org Usertags: mips-patch Hello, Package 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 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: unittest == ... Full build log: https://buildd.debian.org/status/fetch.php?pkg=mathicgb&arch=mips&ver=1.0~git20170104-1&stamp=1486639289&raw=0 On upstream this issue is resolved with proposed commit: https://github.com/Macaulay2/mathicgb/pull/9/commits/d8ae074c7f7655c3b85c2089cd7a05a98a70a46a I have attached the patch. With this patch package builds successfully on mips and mipsel. Thanks for your report! I've been aware of this for a while (I submitted the issue upstream back in 2015), but I suppose it's good to have it in the Debian BTS as well -- thanks! Upstream rejected the proposed patch as-is [1], which is why I've avoided applying it to the Debian package. However, I noticed that it has been applied to the Fedora package [2]. Perhaps I'll follow their lead and apply it to the Debian package as well for the time being. However, I'll wait until after the Stretch freeze. Doug [1] https://github.com/Macaulay2/mathicgb/pull/9#issuecomment-281349279 [2] http://pkgs.fedoraproject.org/cgit/rpms/mathicgb.git/commit/?id=0377aa73d04051c7b7c24c7ce28a054c31e66f52 -- 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#862090: mathicgb FTBFS on big endian architectures: test fails
Package: mathicgb
Version: 1.0~git20170104-1
Severity: important
Tags: sid + patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch
Hello,
Package 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
>
>
> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: unittest
> ==
> ...
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=mathicgb&arch=mips&ver=1.0~git20170104-1&stamp=1486639289&raw=0
On upstream this issue is resolved with proposed commit:
https://github.com/Macaulay2/mathicgb/pull/9/commits/d8ae074c7f7655c3b85c2089cd7a05a98a70a46a
I have attached the patch.
With this patch package builds successfully on mips and mipsel.
Regards,
Radovan--- mathicgb-1.0~git20170104.orig/src/mathicgb/MonoMonoid.hpp
+++ mathicgb-1.0~git20170104/src/mathicgb/MonoMonoid.hpp
@@ -582,13 +582,9 @@ public:
MATHICGB_ASSERT(i == varCount() / 2 || access(a, i*2+1) >= 0);
uint64 A, B, AB;
- // We have to use std::memcpy here because just casting to a int64 breaks
- // the strict aliasing rule which implies undefined behavior. Both MSVC and
- // gcc don't actually call memcpy here. MSVC is a tiny bit slower for this
- // code than for casting while GCC seems to be exactly the same speed.
- std::memcpy(&A, ptr(a, i*2), 8);
- std::memcpy(&B, ptr(b, i*2), 8);
- std::memcpy(&AB, ptr(ab, i*2), 8);
+ A = *ptr(a, i*2) | (((uint64)*ptr(a, i*2 + 1)) << 32);
+ B = *ptr(b, i*2) | (((uint64)*ptr(b, i*2 + 1)) << 32);
+ AB = *ptr(ab, i*2) | (((uint64)*ptr(ab, i*2 + 1)) << 32);
orOfXor |= AB ^ (A + B);
}
MATHICGB_ASSERT((orOfXor == 0) == isProductOf(a, b, ab));
@@ -608,11 +604,11 @@ public:
uint64 orOfXor = 0;
for (VarIndex i = varCount() / 2; i != beforeEntriesIndexBegin(); --i) {
uint64 A1, A2, B, A1B, A2B;
- std::memcpy(&A1, ptr(a1, i*2), 8);
- std::memcpy(&A2, ptr(a2, i*2), 8);
- std::memcpy(&B, ptr(b, i*2), 8);
- std::memcpy(&A1B, ptr(a1b, i*2), 8);
- std::memcpy(&A2B, ptr(a2b, i*2), 8);
+ A1 = *ptr(a1, i*2) | (((uint64)*ptr(a1, i*2 + 1)) << 32);
+ A2 = *ptr(a2, i*2) | (((uint64)*ptr(a2, i*2 + 1)) << 32);
+ B = *ptr(b, i*2) | (((uint64)*ptr(b, i*2 + 1)) << 32);
+ A1B = *ptr(a1b, i*2) | (((uint64)*ptr(a1b, i*2 + 1)) << 32);
+ A2B = *ptr(a2b, i*2) | (((uint64)*ptr(a2b, i*2 + 1)) << 32);
orOfXor |= (A1B ^ (A1 + B)) | (A2B ^ (A2 + B));
}
MATHICGB_ASSERT
--
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#860641: marked as done (dune-localfunctions: FTBFS on i386: Test failures)
Your message dated Thu, 20 Apr 2017 18:07:47 + with message-id 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 as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 860641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 package failed to build on i386. Relevant part (hopefully): >Testing p in dimension 4 with order 3 >Testing p in dimension 4 with order 4 >Testing p in dimension 4 with order 5 > >Testing p in dimension 4 with order 0 >Testing p in dimension 4 with order 1 >Testing p in dimension 4 with order 2 >Testing p in dimension 4 with order 3 >Testing p in dimension 4 with order 4 >Testing p in dimension 4 with order 5 >i = 115, j = 124: 1.0989e-09 >i = 124, j = 115: 1.0989e-09 > FAILED ! > > > /usr/share/dune/dune-debian.mk:16: recipe for target 'override_dh_auto_test' > failed The full build log is available from: http://aws-logs.debian.net/2017/04/18/dune-localfunctions_2.5.0-1_testing-i386.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: dune-localfunctions Source-Version: 2.5.0-2 We believe that the bug you reported is fixed in the latest version of dune-localfunctions, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 860...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt (supplier of updated dune-localfunctions package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 20 Apr 2017 19:32:17 +0200 Source: dune-localfunctions Binary: libdune-localfunctions-dev libdune-localfunctions-doc Architecture: source Version: 2.5.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Ansgar Burchardt Description: libdune-localfunctions-dev - toolbox for solving PDEs -- local basis (development files) libdune-localfunctions-doc - toolbox for solving PDEs -- local basis (documentation) Closes: 860641 Changes: dune-localfunctions (2.5.0-2) unstable; urgency=medium . * Increase ε used for comparisons. (Closes: #860641) + patch: 0001-Merge-branch-bugfix-increase-epsilon-for-i386-into-m.patch Checksums-Sha1: 95c0c1677fde124999e4869372480d8002cc32fb 2776 dune-localfunctions_2.5.0-2.dsc d7cc6030605e58170734a0529cdbf0158495e03a 3820 dune-localfunctions_2.5.0-2.debian.tar.xz 434258fe4f3b13d807406930da1261066e3c99c2 7097 dune-localfunctions_2.5.0-2_source.buildinfo Checksums-Sha256: 8ce29cfd91c61a48a11f491311446ed1d30ad66714c94fb3d171bc955de0466e 2776 dune-localfunctions_2.5.0-2.dsc 29a9f4692575b3b1130572459270d78ab59a257fa58f27f281a51b54ca1b03a9 3820 dune-localfunctions_2.5.0-2.debian.tar.xz cf968cef3d94635f5c65a61f1c66ccd58cc1484b29a6f0dfdfa88621500f8e57 7097 dune-localfunctions_2.5.0-2_source.buildinfo Files: b051aaa7d1f02acd8da30d5050298fe8 2776 libs optional dune-localfunctions_2.5.0-2.dsc 7bf3cf5945209a37fc5ad5332722d729 3820 libs optional dune-localfunctions_2.5.0-2.debian.tar.xz 94eb862de4a33479c4b4b1e0df08ffa9 7097 libs optional dune-localfunctions_2.5.0-2_source.buildinfo -BEGIN PGP SIGNATURE-
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 package failed to build on i386. Relevant part (hopefully): >Testing p in dimension 4 with order 3 >Testing p in dimension 4 with order 4 >Testing p in dimension 4 with order 5 > >Testing p in dimension 4 with order 0 >Testing p in dimension 4 with order 1 >Testing p in dimension 4 with order 2 >Testing p in dimension 4 with order 3 >Testing p in dimension 4 with order 4 >Testing p in dimension 4 with order 5 >i = 115, j = 124: 1.0989e-09 >i = 124, j = 115: 1.0989e-09 > FAILED ! > > > /usr/share/dune/dune-debian.mk:16: recipe for target 'override_dh_auto_test' > failed The full build log is available from: http://aws-logs.debian.net/2017/04/18/dune-localfunctions_2.5.0-1_testing-i386.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- 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#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 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 as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 827199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hfst Version: 3.10.0~r2798-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Thanks for taking care of the twolc errors I reported in #826659. The twolc test now succeeds on little-endian systems, and no longer hangs anywhere, but still fails on big-endian architectures (mips, powerpc, s390x, and several non-release architectures). I don't have further details, but perhaps you can reproduce the problem on a porterbox. Could you please take a look? Thanks! --- End Message --- --- Begin Message --- Source: hfst Source-Version: 3.10.0~r2798-3 We believe that the bug you reported is fixed in the latest version of hfst, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 827...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated hfst package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Mar 2017 18:48:47 +0530 Source: hfst Binary: hfst libhfst45 libhfst45-dev python-libhfst python3-libhfst Architecture: source amd64 Version: 3.10.0~r2798-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Kartik Mistry Description: hfst - Helsinki Finite-State Transducer Technology libhfst45 - Helsinki Finite-State Transducer Technology Libraries libhfst45-dev - Helsinki Finite-State Transducer Technology Development files python-libhfst - Helsinki Finite-State Transducer Technology (Python2 module) python3-libhfst - Helsinki Finite-State Transducer Technology (Python3 module) Closes: 827199 Changes: hfst (3.10.0~r2798-3) unstable; urgency=medium . [ Tino Didriksen ] * Workaround tests failing on big-endian (Closes: #827199) + Not solved, but not needed because hfst-ospell fixed the end-user case Checksums-Sha1: cdfffe695c56527d7dfff0a55a2cb754b0d1de01 2445 hfst_3.10.0~r2798-3.dsc aeb7908d51963660d9973bd7e76840404949f0a1 7372 hfst_3.10.0~r2798-3.debian.tar.xz c0201679f9911d87f75a030a79e660e169251e6b 47671968 hfst-dbgsym_3.10.0~r2798-3_amd64.deb da7c0f2d791552a429c061681cb3cf0c67e8d361 8640 hfst_3.10.0~r2798-3_amd64.buildinfo da4f39fc865fcd38e072f0991cbe549809c0299d 1154122 hfst_3.10.0~r2798-3_amd64.deb 959fb2735f3f0a87bcb9d7701a080f4c134bf6f7 22304226 libhfst45-dbgsym_3.10.0~r2798-3_amd64.deb e42dfb6bad45e7dcda83e93ca719af2e9964d550 185244 libhfst45-dev_3.10.0~r2798-3_amd64.deb d12fbc7c4f8771605236391f5c998779d576e2ef 1535824 libhfst45_3.10.0~r2798-3_amd64.deb 345ba78098b19cdac33e071b7e133c0141681d57 91778 python-libhfst_3.10.0~r2798-3_amd64.deb 1cb1c2b29369df5be5f1c87e9a57de5eab9be0c6 451308 python3-libhfst_3.10.0~r2798-3_amd64.deb Checksums-Sha256: d7b516b8acea229e34c20ef65090bf6b1e9414afc6aadfff4501f538d18b793a 2445 hfst_3.10.0~r2798-3.dsc 9f27e96ad644950036005a7318282a4aecc4fcc77a2f704aa65bd9dd7acff994 7372 hfst_3.10.0~r2798-3.debian.tar.xz 68a6ac4fa9fc3756b4d87ad5b04766821673947b84c337cc86d0e03d5ae11da1 47671968 hfst-dbgsym_3.10.0~r2798-3_amd64.deb ea2ad24df6f42b8926a511eabb530293efef750241ceebf9aa4548d69cb32480 8640 hfst_3.10.0~r2798-3_amd64.buildinfo 03247bee24a9f970095c203a9c763628c03b60b2768c286e733746be8106c106 1154122 hfst_3.10.0~r2798-3_amd64.deb 0be8e5fcdb04c097e6be9c7abdea16edf160a1b2d50f59bec5d98f6e26af773d 22304226 libhfst45-dbgsym_3.10.0~r2798-3_amd64.deb 03e3d8f592abb0600a9c9366575179c75915bf59c0b4b5c5f2152358eb35fc45 185244 libhfst45-dev_3.10.0~r2798-3_amd64.deb 9ae5247379f577d681aa769515295139a197b4cace6c909522a1a8eb7ee8 1535824 libhfst45_3.10.0~r2798-3_amd64.deb 97077986df2c074dbabb3be51fb1f8144f10331e03aa1ae73faf9910def01dac 91778 python-libhfst_3.10.0~r2798-3_amd6
Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems
On Thu, Mar 23, 2017 at 5:29 PM, Tino Didriksen wrote:
> On 23 March 2017 at 12:28, Mattia Rizzolo wrote:
>>
>> > Yes, it will be fixed this month. We've got a strategy that'll work for
>> > the
>> > primary 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 completely forgot there was a dependency bug. I've committed a
> simple test disabler, because we don't need HFST to pass those tests any
> longer.
>
> The actual issue was fixed in https://bugs.debian.org/824119 - since
> hfst-ospell no longer depends on HFST, HFST doesn't need to run tests.
>
> Kartik, can you push it onwards?
If I understand correctly, I need to push hfst-ospell, right?
--
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com
--
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#827199: hfst: FTBFS: twolc test fails on big-endian systems
On 23 March 2017 at 12:28, Mattia Rizzolo wrote: > > Yes, it will be fixed this month. We've got a strategy that'll work for > the > > primary 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 completely forgot there was a dependency bug. I've committed a simple test disabler, because we don't need HFST to pass those tests any longer. The actual issue was fixed in https://bugs.debian.org/824119 - since hfst-ospell no longer depends on HFST, HFST doesn't need to run tests. Kartik, can you push it onwards? -- Tino Didriksen -- 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#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 wrote: > > > > > While it did successfully build in the past, that was only because the > > test > > > > suite was disabled until recently. The tests revealed the unsigned char > > > > issue which was easy to fix, and now the endian issue which will not > > be as > > > > easy. > > > > Any news? > > > Yes, it will be fixed this month. We've got a strategy that'll work for the > primary 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. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature -- 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#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 this test) does not work properly. Disabling test should be done before autoreconf stage. The test has been disabled for both mips and mipsel. I have created and attached a patch which disables this test. With this patch package builds successfully, without test-charpoly execution. Regards, Radovan--- linbox-1.4.2_orig/debian/rules 2016-11-29 22:32:45.0 + +++ linbox-1.4.2/debian/rules 2017-03-07 13:56:57.0 + @@ -15,10 +15,10 @@ DEB_HOST_ARCH_CPU ?= $(shell dpkg-archit # Disable failing test test-charpoly on mipsel. # See https://github.com/linbox-team/linbox/issues/37 -ifeq ($(DEB_HOST_ARCH_CPU), $(filter $(DEB_HOST_ARCH_CPU), mipsel)) -build: +ifeq ($(DEB_HOST_ARCH_CPU), $(filter $(DEB_HOST_ARCH_CPU), mips mipsel)) +override_dh_autoreconf: sed -e '/\s*test-charpoly\s*\\/d' -i tests/Makefile.am - dh build --with autoreconf --parallel + dh_autoreconf -a -O--parallel endif override_dh_auto_configure: -- 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#855929: mclibs: FTBFS: Test failures
Control; tags -1 + patch On Thu, 23 Feb 2017 14:27:50 +0100 Lucas Nussbaum wrote: > Source: mclibs > Version: 20061220+dfsg3-3 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20170221 qa-ftbfs > Justification: FTBFS in stretch on amd64 > > Hi, > > During a rebuild of all packages in stretch (in a stretch chroot, not a > sid chroot), your package failed to build on amd64. > > Relevant part (hopefully): > > -L/<>/mclibs-20061220+dfsg3/lib -Wl,-static -leurodec -lpacklib > > -lkernlib -Wl,-dy -lm -lnsl -lcrypt -ldl -lgfortran > > gfortran -g -o eudtest -O3 -D_FORTIFY_SOURCE=2 -fno-range-check > > -fno-automatic -fno-second-underscore -fstack-protector > > --param=ssp-buffer-size=4 -fno-automatic -Wl,-z,relro > > -L/<>/mclibs-20061220+dfsg3/src/lib main.o steerd.o steerf.o > > testd.o testf.o `cernlib eurodec packlib` \ > > || rm -f eudtest > > rm -f eurodec.dat > > ln -s /<>/mclibs-20061220+dfsg3/build/mclibs/eurodec/eurodec.dat > > eurodec.dat > > cp > > /<>/mclibs-20061220+dfsg3/src/mclibs/eurodec/eudtest/eutitle.data > > eutitle.dat > > Testing eurodec > > ... using eudtest > > > > LOCB/LOCF: 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 'test' failed > > The full build log is available from: >http://aws-logs.debian.net/2017/02/21/mclibs_20061220+dfsg3-3_testing.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. Patch proposal attached, tested on amd64 and i386 sbuild. Thanks, _g. diff -Nru mclibs-20061220+dfsg3/debian/changelog mclibs-20061220+dfsg3/debian/changelog --- mclibs-20061220+dfsg3/debian/changelog 2013-08-23 19:13:53.0 +0200 +++ mclibs-20061220+dfsg3/debian/changelog 2017-03-05 22:14:26.0 +0100 @@ -1,3 +1,11 @@ +mclibs (20061220+dfsg3-3.1) unstable; urgency=medium + + * Non-maintainer upload + * patch 213-fix-test-suite-build.dpatch modified to build eudtest +with -no-pie (closes: #855929) + + -- Gilles Filippini Sun, 05 Mar 2017 22:14:26 +0100 + mclibs (20061220+dfsg3-3) unstable; urgency=low * debian/control: diff -Nru mclibs-20061220+dfsg3/debian/patches/213-fix-test-suite-build.dpatch mclibs-20061220+dfsg3/debian/patches/213-fix-test-suite-build.dpatch --- mclibs-20061220+dfsg3/debian/patches/213-fix-test-suite-build.dpatch 2013-08-23 19:13:53.0 +0200 +++ mclibs-20061220+dfsg3/debian/patches/213-fix-test-suite-build.dpatch 2017-03-05 22:13:53.0 +0100 @@ -20,9 +20,11 @@ diff -urNad mclibs-2006.dfsg.2~/src/mclibs/eurodec/eudtest/Imakefile mclibs-2006.dfsg.2/src/mclibs/eurodec/eudtest/Imakefile --- mclibs-2006.dfsg.2~/src/mclibs/eurodec/eudtest/Imakefile 1997-03-14 17:32:14.0 + +++ mclibs-2006.dfsg.2/src/mclibs/eurodec/eudtest/Imakefile2008-01-04 18:57:55.0 + -@@ -4,11 +4,10 @@ - +@@ -3,12 +3,12 @@ + DefinePackageLibrary(NullParameter) + FORTRANSAVEOPTION = FortranSaveFlags ++FORTRANOPTIONS += -no-pie -CernlibFortranProgramTarget(eudtest,$(OBJS),$(PACKAGE_LIB),$(PACKAGE_LIB),packlib) +CernlibFortranProgramTarget(eudtest,$(OBJS),NullParameter,NullParameter,eurodec packlib) signature.asc Description: OpenPGP digital signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
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: address 0x7f68e28cd740 exceeds the 32 bit address space or is not in the data segments' from 'mclibs: FTBFS: Test failures'. > thanks Stopping processing here. Please contact me if you need assistance. -- 855929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
