GNU bug report logs - #67431
nsq.powerpc64le-linux Testinflightworker test failure

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 67431 in the body.
You can then email your comments to 67431 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: bug-guix <bug-guix <at> gnu.org>
Subject: nsq.powerpc64le-linux Testinflightworker test failure
Date: Fri, 24 Nov 2023 08:48:59 -0500

Hello,

cuirass <at> gnu.org (Cuirass) writes:

> <p>The build <b>nsq.powerpc64le-linux</b> for specification <b>master</b> is broken. You
> can find the detailed information about this build <a
> href="https://ci.guix.gnu.org/build/2674716/details">here</a>.</p>
>
> https://ci.guix.gnu.org/build/2674716/details

Excerpt:

--8<---------------cut here---------------start------------->8---
=== RUN   TestInFlightWorker
    logger.go:16: INFO: nsqd v1.2.1 (built w/go1.17.13)
    logger.go:16: INFO: ID: 16
    logger.go:16: INFO: TOPIC(test_in_flight_worker1700827671): created
    logger.go:16: INFO: TOPIC(test_in_flight_worker1700827671): new channel(channel)
    logger.go:16: INFO: TCP: listening on 127.0.0.1:32843
    logger.go:16: INFO: NSQ: persisting topic/channel metadata to /tmp/guix-build-nsq-1.2.1.drv-0/nsq-test-3611268977/nsqd.dat
    logger.go:16: INFO: HTTP: listening on 127.0.0.1:45211
    assertions.go:13: [31mchannel_test.go:99:
        
        	   0 (expected)
        
        	!= 250 (actual)[39m
        
    logger.go:16: INFO: TCP: closing 127.0.0.1:32843
    logger.go:16: INFO: HTTP: closing 127.0.0.1:45211
    logger.go:16: INFO: NSQ: persisting topic/channel metadata to /tmp/guix-build-nsq-1.2.1.drv-0/nsq-test-3611268977/nsqd.dat
    logger.go:16: INFO: NSQ: persisting topic/channel metadata to /tmp/guix-build-nsq-1.2.1.drv-0/nsq-test-3611268977/nsqd.dat
    logger.go:16: INFO: NSQ: closing topics
    logger.go:16: INFO: TOPIC(test_in_flight_worker1700827671): closing
    logger.go:16: INFO: TOPIC(test_in_flight_worker1700827671): closing ... messagePump
    logger.go:16: INFO: CHANNEL(channel): closing
    logger.go:16: INFO: CHANNEL(channel): flushing 250 memory 0 in-flight 0 deferred messages to backend
    logger.go:16: INFO: DISKQUEUE(test_in_flight_worker1700827671:channel): writeOne() opened /tmp/guix-build-nsq-1.2.1.drv-0/nsq-test-3611268977/test_in_flight_worker1700827671:channel.diskqueue.000000.dat
    logger.go:16: INFO: DISKQUEUE(test_in_flight_worker1700827671:channel): readOne() opened /tmp/guix-build-nsq-1.2.1.drv-0/nsq-test-3611268977/test_in_flight_worker1700827671:channel.diskqueue.000000.dat
    logger.go:16: INFO: DISKQUEUE(test_in_flight_worker1700827671:channel): closing
    logger.go:16: INFO: DISKQUEUE(test_in_flight_worker1700827671:channel): closing ... ioLoop
    logger.go:16: INFO: DISKQUEUE(test_in_flight_worker1700827671): closing
    logger.go:16: INFO: DISKQUEUE(test_in_flight_worker1700827671): closing ... ioLoop
    logger.go:16: INFO: NSQ: stopping subsystems
    logger.go:16: INFO: LOOKUP: closing
    logger.go:16: INFO: QUEUESCAN: closing
    logger.go:16: INFO: NSQ: bye
--- FAIL: TestInFlightWorker (2.50s)
--8<---------------cut here---------------end--------------->8---

Cuirass says the new failure was a result from
https://git.savannah.gnu.org/cgit/guix.git/log/?qt=range&q=0083a2265960f8228112c36e0d10eb974ff9d1f1..e4397a32ac81d0b23b168df27424001a7d20aee7;
I suppose the test is flaky.

-- 
Thanks,
Maxim

Message #10 received at 67431-done <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 67431-done <at> debbugs.gnu.org
Subject: Re: bug#67431: nsq.powerpc64le-linux Testinflightworker test failure
Date: Fri, 24 Nov 2023 16:17:56 +0200

[Message part 1 (text/plain, inline)]

On Fri, Nov 24, 2023 at 08:48:59AM -0500, Maxim Cournoyer wrote:
> Hello,
> 
> cuirass <at> gnu.org (Cuirass) writes:
> 
> > <p>The build <b>nsq.powerpc64le-linux</b> for specification <b>master</b> is broken. You
> > can find the detailed information about this build <a
> > href="https://ci.guix.gnu.org/build/2674716/details">here</a>.</p>
> >
> > https://ci.guix.gnu.org/build/2674716/details
> 
> Excerpt:
<snip>
> 
> Cuirass says the new failure was a result from
> https://git.savannah.gnu.org/cgit/guix.git/log/?qt=range&q=0083a2265960f8228112c36e0d10eb974ff9d1f1..e4397a32ac81d0b23b168df27424001a7d20aee7;
> I suppose the test is flaky.
> 
> -- 
> Thanks,
> Maxim

I sent it through again and it passed the tests

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[signature.asc (application/pgp-signature, inline)]

Message #13 received at 67431-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 67431-done <at> debbugs.gnu.org
Subject: Re: bug#67431: nsq.powerpc64le-linux Testinflightworker test failure
Date: Thu, 30 Nov 2023 08:04:14 -0500

Hi Efraim,

Efraim Flashner <efraim <at> flashner.co.il> writes:

> On Fri, Nov 24, 2023 at 08:48:59AM -0500, Maxim Cournoyer wrote:
>> Hello,
>> 
>> cuirass <at> gnu.org (Cuirass) writes:
>> 
>> > <p>The build <b>nsq.powerpc64le-linux</b> for specification <b>master</b> is broken. You
>> > can find the detailed information about this build <a
>> > href="https://ci.guix.gnu.org/build/2674716/details">here</a>.</p>
>> >
>> > https://ci.guix.gnu.org/build/2674716/details
>> 
>> Excerpt:
> <snip>
>> 
>> Cuirass says the new failure was a result from
>> https://git.savannah.gnu.org/cgit/guix.git/log/?qt=range&q=0083a2265960f8228112c36e0d10eb974ff9d1f1..e4397a32ac81d0b23b168df27424001a7d20aee7;
>> I suppose the test is flaky.
>> 
>> -- 
>> Thanks,
>> Maxim
>
> I sent it through again and it passed the tests

OK!  Ideally we'd re-run the build locally many times to try to
reproduce the failure, and report that upstream while disabling the
unstable test.

-- 
Thanks,
Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.