Closed morri-son closed 2 weeks ago
@mandelsoft and @fabianburth , can you please check this? Maybe we sync files twice or the cleanup of the runner FS at the end does not work like expected?
Why do we have the additional cache
step anyway? The regular setup-go
has already a caching mechanism integrated, which is normally active by default...
Why do we have the additional
cache
step anyway? The regularsetup-go
has already a caching mechanism integrated, which is normally active by default...
@mandelsoft can you please comment?
@hilmarf , maybe we just switch it off and try it out? :-)
What happened: The GitHub action steps writes tons of errors like
writes a huuuuuuge log and and takes quite long, nonetheless is successful.
What you expected to happen: no errors occur
How to reproduce it (as minimally and precisely as possible): check https://github.com/open-component-model/ocm/actions/runs/9446619572/job/26017119898 and trigger the action again.