-
Notifications
You must be signed in to change notification settings - Fork 216
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
Support sha512 content #543
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -92,27 +92,33 @@ conformance-test: | |
|
||
conformance-binary: $(OUTPUT_DIRNAME)/conformance.test | ||
|
||
TEST_REGISTRY_CONTAINER ?= ghcr.io/project-zot/zot-minimal-linux-amd64:v2.0.0-rc6@sha256:bf95a94849cd9c6f596fb10e5a2d03b74267e7886d1ba0b3dab33337d9e46e5c | ||
# TODO: update image once changes are merged in zot | ||
# TEST_REGISTRY_CONTAINER ?= ghcr.io/project-zot/zot-minimal-linux-amd64:v2.1.0 | ||
TEST_REGISTRY_CONTAINER ?= ghcr.io/andaaron/zot-minimal-linux-amd64:v2.1.0-manifest-digest | ||
registry-ci: | ||
docker rm -f oci-conformance && \ | ||
mkdir -p $(OUTPUT_DIRNAME) && \ | ||
echo '{"distSpecVersion":"1.1.0-dev","storage":{"rootDirectory":"/tmp/zot","gc":false,"dedupe":false},"http":{"address":"0.0.0.0","port":"5000"},"log":{"level":"debug"}}' > $(shell pwd)/$(OUTPUT_DIRNAME)/zot-config.json | ||
docker run -d \ | ||
-v $(shell pwd)/$(OUTPUT_DIRNAME)/zot-config.json:/etc/zot/config.json \ | ||
--name=oci-conformance \ | ||
-p 5000:5000 \ | ||
$(TEST_REGISTRY_CONTAINER) && \ | ||
sleep 5 | ||
|
||
conformance-ci: | ||
export OCI_ROOT_URL="http://localhost:5000" && \ | ||
docker rm -f oci-conformance || true | ||
mkdir -p $(OUTPUT_DIRNAME) | ||
docker run -d --rm \ | ||
--name=oci-conformance \ | ||
-p 5000 \ | ||
$(TEST_REGISTRY_CONTAINER) | ||
sleep 5 | ||
|
||
conformance-ci: conformance-binary | ||
export OCI_ROOT_URL="http://localhost:$$(docker port oci-conformance 5000 | head -1 | cut -f2 -d:)" && \ | ||
export OCI_NAMESPACE="myorg/myrepo" && \ | ||
export OCI_TEST_PULL=1 && \ | ||
export OCI_TEST_PUSH=1 && \ | ||
export OCI_TEST_CONTENT_DISCOVERY=1 && \ | ||
export OCI_TEST_CONTENT_MANAGEMENT=1 && \ | ||
$(shell pwd)/$(OUTPUT_DIRNAME)/conformance.test | ||
|
||
conformance-clean: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See my other comment on this file, same applies here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It doesn't apply here, these commands are independent. let's mark this as resolved. |
||
docker stop oci-conformance || true | ||
[ ! -f $(OUTPUT_DIRNAME)/conformance.test ] || rm "$(OUTPUT_DIRNAME)/conformance.test" | ||
[ ! -f "junit.xml" ] || rm junit.xml | ||
[ ! -f "report.html" ] || rm report.html | ||
|
||
$(OUTPUT_DIRNAME)/conformance.test: | ||
cd conformance && \ | ||
CGO_ENABLED=0 go test -c -o $(shell pwd)/$(OUTPUT_DIRNAME)/conformance.test \ | ||
|
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.
Having all commands joined by
&&
ensures make executes them in the same shell.In the new code on the right side they seem to be executed in separate shells since they are different rows in the make target. (I also don't see
.ONESHELL
being used). I don't think this is intended, even if it is unlikely someone would usemake -j
It may be worth it to double check the new behavior of the make target is correct.
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.
From my limited testing,
make -j ...
would still run all steps within a single job in order. Removing the&&
was intended to let make better report failures when one step in the middle of a long list of steps fails. Without that, users are guessing if it's the mkdir, or which of the two docker commands output some error message. However, I'm far from a make expert, so if there are errors this creates, send a reproducible since I'd like to better understand this.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.
Nevermind, all is ok, please resolve