Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Builds broken in master branch (1.8.11)?! #616

Open
henrygab opened this issue Apr 1, 2021 · 6 comments
Open

Builds broken in master branch (1.8.11)?! #616

henrygab opened this issue Apr 1, 2021 · 6 comments

Comments

@henrygab
Copy link
Contributor

henrygab commented Apr 1, 2021

Is something misconfigured for the CI builds?

It appears that all PRs since December 24 have failed to build (via CI Actions).

On December 24th, three PRs (#3, #586, #588) were merged, and then the version was updated to 1.8.11. Each of those merges has failed the CI build (but logs are gone now).

Please fix so PRs can have some sanity checks applied, and be considered for merging again!

Potentially affected PRs include:

@facchinm
Copy link
Member

facchinm commented Apr 1, 2021

Hi @henrygab ,
there's a known incompatibility on branch 1.8.11+ with this library ( https://github.com/bxparks/AceTime ). The check has been added to avoid future breakages but until bxparks/AceTime#57 and #612 get merged the CI will be "broken" (as expected).
@per1234 do we have any solution beside manually checking the CI output to make sure only AceTime fails to compile?

@per1234
Copy link
Contributor

per1234 commented Apr 1, 2021

@facchinm unfortunately there is no established system in place for doing that. The compilation results are all recorded in a JSON file, so it could certainly be done.

I can make the manual checking less painful though. I am currently preparing a PR to disable the verbose output from the arduino/compile-sketches action. The verbose output is primarily intended to be used for troubleshooting the build process or action, and really doesn't offer any value for normal usage. Disabling the verbose output will significantly reduce the size of the log and make it easier for people to check for the cause of the failure.

@stonehippo
Copy link

@per1234 @facchinm any joy? It looks like now @bxparks is holding the PR on the AceTime side until 1.8.12 is released here? bxparks/AceTime#58

@facchinm
Copy link
Member

#597 needs to be fixed (and #622 merged) before releasing 1.8.12, but all the other pieces should be in place now.

@stonehippo
Copy link

Any progress?

@bxparks
Copy link
Contributor

bxparks commented Nov 4, 2021

I was going to create a PR to remove AceTime from the GH Workflow, but it was already done a few weeks ago:
96ce5f9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants