Bug#1103205: marked as done (ruby-pry-byebug: FTBFS: ERROR: Test "ruby3.3" failed. Exiting.)

2025-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 May 2025 11:09:17 + with message-id and subject line Bug#1104606: Removed package(s) from unstable has caused the Debian Bug report #1103205, regarding ruby-pry-byebug: FTBFS: ERROR: Test "ruby3.3" failed. Exiting. to be marked as done. This means that

Bug#1103205: ruby-pry-byebug: FTBFS: ERROR: Test "ruby3.3" failed. Exiting.

2025-04-14 Thread Santiago Vila
dh_autoreconf -O--buildsystem=ruby dh_auto_configure -O--buildsystem=ruby dh_ruby --configure dh_auto_build -O--buildsystem=ruby dh_ruby --build dh_auto_test -O--buildsystem=ruby dh_ruby --test create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=ruby

Bug#783728: marked as done (apt-xapian-index: FTBFS on missing test deps)

2025-04-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Apr 2025 13:22:56 + with message-id and subject line Bug#1100760: Removed package(s) from unstable has caused the Debian Bug report #783728, regarding apt-xapian-index: FTBFS on missing test deps to be marked as done. This means that you claim that the problem has

Bug#1101473: marked as done (CVE-2024-57823 fix and test in raptor2)

2025-03-29 Thread Debian Bug Tracking System
Your message dated Sat, 29 Mar 2025 15:11:11 + with message-id and subject line Bug#1067896: fixed in raptor2 2.0.16-6 has caused the Debian Bug report #1067896, regarding CVE-2024-57823 fix and test in raptor2 to be marked as done. This means that you claim that the problem has been dealt

Bug#155199: marked as done (apsfilter: Apsfilter 7.2.2-3 unable to print test page)

2025-01-26 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jan 2025 02:08:13 +0100 with message-id and subject line Re: Bug#155199: apsfilter: Apsfilter 7.2.2-3 unable to print test page has caused the Debian Bug report #155199, regarding apsfilter: Apsfilter 7.2.2-3 unable to print test page to be marked as done. This means

Bug#1093947: libuser: to enable test again

2025-01-23 Thread Bo YU
Source: libuser Version: 1:0.64+git20241106~dfsg-2 Severity: normal Tags: patch Dear Maintainer, The upload with #1092349 to disable the test to fix FTBFS issue, but new dependency crypt-r modules just got upload to unstable[1] almost at the same moment. So now it can be enable test during build

Processed: pagure: test fail in Python 3.13, etc

2024-12-21 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1084587 [src:pagure] pagure: removal of Python standard libraries in Python 3.13 Added tag(s) patch. > tags 1085764 patch Bug #1085764 [src:pagure] pagure: Python SyntaxWarning Added tag(s) patch. > tags 1064530 patch Bug #1064530 [src:pagure] pag

Bug#1084587: pagure: test fail in Python 3.13, etc

2024-12-21 Thread Rebecca N. Palmer
Control: tags -1 patch Control: tags 1085764 patch Control: tags 1064530 patch Control: tags 1046324 patch These are all fixed in https://salsa.debian.org/debian/pagure/-/merge_requests/2 (Caution: untested, beyond a CI run that doesn't run the upstream tests.) I intend to look at pagure's othe

Bug#1017816: marked as done (golang-github-bsm-pool: Flaky test on i386, blocking other packages migration)

2024-11-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Nov 2024 23:53:59 + with message-id and subject line Bug#1017816: fixed in golang-github-bsm-pool 0.8.0-7 has caused the Debian Bug report #1017816, regarding golang-github-bsm-pool: Flaky test on i386, blocking other packages migration to be marked as done. This

Bug#1017816: golang-github-bsm-pool: Flaky test on i386, blocking other packages migration

2024-11-21 Thread Santiago Vila
forwarded 1017816 https://github.com/bsm/pool/issues/4 thanks Hello. I've just forwarded this upstream, but maybe we should go ahead and remove the package. It used to be a (build-)dependency for gitea, but gitea does not exist anymore. Thanks.

Processed: golang-github-bsm-pool: Flaky test on i386, blocking other packages migration

