-
Notifications
You must be signed in to change notification settings - Fork 150
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
Picoquic builds failing because of module dependency #234
Comments
Looks like a temporary? glitch in GitHub. The error is |
Github is protesting that the commit exists for picotls, but does not exist for deps/picotest. Do you have a commit ID that is verified to exist for picotest? |
OK, I did verify that the commit mentioned in github is visible in git log for picotest. This is really weird. |
Does rerunning the test solve the issue? Hopefully it's a temporary error in the HTTP cache. |
I tried re-running several times. Same error. |
It is frustrating because I don't actually need the test code. But there is no cmake option to not produce the test code. |
Can you update picotls? Up-to-date master branch depends on a different commit of picotest :-) |
This is done in a script, starting from a clean state. I don't understand what "update picotls" means here. Do you mean before the |
@huitema My bad. I thought I changed the commit of picotest that picotls refers to. However, that was the case for quicly, not picotls. I've updated the ref of deps/picotest in commit 7898a8d. If you update your reference of picotls to up-to-date master, then you'd no longer be loading the problematic commit of picotls (i.e. |
Synching on the latest commit in picotls did fix the issue. Thanks. |
Still failing in more recent builds:
@kazuho Our scripts load picotls using:
It obviously does not work. Are we doing something wrong? |
The picoquic builds on travis align on specific commits of picotls, using command:
The specific commit ID was copied from the git log:
Here is the report from the picoquic travis build:
Any idea how to solve that?
The text was updated successfully, but these errors were encountered: