I think that 20 is still too shallow, 50 didn't work with the nightly wheels for 1.21.0. Note that the needed tag only dates to last Saturday, for which 20 barely suffices. The other problem with depth is that it is hard to determine precisely how much is taken, it depends on merges and such. For the true minimum needed you could use the date on which the tag was added; --shallow-since=2021-05-22.

That makes sense - adjusted now.

I was going for the minimum to build since the NumPy build in the container is basically to leverage the use of cache. Since when Gitpod creates a new workspace it makes a fresh clone and builds again - but since we already did a quick build in Docker this should take way less time.

Anyway, this should be all ready to go, thanks for all the insights @charris

The test failures are unrelated. I still haven't managed to figure out how to interpret git 'revisions'. AFAICT, depth goes down all the reachable branches to that many revisions, but even with that I can't figure where it ends in the main branch. Maybe the merged branches provide shortcuts to where they started in the main branch.

Thanks Tania.

Hmm, this failed, but differently

#12 0.350 error: Could not read 3c6a2f8b95a8a673821f4f061ec5ff9615cfdfef
#12 0.350 fatal: Failed to traverse parents of commit ca2880476f2f0f9ff3ba4ca0889ac9911727be9b

The second hash is this commit, the first is the last commit before this. I wonder if the gitpod repo was current?

The .gitpod.yml file has the master branch enabled. Should it be main?

I've made another fix, see #19132.