2024-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1017816 https://github.com/bsm/pool/issues/4 Bug #1017816 [src:golang-github-bsm-pool] golang-github-bsm-pool: Flaky test on i386, blocking other packages migration Set Bug forwarded-to-address to 'https://github.com/bsm/pool/

Bug#398430: marked as done (guessnet: same test results, different mappings)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 16:59:46 + with message-id and subject line Bug#1084746: Removed package(s) from unstable has caused the Debian Bug report #398430, regarding guessnet: same test results, different mappings to be marked as done. This means that you claim that the problem

Bug#330472: marked as done (guessnet: always times out on the pppoe test)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 16:59:46 + with message-id and subject line Bug#1084746: Removed package(s) from unstable has caused the Debian Bug report #330472, regarding guessnet: always times out on the pppoe test to be marked as done. This means that you claim that the problem has

Bug#312119: marked as done (guessnet: test peer address misdetects if multiple networks on same gateway)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 16:59:46 + with message-id and subject line Bug#1084746: Removed package(s) from unstable has caused the Debian Bug report #312119, regarding guessnet: test peer address misdetects if multiple networks on same gateway to be marked as done. This means that

Bug#349092: marked as done (guessnet: test pppoe (and command) always fails)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 16:59:46 + with message-id and subject line Bug#1084746: Removed package(s) from unstable has caused the Debian Bug report #349092, regarding guessnet: test pppoe (and command) always fails to be marked as done. This means that you claim that the problem

Bug#268572: marked as done (guessnet: Please allow two test peer lines with the same IP address and different MAC addresses)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 16:59:46 + with message-id and subject line Bug#1084746: Removed package(s) from unstable has caused the Debian Bug report #268572, regarding guessnet: Please allow two test peer lines with the same IP address and different MAC addresses to be marked as

Bug#1065084: marked as done (libelfin fails autopkg test with LLVM 18)

2024-10-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Oct 2024 15:44:56 + with message-id and subject line Bug#1065084: fixed in libelfin 0.3-5 has caused the Debian Bug report #1065084, regarding libelfin fails autopkg test with LLVM 18 to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: libelfin fails autopkg test with LLVM 18

2024-10-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1065084 [src:libelfin] libelfin fails autopkg test with LLVM 18 Severity set to 'serious' from 'important' -- 1065084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065084 Debian Bug Tracking System Contact ow.

Bug#697475: marked as done (git2cl: test for reading from stdin broken)

2024-10-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Oct 2024 16:49:17 + with message-id and subject line Bug#697475: fixed in git2cl 1:3.0-1 has caused the Debian Bug report #697475, regarding git2cl: test for reading from stdin broken to be marked as done. This means that you claim that the problem has been dealt

Bug#1080275: marked as done (FTBFS with setuptools >= 72: error: invalid command 'test')

2024-09-12 Thread Debian Bug Tracking System
Your message dated Thu, 12 Sep 2024 12:19:44 + with message-id and subject line Bug#1080275: fixed in hovercraft 2.7-7 has caused the Debian Bug report #1080275, regarding FTBFS with setuptools >= 72: error: invalid command 'test' to be marked as done. This means that you c

Bug#1079763: marked as done (setuptools test command is removed)

2024-09-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Sep 2024 12:51:43 + with message-id and subject line Bug#1079763: fixed in python-svg.path 6.3-3 has caused the Debian Bug report #1079763, regarding setuptools test command is removed to be marked as done. This means that you claim that the problem has been dealt

Bug#1080275: FTBFS with setuptools >= 72: error: invalid command 'test'

2024-09-01 Thread Stefano Rivera
Source: hovercraft Version: 2.7-6 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, hovercraft failed to rebuild. FWIW: I think these bugs were all caused

Bug#1080135: Fallout from setuptools dropping the test command

2024-08-31 Thread Stefano Rivera
FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what ma

Bug#1079763: setuptools test command is removed

2024-08-27 Thread Matthias Klose
Package: src:python-svg.path Version: 6.3-2 Severity: serious Tags: sid trixie setuptools test command is removed, the package at least uses this command in it's autopkg tests. setuptools v72.0.0: Deprecations and Removals - - The test command has been removed.

