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

Snap not building - fixed issue #37

Merged
merged 21 commits into from
Nov 25, 2023
Merged

Snap not building - fixed issue #37

merged 21 commits into from
Nov 25, 2023

Conversation

kz6fittycent
Copy link
Contributor

@kz6fittycent
Copy link
Contributor Author

stand by - I see my error...

@kz6fittycent
Copy link
Contributor Author

That's more like it!

Implementing test builds on `testing` branch. Makes far more sense.
@kz6fittycent
Copy link
Contributor Author

Let me know if there's anything else needed. It's passing builds from my end and I have the locally built snap running in my home network.

Just in case there were any more errors from snapcraft.io.
last commit no good.
Included naming conventions, as build seemed to work in commit: kz6fittycent@a2e4c60
apparently the new naming convention isn't working. Reverted to older one from core20.
@kz6fittycent
Copy link
Contributor Author

kz6fittycent commented Nov 13, 2023

Not sure why, but the test builds are passing in my repo. I just merged a core22 based version into my master branch, and it's passing. AFAICT, we have the same GH actions.

EDIT: I just confirmed that they (the workflow yml's) are, in fact, the same. So I am puzzled why the test builds are failing in this repo, versus mine. That said, I am currently running the latest version of Jenkins, built locally.

EDIT AGAIN: OK, I am not so happy with these test builds! They seem to be hit or miss, leading me to believe that we were good to go. I've added a cleanup section to the bottom of the yaml, and that seems to be working in BOTH my branches (master and testing).

Added cleanup section - used in mc-installer. I'm at a loss after this. The failed tests seem to be hit/miss and that makes no sense to me. Whatever, here we go!
I'm reverting back to core20 since the testing branch is working as expected, and no failures. 

If this doesn't work, I am done and closing the PR.
Test builds are failing randomly. I am not certain the checks are legitimate. If it's failing on nearly 50%, what does that say about the 50% that are passing? I'm done troubleshooting it.
@kz6fittycent
Copy link
Contributor Author

@merlijn-sebrechts - if you (or another party) don't mind taking another look at this PR, I think it's ready. I say that with some reservation given the experiences I've had with the ~50/50 build failure/success rate. The latest commit is working and I've even upgraded to core22. I apologize for the noise from this PR, but it was fairly frustrating to see the difference in outcomes from our two repos.

Copy link
Member

@merlijn-sebrechts merlijn-sebrechts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

I'm assuming the weird issues were because we're running snapcraft review-tools after the build, and you might not be doing that. Snapcraft review-tools is what the store runs before publishing your snap, so all snaps must pass this automated review.

@merlijn-sebrechts merlijn-sebrechts merged commit b98436d into snapcrafters:master Nov 25, 2023
1 check passed
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

Successfully merging this pull request may close these issues.

None yet

2 participants