From: Maxime Devos <maximedevos@telenet.be>
To: 56308@debbugs.gnu.org
Subject: bug#56308: Successful builds are stuck on ci.guix.gnu.org for 4.6 hours
Date: Wed, 29 Jun 2022 23:00:47 +0200 [thread overview]
Message-ID: <7b8d7375103d77b0c4b10e6c4678e3281c95ebb4.camel@telenet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
Hi,
Have a look at <https://ci.guix.gnu.org/workers> and take one of the
crates there, e.g.:
https://ci.guix.gnu.org/build/1054529/details
The current status is ‘started’, with duration 16844 seconds.
However, looking at the log:
https://ci.guix.gnu.org/build/1054529/log/raw
it took about 0.5 seconds (ignoring accumulated rounding errors) to
build, and the build is finished!
Something seems wrong there.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
reply other threads:[~2022-06-29 21:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b8d7375103d77b0c4b10e6c4678e3281c95ebb4.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=56308@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).