Bug#1078060: marked as done (libtap-formatter-junit-perl: FTBFS with newer versions of Test::Harness: t/formatter.t failure)

2024-08-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Aug 2024 09:49:29 + with message-id and subject line Bug#1078060: fixed in libtap-formatter-junit-perl 0.16-1 has caused the Debian Bug report #1078060, regarding libtap-formatter-junit-perl: FTBFS with newer versions of Test::Harness: t/formatter.t failure to be

Bug#1078060: libtap-formatter-junit-perl: FTBFS with newer versions of Test::Harness: t/formatter.t failure

2024-08-21 Thread Étienne Mollier
21:50:19-07:00 America/Vancouver > - Sigh... neglected to consider development versions of Test::Harness in > the > recent updates to "t/formatter.t"; although the fixes were released in > v3.44, they were also present in the v3.43_* development versions. Th

Bug#1078378: marked as done (silkaj: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code 13)

2024-08-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Aug 2024 18:52:29 + with message-id and subject line Bug#1078378: fixed in pendulum 3.0.0-1 has caused the Debian Bug report #1078378, regarding silkaj: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code 13 to be

Bug#1078378: silkaj: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code 13

2024-08-13 Thread weepingclown
Hi, While there was no bug report about orphaning this package, the upload history is quite clear on that the previous maintainer has orphaned it, and hence I took the liberty of adopting the package and bringing it under python-team umbrella. The package has been updated to 3.0.0 stable versio

Processed: Re: silkaj: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code 13

2024-08-11 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-pendulum Bug #1078378 [src:silkaj] silkaj: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 returned exit code 13 Bug reassigned from package 'src:silkaj' to 'python3-pendulum'. No lo

Bug#1078060: libtap-formatter-junit-perl: FTBFS with newer versions of Test::Harness: t/formatter.t failure

2024-08-06 Thread Niko Tyni
Source: libtap-formatter-junit-perl Version: 0.11-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.40-transition Forwarded: https://github.com/bleargh45/TAP-Formatter-JUnit/issues/15 This package fails to build from source with newer versions of the Test::Harness module

Bug#746198: marked as done (unar fails to extract test rar on arm.)

2024-04-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Apr 2024 00:44:38 +0200 with message-id and subject line Re: Bug#746198: unar fails to extract test rar on arm. has caused the Debian Bug report #746198, regarding unar fails to extract test rar on arm. to be marked as done. This means that you claim that the problem

Bug#1066003: marked as done (libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.)

2024-03-20 Thread Debian Bug Tracking System
Your message dated Wed, 20 Mar 2024 21:40:03 + with message-id and subject line Bug#1066003: fixed in db5.3 5.3.28+dfsg2-6 has caused the Debian Bug report #1066003, regarding libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed. to be marked as done

Bug#1066752: marked as done (django-maintenancemode: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" --system=custom "--test-args=PYTHONPATH=. {interpreter} -m pytest" ret

2024-03-17 Thread Debian Bug Tracking System
Your message dated Sun, 17 Mar 2024 13:04:23 + with message-id and subject line Bug#1066752: fixed in django-maintenancemode 0.11.7+git221001-4 has caused the Debian Bug report #1066752, regarding django-maintenancemode: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "

Bug#1066752: django-maintenancemode: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" --system=custom "--test-args=PYTHONPATH=. {interpreter} -m pytest" returned exit code

2024-03-13 Thread Lucas Nussbaum
): > make[1]: Entering directory '/<>' > dh_auto_test -- --system=custom --test-args="PYTHONPATH=. {interpreter} -m > pytest" > I: pybuild base:305: PYTHONPATH=. python3.12 -m pytest > = test session starts >

Bug#1058112: marked as done (python-coverage-test-runner: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 14:44:30 + with message-id and subject line Bug#1058112: fixed in python-coverage-test-runner 1.13.1-5 has caused the Debian Bug report #1058112, regarding python-coverage-test-runner: FTBFS: ModuleNotFoundError: No module named 'imp' to be mark

Bug#1058352: marked as done (pytest-localserver: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 08:41:33 + with message-id and subject line Bug#1058352: fixed in pytest-localserver 0.8.1-1 has caused the Debian Bug report #1058352, regarding pytest-localserver: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12

