Closed microbit-carlos closed 7 months ago
I've pushed to this repo a branch which only builds CODAL with MakeCode using the PXT_COMPILE_SWITCHES=csv---mbcodal
env var: https://github.com/lancaster-university/codal-microbit-v2/commit/03d4996ea5d1edd50b56a03ea600f6d0ca0a475d
And that runs correctly, so the issue is isolated to the DAL/yotta build: https://github.com/lancaster-university/codal-microbit-v2/actions/runs/5282631485
Do we have a way forward for the deprecation of yotta? Otherwise this is just going to keep reappearing :(
The proposal is to replace it with CODAL-style CMake files and build.py, but in the meantime we'll need to to continue using Yotta with GitHub tokens, even if we have to renew it yearly.
@JohnVidler as the current branch will be tagged for MakeCode live, could you fix this issue before the tag (and restart the latest workflow run) so that we can get a CI build of MakeCode before tagging?
Okay, so the docker build will fail anyway due to https://github.com/microsoft/pxt-microbit/issues/5313, but the "local build" (nodocker
) in CI should still work to completion once this is fixed.
I've updated the token in this repo with a fine grained read-only token from my account. That fixes the issue building the "no docker" MakeCode build, but due to https://github.com/lancaster-university/codal-microbit-v2/issues/338 the "docker" build will fail, as the docker image is not available in Docker Hub.
As a temporary measure, to be able to tell if the nodocker
builds fail, I'll disable the build with docker until we can fetch the image from a public registry.
The docker image has been pushed to DockerHub and we can restore the MakeCode builds with Docker:
Currently the MakeCode CI builds are failing: https://github.com/lancaster-university/codal-microbit-v2/actions/workflows/makecode.yml
The error is not very descriptive:
However, they run correctly in my fork: https://github.com/microbit-carlos/codal-microbit-v2/actions/runs/5282488564
The only difference I can think of is the population of the
YOTTA_GITHUB_AUTHTOKEN
secret in the repo settings?