You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
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?
@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.
Activity
facchinm commentedon 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 commentedon 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-sketchesaction. 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 commentedon Apr 12, 2021
@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 commentedon Apr 12, 2021
#597 needs to be fixed (and #622 merged) before releasing 1.8.12, but all the other pieces should be in place now.
stonehippo commentedon May 25, 2021
Any progress?
bxparks commentedon 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