Bug#1052652: ghostscript: eps2write fails on test file

2024-01-05 Thread Steven Robbins
tags 1052652 upstream forwarded 1052652 https://bugs.ghostscript.com/show_bug.cgi?id=707368 thanks On Mon, 25 Sep 2023 20:05:27 +0200 Roland Rosenfeld wrote: > Package: ghostscript > Version: 10.02.0~dfsg-2 > Severity: important > > Dear Maintainer, > > upgrading ghostscript from 10.01.2~dfsg-

Processed: Re: ghostscript: eps2write fails on test file

2024-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1052652 upstream Bug #1052652 [ghostscript] ghostscript: eps2write fails with -sPageList=1 Added tag(s) upstream. > forwarded 1052652 https://bugs.ghostscript.com/show_bug.cgi?id=707368 Bug #1052652 [ghostscript] ghostscript: eps2write fails

Bug#1058297: marked as done (python-svg.path: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 15:05:50 + with message-id and subject line Bug#1058297: fixed in python-svg.path 6.3-2 has caused the Debian Bug report #1058297, regarding python-svg.path: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12

Bug#1058352: pytest-localserver: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2023-12-12 Thread Lucas Nussbaum
e[1]: Entering directory '/<>' > PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -x" > dh_auto_test > I: pybuild base:310: python3.12 -m pytest -v -x > = test session starts > == >

Bug#1058297: python-svg.path: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2023-12-12 Thread Lucas Nussbaum
ifest file 'src/svg.path.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files found matching 'Makefile' > adding license file 'LICENSE.txt' > writing manifest file 'src/svg.path.egg-info/SOURCES.tx

Bug#1058112: python-coverage-test-runner: FTBFS: ModuleNotFoundError: No module named 'imp'

2023-12-12 Thread Lucas Nussbaum
Source: python-coverage-test-runner Version: 1.13.1-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#954560: marked as done (debdry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8" returned exit code 13)

2023-09-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Sep 2023 16:31:53 + with message-id and subject line Bug#1051718: Removed package(s) from unstable has caused the Debian Bug report #954560, regarding debdry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8" returned exit cod

Bug#1040322: marked as done (debdry: should not ship test data in /usr/lib/python3/dist-packages/control)

2023-09-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Sep 2023 16:31:53 + with message-id and subject line Bug#1051718: Removed package(s) from unstable has caused the Debian Bug report #1040322, regarding debdry: should not ship test data in /usr/lib/python3/dist-packages/control to be marked as done. This means

Processed: Re: ghostscript: eps2write fails on test file

2023-09-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1052652 ghostscript: eps2write fails with -sPageList=1 Bug #1052652 [ghostscript] ghostscript: eps2write fails on test file Changed Bug title to 'ghostscript: eps2write fails with -sPageList=1' from 'ghostscript: eps2w

Bug#1052652: ghostscript: eps2write fails on test file

2023-09-26 Thread Roland Rosenfeld
retitle 1052652 ghostscript: eps2write fails with -sPageList=1 thanks > Running > gs -dSAFER -sDEVICE=eps2write -sPageList=1 -o line.eps line.pdf > on 10.01.2~dfsg-1 (and older) versions works as expected, but fails > with the following output on 10.02.0~dfsg-2: > > $ gs -dSAFER -sDEVICE=eps2writ

Bug#1052652: ghostscript: eps2write fails on test file

2023-09-25 Thread Roland Rosenfeld
Package: ghostscript Version: 10.02.0~dfsg-2 Severity: important Dear Maintainer, upgrading ghostscript from 10.01.2~dfsg-1 to 10.02.0~dfsg-2 triggers a regression in the testsuite of fig2dev. I now stripped down the first test failure (testcase 17) to the following problem: Running gs -dSAFER

Bug#1040322: debdry: should not ship test data in /usr/lib/python3/dist-packages/control

2023-07-04 Thread Helmut Grohne
Package: debdry Version: 0.2.2-1 Severity: serious debdry creates a control file in its test suite. This file happens to get installed into /usr/lib/python3/dist-packages/control and this happens to cause an undeclared file conflict with python3-kombu. I'm filing this with debdry, becau

