Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

travis failure on rc3: "src/crypto/ctaes is not a subtree" #12388

Closed
laanwj opened this issue Feb 8, 2018 · 4 comments
Closed

travis failure on rc3: "src/crypto/ctaes is not a subtree" #12388

laanwj opened this issue Feb 8, 2018 · 4 comments
Labels

Comments

@laanwj
Copy link
Member

laanwj commented Feb 8, 2018

Travis on the 0.16 branch is failing on the subtree check.

0.04s$ if [ "$CHECK_DOC" = 1 ]; then contrib/devtools/git-subtree-check.sh src/crypto/ctaes; fi
ERROR: src/crypto/ctaes is not a subtree
The command "if [ "$CHECK_DOC" = 1 ]; then contrib/devtools/git-subtree-check.sh src/crypto/ctaes; fi" failed and exited with 2 during .

The reason for this is that it makes a shallow clone, and the last change to that subtree is deeper than the oldest commit fetched.

The obvious solution would be to clone deeper, but that would be kicking the can down the road and make things slower. I'd say to be robust the check needs to generate a warning in this case but continue. If nothing changed to it in the last 50 commits, then the subtree can be assumed to be fine, otherwise we would have intervened by then.

Ping @MarcoFalke @sipa

@laanwj laanwj added the Tests label Feb 8, 2018
@maflcko
Copy link
Member

maflcko commented Feb 8, 2018

The compressed size of the git objects for master at --depth 50 and --depth 99999 is 60 MiB and 80 MiB, respectively.

On the rc3 tag it is 30 MiB, but still with a download rate of 19.80 MiB/s, this should have limited effect on the total run time. https://travis-ci.org/bitcoin/bitcoin/jobs/338906244#L351

laanwj pushed a commit that referenced this issue Feb 15, 2018
Github-Pull: #12388

Tree-SHA512: 8dc7fd5619e60674021ef58f384ddaa2b0d49a88f8babab03697ab19819954f9521de0ede7398661be670ce6339bfea436b10ad916b72f194e18efdb3721c08d
@laanwj
Copy link
Member Author

laanwj commented Feb 15, 2018

I don't like that solution on the longer term, but it's ok for now on the 0.16 branch.

@laanwj
Copy link
Member Author

laanwj commented Feb 15, 2018

Grr apparently we already have an git fetch --unshallow step, removed it in 5e40e64, hopefully the tests there are fixed now...

@maflcko
Copy link
Member

maflcko commented Mar 13, 2018

We use a full clone now on all platforms (0f58d7f) due to

  • git subtree check
  • verify commits

and to simplify the travis yaml

Hope that is ok.

@maflcko maflcko closed this as completed Mar 13, 2018
maflcko pushed a commit that referenced this issue Mar 13, 2018
fa44af5 travis: Full clone for git subtree check (MarcoFalke)

Pull request description:

  Lazy workaround and fix for #12388

Tree-SHA512: ef2843c07bfe00b91a6f7ee551172b54db62a7e0120c734be2fa5e8cb2cb232e34f69239cae3cb319734e321822040ee7dcff00b8f0387a01afa6b3d26cc1ca3
HashUnlimited pushed a commit to chaincoin/chaincoin that referenced this issue Mar 16, 2018
Github-Pull: bitcoin#12388

Tree-SHA512: 8dc7fd5619e60674021ef58f384ddaa2b0d49a88f8babab03697ab19819954f9521de0ede7398661be670ce6339bfea436b10ad916b72f194e18efdb3721c08d
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants