From: Demi Marie Obenour <demiobenour@gmail.com>
To: Alyssa Ross <hi@alyssa.is>, Yureka Lilian <yureka@cyberchaos.dev>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 2/2] lib/nixpkgs.default.nix: update to staging-next
Date: Sun, 26 Oct 2025 05:18:06 -0400 [thread overview]
Message-ID: <f52c1aa7-96c0-462b-9287-0dbbae037e4f@gmail.com> (raw)
In-Reply-To: <87ldky3u7i.fsf@alyssa.is>
[-- Attachment #1.1.1: Type: text/plain, Size: 821 bytes --]
On 10/26/25 05:09, Alyssa Ross wrote:
> Yureka Lilian <yureka@cyberchaos.dev> writes:
>
>> Signed-off-by: Yureka Lilian <yureka@cyberchaos.dev>
>> ---
>> lib/nixpkgs.default.nix | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> I'm seeing a timeout in the networking test in
> release/checks/integration with this patch applied. I'll try bisecting,
> but I get the impression you might have the resources to be able to do
> that faster, if you want to try to beat me.
I wonder if this is not a new bug, but rather a pre-existing race
being exposed. I have run into this before on x86.
I think it would be better to actually figure out what is happening.
One option would be allow the person running the tests to break into
a shell.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-26 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-12 22:27 [PATCH 1/2] vm/sys/net: build against pkgsMusl Yureka Lilian
2025-10-12 22:27 ` [PATCH 2/2] lib/nixpkgs.default.nix: update to staging-next Yureka Lilian
2025-10-21 16:00 ` Alyssa Ross
2025-10-26 9:09 ` Alyssa Ross
2025-10-26 9:18 ` Demi Marie Obenour [this message]
2025-10-26 9:24 ` Alyssa Ross
2025-10-29 20:05 ` Alyssa Ross
2025-10-31 11:17 ` Alyssa Ross
2025-10-31 11:17 ` [PATCH 1/2] vm/sys/net: build against pkgsMusl Alyssa Ross
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f52c1aa7-96c0-462b-9287-0dbbae037e4f@gmail.com \
--to=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
--cc=hi@alyssa.is \
--cc=yureka@cyberchaos.dev \
/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://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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 NNTP newsgroup(s).