From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Eric Bavier <bavier@posteo.net>
Cc: 72877-done@debbugs.gnu.org, Andreas Enge <andreas@enge.fr>,
Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: [bug#72877] [PATCH 0/8] Upgrade PETSc, SLEPc, SUNDIALS, and DealII
Date: Thu, 05 Sep 2024 16:40:44 +0200 [thread overview]
Message-ID: <87a5gm6u4z.fsf@inria.fr> (raw)
In-Reply-To: <692205d6c164d7e3e339068c65a43db4@posteo.net> (Eric Bavier's message of "Thu, 05 Sep 2024 13:07:25 +0000")
Hi Eric,
Thanks for taking the time to look into it. (I rushed the patch series
more than usual because the whole stack was broken since the
‘core-updates’ merge.)
Eric Bavier <bavier@posteo.net> skribis:
> I finally got a chance to look through it just before you pushed. My
> only
> note is that I noticed this in the output of petsc's "check" phase:
>
> # -------------
> # Summary
> # -------------
> # FAILED vec_pf_impls_string_tests-ex1_1 diff-snes_tutorials-ex78_2
> # success 5721/10154 tests (56.3%)
> # failed 2/10154 tests (0.0%)
> # todo 240/10154 tests (2.4%)
> # skip 4191/10154 tests (41.3%)
>
> but the 'check' phase doesn't fail. I wonder if the `make check`
> invocation does not return a failure code when the tests fail. These
> test failures
> in particular look mostly harmless, but maybe other more catastrophic
> failures
> might not be caught if `check` is not detecting failures.
Oh. I was told in the meantime that we might want to use ‘make test’
instead, so perhaps we should followup on this update with a switch to
‘make test’ and see if problems as shown above still appear:
https://gitlab.com/petsc/petsc/-/issues/1634#note_2070200322
Ludo’.
prev parent reply other threads:[~2024-09-05 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 15:38 [bug#72877] [PATCH 0/8] Upgrade PETSc, SLEPc, SUNDIALS, and DealII Ludovic Courtès
2024-08-29 15:39 ` [bug#72877] [PATCH 1/8] gnu: petsc: Update to 3.21.4 Ludovic Courtès
2024-08-29 15:39 ` [bug#72877] [PATCH 2/8] gnu: python-petsc4py: " Ludovic Courtès
2024-08-29 15:39 ` [bug#72877] [PATCH 3/8] gnu: slepc: Update to 3.21.1 Ludovic Courtès
2024-08-29 15:39 ` [bug#72877] [PATCH 4/8] gnu: python-slepc4py: " Ludovic Courtès
2024-08-29 15:39 ` [bug#72877] [PATCH 5/8] gnu: petsc: Make ‘petscvariables’ reproducible Ludovic Courtès
2024-08-29 15:39 ` [bug#72877] [PATCH 6/8] gnu: sundials: Upgrade to 7.1.1 Ludovic Courtès
2024-08-29 15:39 ` [bug#72877] [PATCH 7/8] gnu: sundials, sundials-openmpi: Use gexps Ludovic Courtès
2024-08-29 15:39 ` [bug#72877] [PATCH 8/8] gnu: dealii: Update to 9.6.0 Ludovic Courtès
2024-09-05 8:17 ` bug#72877: [PATCH 0/8] Upgrade PETSc, SLEPc, SUNDIALS, and DealII Ludovic Courtès
2024-09-05 13:07 ` [bug#72877] " Eric Bavier
2024-09-05 14:40 ` Ludovic Courtès [this message]
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=87a5gm6u4z.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=72877-done@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=bavier@posteo.net \
--cc=sharlatanus@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.