{tools}[foss/2024a,foss/2025a,foss/2025b] jupyterview v0.8.0, jupyterlab-h5web v12.6.1, JupyterLab-git v0.51.4, hatch-nodejs-build v1.1.1, meshio v5.3.5#25256
Conversation
…0-foss-2025a.eb, jupyterview-0.8.0-foss-2025b.eb, jupyterlab-h5web-12.6.1-foss-2024a.eb, jupyterlab-h5web-12.6.1-foss-2025a.eb, jupyterlab-h5web-12.6.1-foss-2025b.eb, JupyterLab-git-0.51.4-GCCcore-14.2.0.eb, JupyterLab-git-0.51.4-GCCcore-14.3.0.eb, hatch-nodejs-build-1.1.1-GCCcore-13.3.0.eb, hatch-nodejs-build-1.1.1-GCCcore-14.2.0.eb, hatch-nodejs-build-1.1.1-GCCcore-14.3.0.eb, meshio-5.3.5-foss-2024a.eb, meshio-5.3.5-foss-2025a.eb, meshio-5.3.5-foss-2025b.eb
Updated software
|
|
Test report by @Micket |
|
Need to remember what to fix in the CI to allow for use of newer hatchling in hatch-nodejs-build. There is nothing wrong with this PR, it's just the CI that should stop complaining |
|
Test report by @Micket |
|
@boegelbot please test @ jsc-zen3 |
|
@Micket: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3913434179 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Test report by @boegel |
|
Going in, thanks @Micket! |
(created using
eb --new-pr)