I think the label defaults.run.working-directory sets the default only for run steps, [like in GitHub Actions](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-ac…
I have no OS package (vis OpenSUSE Tumbleweed) access to a later version of cargo.
rpm -qf /usr/bin/cargo rustup-1.28.1~0-1.1.x86_64
My impression is that rustup is a…
Your prediction is correct. So what's the response?
Since these messages crossed: see above.
I'd love to hear thoughts on how we can make things at least let you know that you need to change/update versions of things
Since the error is coming from Sycamore, it…
I'm now confident that this is a Rust version issue. A helpful Redditor announced that the…
That's odd!
- Which test is this happening in?
- Do you get a similar "lint reasons are experimental" warning when you call
cargo buildortrunk build? - What do you get when you call…
And yes either way please get the "local testing" working. It's OK with me if the local testing doesn't go through forgejo-runner; perhaps the forgejo-runner jobs invoke the local testing script…
Yes, [the examples] are tests too!
I've now configured the examples to run as tests using Cargo's target selection…
Now you need to push some additional commit and see if the jobs re-run on their own
I'm going to try to address #76 in this pull request, so we should have plenty more commits to test that with.
If you trust an organization and the image is open-souce licensed, feel free to check in a use of it.
Would it matter if the image weren't open-source licensed? We're just using it as a tool,…
Hmm, the issue seems now to be that image
rust:1.85-bookwormdoes not have node installed, see the details below.
Okay, that's what I'd expect. Let's set aside the…
Before you upgrade to a t3a.medium instance, let's try something completely different. The latest commit (4251242953) runs CI on a stock Docker image, getting rid of the setup-image step. On…
Now that we've installed Node 20 on the runner host, the setup-image job can run! Unfortunately, building the CI image seems to crash the host by eating up its entire 2GB of RAM.
I just…