Re: Thanks for helping sra-sdk 3 migrate!

2023-01-29 Thread Paul Gevers
Hi Aaron, On 26-01-2023 19:15, Paul Gevers wrote: You're welcome. Next time in similar situations, don't hesitate to contact us. I don't think our tools could have handled this situation without interference. britney2 (our migration software) still refuses to let sra-sdk migrate and replace

Re: Thanks for helping sra-sdk 3 migrate!

2023-01-26 Thread Paul Gevers
Hi Aaron, On 26-01-2023 18:06, Aaron M. Ucko wrote: I see that https://qa.debian.org/excuses.php?package=sra-sdk now has autopkgtest for ngs-sdk/2.11.2-4: amd64: Pass, arm64: Pass, armel: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored

Re: Bug#991919: Bioconductor API Bump to 3.13

2021-08-26 Thread Paul Gevers
Hi Andreas, On 26-08-2021 07:45, Andreas Tille wrote: > Hi Dylan, > > On Sun, Aug 15, 2021 at 01:17:29PM +0200, Andreas Tille wrote: >> Hi, >> >> On Sun, Aug 15, 2021 at 10:01:21AM +0200, Dylan Aïssi wrote: >>> >>> The transition tracker is on at >>>

Re: Bug#987007: release-notes: Release notes for Bullseye by Debian Med team

2021-04-16 Thread Paul Gevers
Hi Andreas, On 15-04-2021 16:01, Andreas Tille wrote: > I'm fine with all your corrections (and updated Git accordingly). pushed, thanks. Paul OpenPGP_signature Description: OpenPGP digital signature

Re: Bug#954270: [RFS] kmc: arm64 autopkgtest time out

2020-12-10 Thread Paul Gevers
Hi Oops, missed a part of the message. On 10-12-2020 11:00, Andreas Tille wrote: >> It seems that this didn't work on our armhf worker: >> https://ci.debian.net/packages/k/kmc/testing/armhf/ >> >> The amd64 run didn't happen on the big box. > > In the kmc case I'm seriously wondering whether we

Re: Bug#954270: [RFS] kmc: arm64 autopkgtest time out

2020-12-10 Thread Paul Gevers
Hi Andreas, On 10-12-2020 11:00, Andreas Tille wrote: > just a general question: The general overview page like > >https://ci.debian.net/packages/k/kmc/ > > does not seem to be updated while the specific architecture > pages like You can see at the bottom of the page when it was last

Re: [RFS] kmc: arm64 autopkgtest time out

2020-12-10 Thread Paul Gevers
Control: reopen -1 Control: retitle -1 kmc: autopgktest times out on multimulticore hosts Hi On 06-12-2020 22:06, Étienne Mollier wrote: > Paul Gevers, on 2020-12-06 20:54:43 +0100: >> It recently started to time out on amd64 too, but not always [1]. And >> when we added armhf,

Re: [RFS] kmc: arm64 autopkgtest time out

2020-12-06 Thread Paul Gevers
Control: severity -1 serious Hi Étielle, On 06-12-2020 19:31, Étienne Mollier wrote: > I tried to trigger the kmc bug #954270 from an autopkgtest run > within a qemu-user arm64 machine (host amd64). Unfortunately, I > failed to reproduce any freeze; the run executes in a matter of > a minute or

Re: armhf regressions in a few packages

2020-11-22 Thread Paul Gevers
Hi Nilesh, On 21-11-2020 22:11, Nilesh Patra wrote: > I've seen some packages failing _only_ on armhf when I added > autopkgtests to them. Murasaki[1] and lighter[2] for example. > They seem to fail with this common error message: Bus Error -- > > > Could it be because of lack of RAM/memory

Re: Issue with jellyfish autopkgtest on arm64

2020-11-17 Thread Paul Gevers
Hi Andreas, On 16-11-2020 22:20, Andreas Tille wrote: > Hi, > > according to the arm64 log[1] the autopkgtest of jellyfish fails with > >tests/generate_sequence.sh: 6: /usr/lib/jellyfish/bin/generate_sequence: > Exec format error > Which I assume is this:

Re: Kmc might cause iva autopkgtest fail on arm64 (possibly memory issue?)

2020-11-16 Thread Paul Gevers
Hi, On 16-11-2020 16:58, Andreas Tille wrote:>> This is on ARM, and tests on amd64 are OK... could this just be a RAM>> issue on the test box? I very vaguely remember that kmc needs quite a>> bit of RAM, which I'm not sure all of the ARM CI boxes have?>> Just guessing. Our arm64 hosts have about

Re: Tests failing in many chroots but passing in some others

2020-10-17 Thread Paul Gevers
Hi Pierre, On 16-10-2020 22:49, Pierre Gruet wrote: > I have just found this was due to a file not being closed with the > close() method. Afterwards some other tests were counting open files and > failing because of this file not being closed whereas they expected it. > I guess the Java garbage

