From: zimoun <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: ‘core-updates-frozen’: julia status
Date: Thu, 25 Nov 2021 03:13:53 +0100 [thread overview]
Message-ID: <86fsrlrnha.fsf@gmail.com> (raw)
In-Reply-To: <87fsroaqzv.fsf@gmail.com>
Hi,
On Mon, 22 Nov 2021 at 15:13, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>> Julia is annoying, Because the test suite sometimes passes, sometimes
>> not. Well, I am not even sure it is the same part that fails. I
>> notice that "guix build julia --without-tests=julia" then "guix build
>> julia" tends to works. :-)
>>
>> Any idea to debug this?
>
> No idea how to debug this, but when faced with nondeterministic tests,
> here's how I proceed:
>
> 1. Report them upstream.
> 2. Disable the problematic tests. You may need to disable a whole test suite of
> similarly faulted tests, if they all behave the same.
After this hacking day, Julia builds deterministically* on
core-updates-frozen. Along the way, now the test suite runs in parallel
which reduces a lot the feedback loop. :-) And a variant of the current
patch of julia source is upstream PR.
*deterministically: at least on 2 machines. ;-)
One or two failing tests randomly failing should be investigated and
probably reported upstream.
The test suite of julia-* packages supports also (more or less) some
parallelism. From my understanding, the limitation comes from the
script 'test/runtests.jl' from each package; each implements more or
less some parallelism. Now, the environment variable JULIA_CPU_THREADS
is set but Julia does not always honor it as its doc specifies – see the
patch fixing the parallelism of Julia test suite ;-). Therefore, the
test suite of each package is launched with
'--procs=(parallel-job-count)' and Julia exploits at best the available
workers.
I am currently rebuilding all the julia-* packages. It is high probable
some are now broken. But it appears to me not a blocker for the merge.
On a side note, Julia is not currently reproducible [1] and
'julia-build-system' neither [2]. Therefore, probable non-reproducible
build introduced by parallelism is currently not the point, IMHO.
Thanks Maxim for the help and the good vibes to tackle that.
Cheers,
simon
1: <http://issues.guix.gnu.org/issue/22304>
2: <http://issues.guix.gnu.org/issue/47354>
next prev parent reply other threads:[~2021-11-25 2:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 11:46 Thursday 18th: ‘core-updates-frozen’ sprint! Ludovic Courtès
2021-11-17 12:06 ` Ricardo Wurmus
2021-11-19 15:01 ` Ludovic Courtès
2021-11-19 23:43 ` Ricardo Wurmus
2021-11-22 13:19 ` Ludovic Courtès
2021-11-22 13:36 ` zimoun
2021-11-22 20:13 ` Maxim Cournoyer
2021-11-24 11:07 ` zimoun
2021-11-25 2:13 ` zimoun [this message]
2021-11-25 23:49 ` ‘core-updates-frozen’: julia status update zimoun
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=86fsrlrnha.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.