-
Notifications
You must be signed in to change notification settings - Fork 15
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
Clean up filename and required ignition version templates #40
Clean up filename and required ignition version templates #40
Conversation
Hey @paul-griffith. Is this PR still alive? I can review if needed. And get a clean build; looks like the logs are gone. |
Haven't touched it in a long time, obviously, but I think the changes are still valid. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to see if I can manually kick off the GH workflow again to find out why it failed the last time.
Co-authored-by: Brian Ray <brianeray@users.noreply.github.com>
Co-authored-by: Brian Ray <brianeray@users.noreply.github.com>
I don't have privileges to override the checks failure and merge, which is what I would do since these aren't code changes. I might need to bug the |
@brianeray Just stumbled across this. Can you explain to me in simple terms why it's okay to merge with a failed build? Thanks! |
No. Looking at this again, especially this,
This thing should pass a PR build first. |
The old PR GH Actions failures are a mystery, because their logs are gone. Trying to trigger another run to capture the actual failure.
OK I finally tricked it into rebuilding and giving us good output. I've downloaded the failed Gradle log and finally have something to go on. Stay tuned. |
For internal tracking: IGN-10603. |
@paul-griffith I think I figured it out. It's coming from the current PR. Try this.
I'm having problems getting unit tests to pass even after that patch due to Gradle-Windows fighting, but am pretty sure this squashes the thing that is tanking most of the unit tests. This is the kind of test failure up in that build log over and over and over.
|
OK this is better; I'm not going to run the whole suite locally but it gives confidence in the
|
Replaced by #58--just to make it easier for me to grind away at the unit test failures and take this off of Paul's plate. |
Fixes #37
Fixes #38