-
Notifications
You must be signed in to change notification settings - Fork 140
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
[FEATURE] Get well plan for the Github CI pipeline #3168
[FEATURE] Get well plan for the Github CI pipeline #3168
Comments
Thanks @andy-k-improving - it sounds like we have a plan !! |
Seems to be related: actions/checkout#1590, actions/checkout#1809 |
The error seems to happen after 8b2d01e, but I don't think it's related to the code change itself, it's more about |
Similar fix applied on Job-scheduler and it's working. |
bwc seems to be broken also: This will be the next item to fix. |
@YANG-DB Can you re-open this, as |
I tried to reproduce the bwc-test locally on Mac, however the Gradle build script script looks for the @YANG-DB Wonder have you seen this issue before?
|
Unfortunately no |
Thx for the quick reply. If that is the case, I will put this on hold, as I don't a Linux || Ubuntu machine handy, and the amount of time to make the |
If others would be able to run |
Is your feature request related to a problem?
At the moment, the CI build for the project is broken, and PR patch being merged regardless of the CI build result.
This brings additional risk to the project, because there may be additional failure that a particular patch introduced, but being ignored by both Dev and reviewer, due to the fact that build is always failing on the
main
branch.What solution would you like?
Existing CI errors with corresponded fix:
What alternatives have you considered?
N/A
Do you have any additional context?
The text was updated successfully, but these errors were encountered: