-
Notifications
You must be signed in to change notification settings - Fork 187
Teach mantle/kola how to automatically find cosa builds #1259
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
Conversation
arithx
left a comment
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.
Last commit makes sense to me.
|
A follow on to this per the first para of git commit msg is to |
jlebon
left a comment
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.
Yup, makes sense to me overall to start making mantle more cosa-aware.
|
/lgtm |
|
The CI run here is stuck in emergency mode...looks like we have an old coreos-installer for some reason? And we really need something like coreos/ignition-dracut#146 so we can consistently detect this and error out fast. |
Looks like a test flake. |
|
Hmm...I don't think this should be racy (though it's possible). Without trying to reproduce locally my current guess is this has something to do with us implicitly changing from absolute paths to relative |
|
/lgtm |
|
/hold |
|
OK I logged into the pod live and: Somehow we're missing everything except the ostree? |
|
Heh, from the clitests: So that's definitely racing. |
The current `mantle/cosa` directory is a bit circular, we basically have `cosa/mantle/cosa` then. It made sense before the projects were merged but less so now I think. Second, the `mantle/cosa/builds.go` is really about the `meta.json` file but we also need the *directory* for a build. What's going on in kola is quite weird because we basically need to keep around the pair of (directory, parsed meta). Enhance the `mantle/sdk` to learn about a `LocalBuild` struct and teach kola how to use it to synthesize the other two if `.` looks like a coreos-assembler root. This drains more logic from `cmd-kola` in cosa, trending towards removing it!
|
And hooray, passing tests now. |
|
Ahh, nice catch! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arithx, cgwalters, jlebon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold cancel |
|
Any chance this is the source of our kola aws tests starting to "fail": coreos/fedora-coreos-pipeline#215 |
|
|
|
Follow up to this here: #1283 |
The current
mantle/cosadirectory is a bit circular, webasically have
cosa/mantle/cosathen. It made sense beforethe projects were merged but less so now I think.
Second, the
mantle/cosa/builds.gois really about themeta.jsonfile but we also need the directory for a build. What's
going on in kola is quite weird because we basically need
to keep around the pair of (directory, parsed meta).
Enhance the
mantle/sdkto learn about aLocalBuildstructand teach kola how to use it to synthesize the other two if
.looks like a coreos-assembler root.This drains more logic from
cmd-kolain cosa, trendingtowards removing it!