Re: Tests failing in many chroots but passing in some others

2020-09-24 Thread Paul Gevers
Hi, On 22-09-2020 22:39, Pierre Gruet wrote: > Thanks for this precision concerning lxc. > The failing tests are basically just opening and closing files, counting > open files... I think this is not an issue here. I think I recently heard about issues regarding docker and lxc in this regard. I

Re: Tests failing in many chroots but passing in some others

2020-09-22 Thread Paul Gevers
Hi Pierre, On 22-09-2020 21:45, Pierre Gruet wrote: > Dear Debian CI project members, > > In Debian-med we have the package libsis-jhdf5-java. I can build it > inside or outside a chroot on my computer with no error concerning > build-time tests, which are also run by autopkgtest -- also fine. >

Re: How much data load is acceptable in debian/ dir and upstream (Was: edtsurf_0.2009-7_amd64.changes REJECTED)

2020-09-15 Thread Paul Gevers
Hi Andreas, On 14-09-2020 21:04, Andreas Tille wrote: > In the case of larger data sets it seems to be natural to provide the > data in a separate binary architecture all package to not bloat the > machines of users who do not want this and also save bandwidt of our > mirroring network. New

Re: Tests seem to work again

2020-04-11 Thread Paul Gevers
Hi Liubov, On 11-04-2020 20:29, Liubov Chuprikova wrote: > Do you think, it makes sense to keep it longer? Not much, no. I'm thus closing the bug. Paul signature.asc Description: OpenPGP digital signature

Re: FastQC users attention: Please comment on the remaining failures! (Was: Bug#950311: fastqc: autopkgtest regression: debhelper bump moved files to different location)

2020-01-31 Thread Paul Gevers
Hi, On Fri, 31 Jan 2020 12:22:42 +0100 Andreas Tille wrote: > I'd love if some users of fastqc could comment on the outcome of these > tests. Me too. Because how it looks to me (Release Team member hat on) this test should actually not reward FastQC with the reduced age. Hence I have aged this

Re: picard-tools: autopkgtest regression

2019-01-17 Thread Paul Gevers
Hi Olivier, On 17-01-2019 12:12, Olivier Sallou wrote: > I tested in buster with updated libbarclay-java (2.1.0-3 pushed today to > allow migration to testing) and could rebuild picard-tools from source > (with tests) with no issue. > > > I tried again with libbarclay-java 2.1.0-2 and faced no

Re: picard-tools: autopkgtest regression

2019-01-17 Thread Paul Gevers
Hi Olivier, On 17-01-2019 09:38, Olivier Sallou wrote: > On 1/17/19 9:25 AM, Paul Gevers wrote: >> autopkgtest [04:38:35]: test run-unit-test: [--- >> Error: Unable to initialize main class picard.cmdline.PicardCommandLine >> Caused by: java.lang.NoClass

Re: [Debian-med-packaging] Bug#911793: autopkgtest regression: Segmentation fault

2018-11-20 Thread Paul Gevers
Hi Emmanuel, On 19-11-18 22:11, Emmanuel Promayon wrote: > On 19/11/2018 19:32, Paul Gevers wrote: >> If you comment on the RC bug that is triggering the autoremoval, then >> the timer gets reset. Just explain there why it can't be fixed NOW. I >> still agree with Mattia: &

Re: autopkgtest regression: Segmentation fault

2018-11-19 Thread Paul Gevers
Hi Emmanuel, On 19-11-18 13:06, Emmanuel Promayon wrote: > It seems camitk-4.1.2-2 is not very lucky! So you are caught in the hdf5 transition: https://release.debian.org/transitions/html/auto-hdf5.html > The current deadline for camitk package removal is 22 November. > > What do you think is

Re: autopkgtest regression: Segmentation fault

2018-11-16 Thread Paul Gevers
Hi On 16-11-18 11:08, Mattia Rizzolo wrote: > On Fri, Nov 16, 2018 at 07:28:21AM +0100, Emmanuel Promayon wrote: >> Thanks to the (great work) of Gert  on vtk7 and gdcm packages, version >> 7.1.1+dfsg1-9 of vtk7 and version 2.8.8-2 of gdcm are now both in testing. >> I sent a retry request for

Re: autopkgtest regression: Segmentation fault

2018-10-26 Thread Paul Gevers
Dear Emmanuel, [I didn't see your reply until ginggs notified me, bug submitters aren't automatically subscribed to the bug]. On Thu, 25 Oct 2018 07:56:17 +0200 Emmanuel Promayon wrote: > From the autopkgtest log [1], it seems that vtk6 is installed along > side vtk7. Yes, as a bystander,