Hi Guix,

  There is an usual currently ongoing effort towards updating
  hpc-related packages in a dedicated branch [0]. A ci jobset has
  dictated its verdict [1]. Even if hpc specific, I think this is an
  interesting exercise for most teams.

  When trying to understand and fix the failures, I observe three
  different cases:

  - failures I’m unable to reproduce [2], as these build in two
    different machines for me, which makes them hard to debug
  - failures due to dependencies [3], except all dependencies build, so
    no log is available
  - remaining failures, but I ignore if these are a consequence of
    changes in the branch, or pre-existing failures

  Ci is a great tool, and more than useful, once you get used to its
  intrinsics. Any tip helping to understand what’s going on here would
  help to move forward, and will probably apply to all other testing
  branches and jobsets.

  Thanks in advance !

[0] https://codeberg.org/guix/guix/commits/branch/hpc-team
[1] https://ci.guix.gnu.org/eval/2127972?status=failed
[2] https://ci.guix.gnu.org/build/17484247/details
[3] https://ci.guix.gnu.org/build/17483015/details

ps. Still with me ? Consider joining the team, HPC is a really
interesting and rewarding domain where Guix shines, but also a broad
field where more eyes would be more than helpful !

--
Cayetano Santos
.
gpg: CCB8 1842 F9D7 058E CD67 377A BF5C DF4D F6BF 6682
key: meta.sr.ht/~csantosb.pgp

Attachment: signature.asc
Description: PGP signature

Reply via email to