Bug#711218: marked as done (add a IT8 target test)

2023-05-09 Thread Debian Bug Tracking System
Your message dated Tue, 09 May 2023 15:01:54 + with message-id and subject line Bug#1035806: Removed package(s) from unstable has caused the Debian Bug report #711218, regarding add a IT8 target test to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1016728: marked as done (autoconf: _AC_PROG_CXX_STDCXX_EDITION_TRY test is broken due to typo)

2023-01-14 Thread Debian Bug Tracking System
Your message dated Sat, 14 Jan 2023 18:19:22 + with message-id and subject line Bug#1016728: fixed in autoconf 2.71-3 has caused the Debian Bug report #1016728, regarding autoconf: _AC_PROG_CXX_STDCXX_EDITION_TRY test is broken due to typo to be marked as done. This means that you claim that

Bug#1026546: zope.testing: FTBFS: AssertionError: Failed doctest test for doctestcase.txt

2022-12-20 Thread Lucas Nussbaum
c/zope/testing/cleanup.txt -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/doctestcase.txt -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/formparser.txt -> > /<>/.pybuild/cpython3_3.

Bug#1017816: golang-github-bsm-pool: Flaky test on i386, blocking other packages migration

2022-08-20 Thread Shengjing Zhu
Source: golang-github-bsm-pool Version: 0.8.0-6 Severity: serious Tags: ftbfs X-Debbugs-Cc: z...@debian.org https://ci.debian.net/user/britney/jobs?package=golang-github-bsm-pool&suite[]=testing&arch[]=i386 https://ci.debian.net/packages/g/golang-github-bsm-pool/testing/i386/ The test

Bug#1016728: autoconf: _AC_PROG_CXX_STDCXX_EDITION_TRY test is broken due to typo

2022-08-06 Thread Ron
and which make it obvious this test is simply failing "unnoticed" in the case where the compiler default isn't already greater than C++11 ... The problem is a simple typo in _AC_PROG_CXX_STDCXX_EDITION_TRY which is fixed by the patch below. Its correctness can be cross chec

Bug#1013532: marked as done (monero: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 "ARGS+=--output-on-failure -E 'functional_tests_rpc|core_tests|cnv

2022-06-28 Thread Debian Bug Tracking System
Your message dated Tue, 28 Jun 2022 16:34:21 + with message-id and subject line Bug#1013532: fixed in monero 0.17.3.2+~0+20200826-1 has caused the Debian Bug report #1013532, regarding monero: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose AR

Bug#1002360: marked as done (zope.exceptions: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

2022-06-26 Thread Debian Bug Tracking System
Your message dated Sun, 26 Jun 2022 13:50:25 + with message-id and subject line Bug#1002360: fixed in zope.exceptions 4.5-1 has caused the Debian Bug report #1002360, regarding zope.exceptions: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned ex

Bug#1013532: monero: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 "ARGS+=--output-on-failure -E 'functional_tests_rpc|core_tests|cnv4-jit|hash-slow-

2022-06-24 Thread Lucas Nussbaum
lt;>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtur

Bug#954884: marked as done (Please make autopkgtests cross-test-friendly)

2022-06-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jun 2022 15:47:07 +0200 with message-id and subject line Re: Bug#954884: Please make autopkgtests cross-test-friendly has caused the Debian Bug report #954884, regarding Please make autopkgtests cross-test-friendly to be marked as done. This means that you claim that

python-coverage-test-runner is marked for autoremoval from testing

2022-05-26 Thread Debian testing autoremoval watch
python-coverage-test-runner 1.13.1-4 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https

Processed: Re: Bug#1006038: git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

2022-02-19 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48 Bug #1006038 [src:git-remote-hg] git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/mnauw/git-remote-hg/i

Bug#1006038: git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

2022-02-19 Thread Paul Wise
Control: forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48 On Sat, 2022-02-19 at 07:31 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. This appears to be caused by git 1:2.35.1-1 in unstable, the autopkgtests regressed

Bug#795421: marked as done (version 5.01 freezes on test #7 in SMP mode)

