Skip to content

CI

CI #1561

Triggered via schedule April 7, 2026 03:00
Status Failure
Total duration 1m 2s
Artifacts

gnu-data.yml

on: schedule
Process the GNU test results
58s
Process the GNU test results
Process the BFS test results
53s
Process the BFS test results
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Process the BFS test results
Error: To https://github.com/uutils/findutils-tracking ! refs/heads/main:refs/heads/main [rejected] (fetch first) Done Pushing to https://github.com/uutils/findutils-tracking POST git-receive-pack (57 bytes) error: failed to push some refs to 'https://github.com/uutils/findutils-tracking' hint: Updates were rejected because the remote contains work that you do not hint: have locally. This is usually caused by another repository pushing to hint: the same ref. If you want to integrate the remote changes, use hint: 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.
Process the BFS test results
Error: To https://github.com/uutils/findutils-tracking ! refs/heads/main:refs/heads/main [rejected] (fetch first) Done Pushing to https://github.com/uutils/findutils-tracking POST git-receive-pack (57 bytes) error: failed to push some refs to 'https://github.com/uutils/findutils-tracking' hint: Updates were rejected because the remote contains work that you do not hint: have locally. This is usually caused by another repository pushing to hint: the same ref. If you want to integrate the remote changes, use hint: 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.
Process the GNU test results
Error: fatal: pathspec 'gnu-results.png' did not match any files
Process the BFS test results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dawidd6/action-download-artifact@v3, EndBug/add-and-commit@v9.1.4. 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/
Process the GNU test results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dawidd6/action-download-artifact@v3, EndBug/add-and-commit@v9.1.4. 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/