Skip to content

Nightly Build (by @ClaasRostock) #416

Nightly Build (by @ClaasRostock)

Nightly Build (by @ClaasRostock) #416

Triggered via schedule May 12, 2026 06:26
Status Success
Total duration 3m 5s
Artifacts 1

nightly_build.yml

on: schedule
Matrix: test / test
Matrix: test_future / test315
build_package  /  Build source distribution
20s
build_package / Build source distribution
build_and_publish_documentation  /  Build and publish documentation
30s
build_and_publish_documentation / Build and publish documentation
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 3 warnings, and 5 notices
test_future / Test on 3.15.0-alpha - 3.15.0-ubuntu-latest (experimental)
Process completed with exit code 2.
test_future / Test on 3.15.0-alpha - 3.15.0-windows-latest (experimental)
Process completed with exit code 1.
build_package / Build source distribution
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_and_publish_documentation / Build and publish documentation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: peaceiris/actions-gh-pages@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_and_publish_documentation / Build and publish documentation
Lexing literal_block 'class <basic-model>_FMU(Model, <basic-model>):\n def __init__(self, <basic_model_args, **kwargs):\n Model.__init__(self,name,description,author,version, kwargs)\n <basic-model>.__init__(<basic-model-args>)' as "Python" resulted in an error at token: '<'. Retrying in relaxed mode. [misc.highlighting_failure]
test_future / Test on 3.15.0-alpha - 3.15.0-windows-latest (experimental)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
test / Test on 3.14-windows-latest
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
test / Test on 3.13-windows-latest
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
test / Test on 3.11-windows-latest
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
test / Test on 3.12-windows-latest
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
artifact Expired
313 KB
sha256:c7b47983b4b32deb2c8a0a0a7e1afc0daa492a05084916b0e2fe068af5b46f28