Closed ghost closed 2 years ago
See https://github.com/actions/checkout#usage and the lfs
attribute, don't know if we should set this to true by default, I think that even if you use GitHub as the backend it still counts towards the monthly download limit.
I'm fairly sure the solution to this is to add
with:
lfs: true
To the generated ci.yml
. Given the costs (cash money) I don't think we should enable it by default and leave this to an exercise for the user.
Description
What I was trying to do (and succeeded): Pushing a change to my github repo.
On the github side of things, the
ci.yml
workflow is started on push, as expected. My container builds successfully but fails during the test run. The failure however is when loading the pytorch pre-trained weights file. This failure only happens with the Github CI environment. Locally it all works fine.What I Did / What Happened
So thie core issue is this:
_pickle.UnpicklingError: invalid load key, 'v'.
The weights are stored in my github repositiory (as required) using
git lfs
support. All works fine locally and in fact on three separate client machines, all locally (or via ssh). However, it fails on Gihub CI.I suspect the
git lfs
support isn't working in some way in the Github CI environment and instead of getting my actual 43MB of weights files, it is loading thegit lfs
pointer to it.