Skip to content
Test

fix: return a response that docker understands better when it doesn't find a manifest #47

Sign in to view logs

fix: return a response that docker understands better when it doesn't find a manifest

fix: return a response that docker understands better when it doesn't find a manifest #47

Triggered via pull request May 31, 2024 23:09
@gabivljgabivlj
opened #32
gv/correct-manifest-unknown
Status Failure
Total duration 24s
Artifacts –

test.yml

on: pull_request
Matrix: Unit Tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors
index.test.ts > v2 manifests > HEAD /v2/:name/manifests/:reference NOT FOUND: index.test.ts#L87
AssertionError: expected { errors: [ { …(3) } ] } to deeply equal { errors: [ { …(3) } ] } - Expected + Received Object { "errors": Array [ Object { "code": "MANIFEST_UNKNOWN", - "detail": "This error is returned when the manifest, identified by name and tag is unknown to the repository.", + "detail": Object { + "Tag": "reference", + }, "message": "manifest unknown", }, ], } ❯ index.test.ts:87:18
Unit Tests (20.x)
Process completed with exit code 1.
index.test.ts > v2 manifests > HEAD /v2/:name/manifests/:reference NOT FOUND: index.test.ts#L87
AssertionError: expected { errors: [ { …(3) } ] } to deeply equal { errors: [ { …(3) } ] } - Expected + Received Object { "errors": Array [ Object { "code": "MANIFEST_UNKNOWN", - "detail": "This error is returned when the manifest, identified by name and tag is unknown to the repository.", + "detail": Object { + "Tag": "reference", + }, "message": "manifest unknown", }, ], } ❯ index.test.ts:87:18
Unit Tests (18.x)
Process completed with exit code 1.