2022-01-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jan 2022 17:50:01 +0100 with message-id <06b5cc2ec86cc08e00e44adb104a20a6fc811ad2.ca...@scientia.net> and subject line Re: Bug#795421: version 5.01 freezes on test #7 in SMP mode has caused the Debian Bug report #795421, regarding version 5.01 freezes on test #7

Bug#795421: version 5.01 freezes on test #7 in SMP mode

2022-01-11 Thread Fabio Fantoni
Hi, I also had similar freeze with 5.01 but in new version in experimental as saw in my tests solves freeze cases. Please reply if this still happen on latest version, otherwise I'll close this. OpenPGP_signature Description: OpenPGP digital signature

Bug#977217: marked as done (New upstream release available, fixes stuck test on UEFI systems)

2022-01-10 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jan 2022 01:18:31 + with message-id and subject line Bug#977217: fixed in memtest86+ 5.31b+dfsg-1 has caused the Debian Bug report #977217, regarding New upstream release available, fixes stuck test on UEFI systems to be marked as done. This means that you claim

Bug#1002196: marked as done (python-kaptan: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

2021-12-28 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 12:21:04 + with message-id and subject line Bug#1002196: fixed in python-kaptan 0.5.12-1 has caused the Debian Bug report #1002196, regarding python-kaptan: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned ex

Bug#1002360: zope.exceptions: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

2021-12-22 Thread Lucas Nussbaum
ests > running egg_info > writing src/zope.exceptions.egg-info/PKG-INFO > writing dependency_links to src/zope.exceptions.egg-info/dependency_links.txt > writing namespace_packages to > src/zope.exceptions.egg-info/namespace_packages.txt > writing requirements to src/zope.excep

Bug#1002196: python-kaptan: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

2021-12-21 Thread Lucas Nussbaum
;/.pybuild/cpython3_3.9_kaptan/build/kaptan/handlers > copying kaptan/handlers/dict_handler.py -> > /<>/.pybuild/cpython3_3.9_kaptan/build/kaptan/handlers >dh_auto_test -O--buildsystem=pybuild > dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 >

Bug#999534: marked as done (python-bayespy: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2021-11-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Nov 2021 12:03:45 + with message-id and subject line Bug#999534: fixed in python-bayespy 0.5.22-1 has caused the Debian Bug report #999534, regarding python-bayespy: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i

Bug#999534: python-bayespy: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

2021-11-11 Thread Lucas Nussbaum
y/build; > python3.9 -m pytest > = test session starts > == > platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 > rootdir: /<> > collected 124 items / 1 error / 123 se

Bug#993373: [PATCH 1/2] Populate with dummy test data

2021-08-31 Thread Madie K. Mckeel
This is derived (and slightly expanded) from the old-upstream revision 144. --- tests/check_fstab/a | 1 + tests/check_fstab/b | 1 + tests/check_fstab/c | 1 + tests/check_fstab/d | 1 + tests/check_fstab/e | 1 + 5 files changed, 5 insertions(+) create mode 100644 tests/check_fstab/a create m

Bug#975696: marked as done (link-grammar: multi-thread test fails)

2021-01-01 Thread Debian Bug Tracking System
Your message dated Sat, 02 Jan 2021 00:05:41 + with message-id and subject line Bug#975696: fixed in link-grammar 5.8.0-6 has caused the Debian Bug report #975696, regarding link-grammar: multi-thread test fails to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-29 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #975696 [src:link-grammar] link-grammar: multi-thread test fails Severity set to 'serious' from 'important' -- 975696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975696 Debian Bug Tracking System Contact ow.

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-29 Thread Jonas Smedegaard
id the BTS sports and leave this > > bug open until link-grammar builds and passes its autopkgtests > > reliably. > > I closed the bugreport when in -3 I optimistally expected the test > failures to be gone. I agree this bug should stay open when that's > not the case.

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-29 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #975696 [src:link-grammar] link-grammar: multi-thread test fails Severity set to 'important' from 'serious' -- 975696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975696 Debian Bug Tracking System Contact ow.

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-29 Thread Jonas Smedegaard
uilds and passes its autopkgtests reliably. I closed the bugreport when in -3 I optimistally expected the test failures to be gone. I agree this bug should stay open when that's not the case. I disagree, however, that the current level of flakiness renders the package unsuitable for a stable D

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-29 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #975696 {Done: Jonas Smedegaard } [src:link-grammar] link-grammar: multi-thread test fails 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bu

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-29 Thread Graham Inggs
Control: reopen -1 Hi Jonas The build of link-grammar/5.8.0-3 has already failed on ppc64el [1] (details below). As fun as it is, please let's avoid the BTS sports and leave this bug open until link-grammar builds and passes its autopkgtests reliably. Regards Graham [1] https://buildd.debian

Bug#975696: marked as done (link-grammar: multi-thread test fails)

2020-12-29 Thread Debian Bug Tracking System
Your message dated Tue, 29 Dec 2020 18:03:39 + with message-id and subject line Bug#975696: fixed in link-grammar 5.8.0-3 has caused the Debian Bug report #975696, regarding link-grammar: multi-thread test fails to be marked as done. This means that you claim that the problem has been dealt

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-29 Thread Graham Inggs
Control: severity -1 serious Hi Jonas Happy Holidays! On Sun, 27 Dec 2020 at 19:12, Jonas Smedegaard wrote: > I tightened the test checking - enabled them during build and made them > more verbose (and explicitly passed environment variable "srcdata" which > might hav

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-29 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #975696 [src:link-grammar] link-grammar: multi-thread test fails Severity set to 'serious' from 'important' -- 975696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975696 Debian Bug Tracking System Contact ow.

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-27 Thread Jonas Smedegaard
Control: severity -1 important Quoting Graham Inggs (2020-11-25 09:59:36) > The upload of link-grammar 5.8.0-1 intermittently FTBFS on several > architectures, e.g. arm64 [1], armel [2] and ppc64 [3]. The failures > all happen during the multi-thread test with various errors: > do

Processed: Re: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

2020-12-27 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #975696 [src:link-grammar] link-grammar: multi-thread test fails Severity set to 'important' from 'serious' -- 975696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975696 Debian Bug Tracking System Contact ow.

Bug#976569: marked as done (numcodecs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13)

2020-12-07 Thread Debian Bug Tracking System
Your message dated Mon, 07 Dec 2020 20:21:23 + with message-id and subject line Bug#976569: fixed in c-blosc 1.20.1+ds1-2 has caused the Debian Bug report #976569, regarding numcodecs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned

Bug#973169: marked as done (python-chameleon: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)

2020-11-29 Thread Debian Bug Tracking System
Your message dated Sun, 29 Nov 2020 10:04:33 + with message-id and subject line Bug#973169: fixed in python-chameleon 3.8.1-1 has caused the Debian Bug report #973169, regarding python-chameleon: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned ex

Processed: link-grammar: multi-thread test fails

2020-11-25 Thread Debian Bug Tracking System
Processing control commands: > block 972670 by -1 Bug #972670 {Done: Paul Gevers } [src:link-grammar] src:link-grammar: fails to migrate to testing for too long: FTBFS on arm64 and armhf autopkgtest regression 972670 was not blocked by any bugs. 972670 was not blocking any bugs. Added blocking b

Bug#975696: link-grammar: multi-thread test fails

2020-11-25 Thread Graham Inggs
several architectures, e.g. arm64 [1], armel [2] and ppc64 [3]. The failures all happen during the multi-thread test with various errors: double free or corruption (fasttop) free(): invalid pointer malloc_consolidate(): invalid chunk size Segmentation fault corrupted double-linked list Giving back the

Bug#973169: python-chameleon: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

2020-10-27 Thread Lucas Nussbaum
Source: python-chameleon Version: 3.6.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh bui

Bug#954590: marked as done (python-bayespy: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13)

2020-07-09 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jul 2020 16:04:50 + with message-id and subject line Bug#954590: fixed in python-bayespy 0.5.18-3 has caused the Debian Bug report #954590, regarding python-bayespy: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8"

python-coverage-test-runner_1.13.1-4_source.changes ACCEPTED into unstable

2020-04-26 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 26 Apr 2020 13:10:00 -0300 Source: python-coverage-test-runner Architecture: source Version: 1.13.1-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Jair Reis Changes: python

Processing of python-coverage-test-runner_1.13.1-4_source.changes

2020-04-26 Thread Debian FTP Masters
python-coverage-test-runner_1.13.1-4_source.changes uploaded successfully to localhost along with the files: python-coverage-test-runner_1.13.1-4.dsc python-coverage-test-runner_1.13.1-4.debian.tar.xz python-coverage-test-runner_1.13.1-4_source.buildinfo Greetings, Your Debian

Bug#954590: python-bayespy: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13

2020-03-22 Thread Lucas Nussbaum
ory '/<>' > xvfb-run -a dh_auto_test > I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_bayespy/build; > python3.7 -m nose -v > Test the creation of Bernoulli nodes. ... ok > Test mixture of Bernoulli ... > /<>/.pybuild/cpython3_3.7_bayespy/bu

Bug#954560: debdry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8" returned exit code 13

2020-03-22 Thread Lucas Nussbaum
ython3.7 -m unittest discover -v > test_plainfield (test.test_control.TestCombine) ... ERROR > test_smartfield_plain (test.test_control.TestCombine) ... ERROR > test_smartfield_smart (test.test_control.TestCombine) ... ERROR > test_plainfield (test.test_control.TestDiff) ... ERROR > test_

This TUYA mini wifi PTZ camera there is not MOQ, you can take one for test.

2020-03-19 Thread sunivision
Hello Manager How are you? Are you interested in this TUYA wifi mini PTZ camera? This camera is 1080P, come with AF 2.8-12MM 4 TIMES ZOOM LENS This camera can use outdoor and indoor, IP66 waterproof rate. This camera can support Google home or Amazon Alex (Optional). If you have any question,

Bug#952215: marked as done (golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/facebookgo/stack returned exit code 1)

2020-03-16 Thread Debian Bug Tracking System
-gnu && go test -vet=off -v -p 4 github.com/facebookgo/stack returned exit code 1 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 f

Bug#952215: golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/facebookgo/stack returned exit code 1

2020-02-23 Thread Lucas Nussbaum
; internal/testlog > math > runtime > internal/reflectlite > sync > errors > sort > io > internal/oserror > strconv > syscall > bytes > strings > reflect > internal/syscall/unix > time > internal/poll > os > internal/fmtsort > path/filepath > fmt

Bug#952176: golang-github-facebookgo-ensure: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/facebookgo/ensure returned exit code 1

2020-02-23 Thread Lucas Nussbaum
github.com/facebookgo/subset > os > path/filepath > fmt > encoding/hex > github.com/facebookgo/stack > github.com/davecgh/go-spew/spew > github.com/facebookgo/ensure >dh_auto_test -O--buildsystem=golang > cd obj-x86_64-linux-gnu &

Bug#943517: marked as done (boxbackup: FTBFS with test failures)

2020-02-15 Thread Debian Bug Tracking System
Your message dated Sat, 15 Feb 2020 20:36:31 + with message-id and subject line Bug#943517: fixed in boxbackup 0.13~~git20190527.g039c4a1-4 has caused the Debian Bug report #943517, regarding boxbackup: FTBFS with test failures to be marked as done. This means that you claim that the problem

python-coverage-test-runner_1.13.1-3_source.changes ACCEPTED into unstable

2019-11-29 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 29 Nov 2019 22:44:36 -0500 Source: python-coverage-test-runner Architecture: source Version: 1.13.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sandro Tosi Closes: 937666

Bug#937666: marked as done (python-coverage-test-runner: Python2 removal in sid/bullseye)

2019-11-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Nov 2019 04:04:21 + with message-id and subject line Bug#937666: fixed in python-coverage-test-runner 1.13.1-3 has caused the Debian Bug report #937666, regarding python-coverage-test-runner: Python2 removal in sid/bullseye to be marked as done. This means that you

Bug#937666: python-coverage-test-runner: Python2 removal in sid/bullseye

2019-11-09 Thread peter green
severity 937666 serious thanks python-coverage-test-runner depends on the python-coverage binary package which is no longer built by the python-coverage source package.

Processed: re: python-coverage-test-runner: Python2 removal in sid/bullseye

2019-11-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 937666 serious Bug #937666 [src:python-coverage-test-runner] python-coverage-test-runner: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Ple

  1   2   3   >