Closed rchincha closed 9 months ago
Hm, these ci failures sure do seem unrelated...
Oh, no, this is a stacker-bom failure I guess:
7965 2024-02-06T00:17:11.0606144Z # {"level":"info","file":"/file1","package":"pkg1","time":"2024-02-06T00:17:03Z","message":"adding file to package"}
7966 2024-02-06T00:17:11.0607977Z # time="2024-02-06T00:17:03Z" level=info msg="Package SPDXRef-Package-pkg1 has 2 relationships defined"
7967 2024-02-06T00:17:11.0611665Z # {"level":"error","error":"serializing document: pre-rendering the document: rendering pkg pkg1 :computing verification code: unable to render package, files were analyzed but some do not have sha1 checksums","path":"/stacker/artifacts/doc-pkg1.spdx.json","time":"2024-02-06T00:17:03Z","message":"unable to write output"}
7968 2024-02-06T00:17:11.0615757Z # error: serializing document: pre-rendering the document: rendering pkg pkg1 :computing verification code: unable to render package, files were analyzed but some do not have sh a1 checksums
7969 2024-02-06T00:17:11.0617278Z # failed to generate layer artifacts for bom-alpine - execute failed: exit status 1
7970 2024-02-06T00:17:11.0617883Z # error: exit status 1
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
3177e8d
) 57.15% compared to head (3d1da55
) 55.77%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
https://github.com/project-stacker/stacker-bom/pull/57
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.