From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guix-devel@gnu.org
Subject: Re: Offloading problems on berlin
Date: Fri, 17 Mar 2023 12:35:19 -0400 [thread overview]
Message-ID: <877cvf5oag.fsf@gmail.com> (raw)
In-Reply-To: <ZBN+xXuzyVBh6wRO@jurong> (Andreas Enge's message of "Thu, 16 Mar 2023 21:40:37 +0100")
Hi Andreas,
Andreas Enge <andreas@enge.fr> writes:
> Am Thu, Mar 16, 2023 at 02:50:53PM +0100 schrieb Ludovic Courtès:
>> There’s a problem with offloading on berlin:
>> https://issues.guix.gnu.org/61839
>> I occasionally offload from my laptop to machines at work but didn’t hit
>> this bug, so we’ll have to see if it’s specific to berlin or not.
>
> Thanks for pointing out that it is a known issue!
> Is there a commandline program that can be used like gkrellm to check
> whether data is flowing out of berlin to the build node?
Just clarifying, it is *not* currently known issue outside of Berlin.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-03-17 16:35 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 14:58 State of core-updates Andreas Enge
2023-03-10 18:24 ` Christopher Baines
2023-03-12 11:21 ` Andreas Enge
2023-03-10 18:55 ` Josselin Poiret
2023-03-11 12:16 ` Andreas Enge
2023-03-13 14:14 ` Simon Tournier
2023-03-14 20:43 ` Andreas Enge
2023-04-03 15:15 ` Simon Tournier
2023-03-14 9:27 ` Roman Scherer
2023-03-14 10:32 ` Josselin Poiret
2023-03-14 11:20 ` Roman Scherer
2023-03-14 15:50 ` Maxim Cournoyer
2023-03-14 18:02 ` Andreas Enge
2023-03-15 0:56 ` Maxim Cournoyer
2023-03-15 7:54 ` Andreas Enge
2023-03-15 11:33 ` Efraim Flashner
2023-03-15 13:35 ` Andreas Enge
2023-03-15 13:35 ` Maxim Cournoyer
2023-03-15 13:27 ` Maxim Cournoyer
2023-03-15 16:34 ` Notes from the Guix Days Ludovic Courtès
2023-03-15 18:21 ` Pjotr Prins
2023-03-17 15:07 ` Maxim Cournoyer
2023-04-11 14:05 ` Debugging Guix beyond pk (was Re: Notes from the Guix Days) Simon Tournier
2023-04-11 18:32 ` Maxim Cournoyer
2023-03-15 13:33 ` State of core-updates Andreas Enge
2023-03-15 14:56 ` Andreas Enge
2023-03-15 17:59 ` Kaelyn
2023-03-17 20:01 ` Andreas Enge
2023-03-17 20:17 ` Kaelyn
2023-03-17 20:27 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-17 20:43 ` Kaelyn
2023-03-18 8:56 ` Andreas Enge
2023-03-18 16:36 ` Kaelyn
2023-03-18 17:31 ` Andreas Enge
2023-03-18 9:39 ` Andreas Enge
2023-03-15 19:20 ` Felix Lechner
2023-03-17 16:40 ` Maxim Cournoyer
2023-03-16 13:50 ` Offloading problems on berlin Ludovic Courtès
2023-03-16 20:40 ` Andreas Enge
2023-03-16 20:55 ` Andreas Enge
2023-03-22 14:16 ` Ludovic Courtès
2023-03-16 21:25 ` Kaelyn
2023-03-17 12:15 ` Andreas Enge
2023-03-17 16:35 ` Maxim Cournoyer [this message]
2023-03-16 9:33 ` State of core-updates Björn Höfling
2023-03-16 10:05 ` Andreas Enge
2023-03-15 16:47 ` Building more of ‘core-updates’ on ci.guix Ludovic Courtès
2023-03-18 15:31 ` Andreas Enge
2023-03-22 14:32 ` Ludovic Courtès
2023-03-30 9:20 ` Andreas Enge
2023-03-30 11:21 ` Andreas Enge
2023-03-31 8:54 ` Andreas Enge
2023-04-07 13:22 ` Andreas Enge
2023-04-08 10:28 ` Josselin Poiret
2023-04-10 15:49 ` core-updates sprint (was: Building more of ‘core-updates’ on ci.guix) Andreas Enge
2023-04-11 14:47 ` Building more of ‘core-updates’ on ci.guix Simon Tournier
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=877cvf5oag.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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).