test: Add API test for partial pull with pullProgress flag#28713
test: Add API test for partial pull with pullProgress flag#28713simek-m wants to merge 2 commits into
Conversation
mtrmac
left a comment
There was a problem hiding this comment.
Without vendoring the updated c/image this does not show that the new c/image passes…
… which is actually good now, because, the test is running here, against a not-yet-modified version of c/image, and it is passing; it probably shouldn’t.
| podman rmi -f quay.io/libpod/alpine:latest >/dev/null 2>&1 || true | ||
|
|
||
| # Test pullProgress=true with zstd:chunked image from local registry | ||
| start_registry |
There was a problem hiding this comment.
I see in the logs # started registry (auth=none) on port8081 vs.
POST libpod/images/pull?reference=localhost:5796
What is going on here? I can’t see any immediate explanation myself.
There was a problem hiding this comment.
… the logging in start_registry is using a wrong variable.
Can you fix that as well, please? A separate commit would be nice.
|
@mtrmac Yes, that was my intention to have the test failing here, but I'm surprised it actually passes. It definitely should not:( I had it failing locally with the main version of ‘c/image‘ and passing with the bugfix version so it made me think it's correct. I'll investigate what I did wrong, thanks. |
Progress reporting in container-libs/image did not update the progress channel for chunked layers. Add test that builds a new image with chunked layers, pull it using the REST API and verify that the progress stream contains events for partial pulls too. Depends-on: containers/container-libs#469 Signed-off-by: Marek Simek <msimek@redhat.com>
300c5dc to
54f93d1
Compare
|
It worked locally because I had and for some weird reason assumed it's the default option (it's The test passed on CI because it did not hit the code path at all (i.e. that's what the previous test exercises) 🤦♂️ |
Signed-off-by: Marek Simek <msimek@redhat.com>
mtrmac
left a comment
There was a problem hiding this comment.
Thanks! The explanation makes sense — let’s later see a passing version with a close-to-final implementation.
container-libs/imagedid not update the progress channel for chunked layers.This PR adds a test that builds a new image with chunked layers, pulls it using the REST API
images/pullendpoint with thepullProgressflag introduced in Extend libpod pull API to show pull progress #28224 and verifies that the progress stream contains events for partial pulls too.The fix for the container-libs bug needs to be merged first. The test currently fails as expected.
Depends-on: containers/container-libs#469
start_registry.Current outcome of the test:
Test with changes applied:
Checklist
Ensure you have completed the following checklist for your pull request to be reviewed:
commits. (
git commit -s). (If needed, usegit commit -s --amend). The author email must matchthe sign-off email address. See CONTRIBUTING.md
for more information.
Fixes: #00000in commit message (if applicable)make validatepr(format/lint checks)Noneif no user-facing changes)Does this PR introduce a user-facing change?
None.