deploySite task in github workflow failing

[another_commander]

We seem to have an issue with the auto-build script on github. Earlier tooday I updated the code on master and the build failed. That was because we were using a recently deprecated upload-artifact action. After fixing that, the workflow run again but although a pre-release was successfully created, the build was still reported as failing. This is the output of the deploySite task, which was the point of failure:

Code: Select all

Run actions/deploy-pages@v2
  with:
    token: ***
    timeout: 600000
    error_count: 10
    reporting_interval: 5000
    artifact_name: github-pages
    preview: false
Artifact exchange URL: https://pipelinesghubeus24.actions.githubusercontent.com/yOkN68OsvTXlm3slYtE6HCHMi8FrQcLpFlh55gIeh5iUhX4PxO/_apis/pipelines/workflows/14112224591/artifacts?api-version=6.0-preview
Error: Getting signed artifact URL failed
Error: HttpError: Cannot find any run with github.run_id 14112224591.
    at processRuntimeResponse (/home/runner/work/_actions/actions/deploy-pages/v2/src/internal/api-client.js:48:1)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at getSignedArtifactMetadata (/home/runner/work/_actions/actions/deploy-pages/v2/src/internal/api-client.js:82:1)
    at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v2/src/internal/deployment.js:68:1)
    at main (/home/runner/work/_actions/actions/deploy-pages/v2/src/index.js:30:1)
Error: Error: Failed to create deployment (status: 404) with build version ca04e6454be56bc6c11c4e29b9ccd493c3b3a92a. Ensure GitHub Pages has been enabled: https://github.com/OoliteProject/oolite/settings/pages

In order to fix it I had to completely disable the deploySite action, I am not sure what the issue is here. Not a huge deal, as the action is just about uploading the doxygen output to a website, but it would be nice to get it back if we could. Any input resulting in a proper fix would be much appreciated.

Thankfully the nightly builds continue to be generated properly so the latest one contains the most recent code changes (the -nodust cmd line option, that is).

[MrFlibble]

Any input resulting in a proper fix would be much appreciated.

I bounced off this a little on my 'linux library bundle fix' fork, and mostly ignored it, as it was not my main focus.

Will have a look, maybe later today as github are due to deprecate an Ubuntu release, and I hope to make a fork of latest release available at that older version, for those nursing old nVidia cards with proprietary drivers etc.

Re: My fork. When the dust settles, and as we have to go to the next Ubuntu up, I'll try to work out a less manual way to bundle the libraries and do a PR. It's pretty much just updated linux-dependencies. It'd be quite sweet to do a 'fixed' version of 1.90 for current distros, unless consensus is that it's near time to settle a 1.92 as stable.

[Cholmondely]

Was moving to GitHub something which is now proving to be a mistake (with their now relentless drive to update everything which moves)?

[another_commander]

Absolutely not, it was the right move.

[MrFlibble]

Was moving to GitHub something which is now proving to be a mistake (with their now relentless drive to update everything which moves)?

I agree with a_c.

The apparent 'relentless drive' is not so bad really. They tend to keep runners available until their proper end of life.

So the Ubuntu 20.04 github runner will be fully retired this coming Tuesday. The same day that Ubuntu cease maintenance updates for it. Any releases built with it may remain available.

There's nothing to prevent us from building binaries on older or more obscure platforms at home, then uploading them to the Github release... where there' any real point. I'll do that occasionally with Starter for older MacOS versions.