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

tests/integration: install libzstd-devel #586

Merged
merged 2 commits into from
Jun 5, 2024

Conversation

@github-actions github-actions bot added the area/install Issues related to `bootc install` label Jun 5, 2024
Signed-off-by: John Eckersberg <jeckersb@redhat.com>
@jeckersb jeckersb changed the title integration zstd tests/integration: install libzstd-devel Jun 5, 2024
@jmarrero
Copy link
Member

jmarrero commented Jun 5, 2024

lgtm
however can you add to the description what this fixes or preps for?

@cgwalters
Copy link
Collaborator

This also relates to 0455f80 - in chatting with @henrywang I was hoping that we could rework the integration tests to always start from our hack/Containerfile to get closer to a single source of truth for the build starting point.

@jeckersb
Copy link
Contributor Author

jeckersb commented Jun 5, 2024

@cgwalters
Copy link
Collaborator

I think it's because the framework is passing --resultsdir to mock, but the test harness isn't picking up the files written there.

@cgwalters
Copy link
Collaborator

I'm not sure; maybe it's somehow a flake. I tried restarting the jobs.

@cgwalters
Copy link
Collaborator

It's also possible that this was actually broken by #581 - I think I ended up merging without those jobs being run because they were running for over 2 hours and we had a big TF backlog.

@jeckersb
Copy link
Contributor Author

jeckersb commented Jun 5, 2024

Ah I think we need to update the buildrequires from the spec in contrib/, testing that now locally to see if that's sufficient.

Signed-off-by: John Eckersberg <jeckersb@redhat.com>
@jeckersb
Copy link
Contributor Author

jeckersb commented Jun 5, 2024

Ah I think we need to update the buildrequires from the spec in contrib/, testing that now locally to see if that's sufficient.

Seems to fix it for me locally, added a new commit with that, we'll see how it shakes out in CI

@cgwalters
Copy link
Collaborator

Ah right. Hmm...I might lean a bit towards always fetching the spec from fedora instead. This is a classic problem with specs/dpkg/arch etc in upstream, it just bitrots as it's not canonical.

(Actually though, in theory in Fedora we could make use of the "dynamic buildrequires" stuff to auto-determine from our source external dependencies we have, but not worth doing right now)

@cgwalters
Copy link
Collaborator

It's actually kind of tempting to change ostree-ext to also just support forking off /usr/bin/zstd, I don't have any problem with taking a hard dep on it...

@jeckersb
Copy link
Contributor Author

jeckersb commented Jun 5, 2024

Now it looks like quay issues:
Error: authenticating creds for "quay.io": received unexpected HTTP status: 504 Gateway Time-out

@cgwalters
Copy link
Collaborator

I guess let's give the other jobs a little bit more time to see if they get farther. But if not, we can just merge over red for those too.

@cgwalters
Copy link
Collaborator

Ooh no it looks like #581 did break more things:

[31mERROR[0m Installing to filesystem: Verifying fetch: Creating importer: Conflicting authentication options

@cgwalters
Copy link
Collaborator

@cgwalters cgwalters merged commit 2ea13a4 into containers:main Jun 5, 2024
8 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to `bootc install`
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants