-
Notifications
You must be signed in to change notification settings - Fork 282
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
[email protected] #2260
[email protected] #2260
Conversation
Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (rules_libusb) have been updated in this PR. Please review the changes. |
Current failure is:
Is there a way we can allowlist this particular instance? The only alternative is expressing this dependency as a git_repository, which isn't ideal. We have an automated builder that creates these, the first number is the buildbucket ID and the second is the commit hash of interest. Separately, it appears the tools are choking on the URL and ignore the archive_type hint:
|
Nice, now it's just stuck on the unknown archive format:
Unfortunately, if I drop the |
Sent out #2261 to work around the current failure. |
4780b43
to
067a894
Compare
Should be ready for another look now, everything that has run is passing. |
Sorry, looks like there are more places in the BCR presubmit script that need patching :S |
Filed https://pwbug.dev/347353308 to track failures for next RC.
Filed https://pwbug.dev/347353308 to track failing workflows. I'll cut a second release candidate after I've had a chance to verify other environments after RC1 merges. |
First commit to add Pigweed's rules_libusb module to the BCR. We work from Gerrit, which does not have stable tarball hashes, so releases are provided via GCS.