Uh oh!
There was an error while loading. Please reload this page.
fix: use crypto_key_path instead of crypto_key_path_path - #3319
Conversation
`crypto_key_path_path` was added in error and will be removed in a future version of the library
Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR |
Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot. |
Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR |
Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot. |
irvifa
commented
Apr 12, 2020
Hi, wondering why kokoro build is only failing on python 3.6 here. |
busunkim96
commented
Apr 13, 2020
@irvifa It looks like a resource collision from the 3.7 and 3.6 tests running concurrently. |
Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR |
1 similar comment
Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR |
Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot. |
tmatsuo
commented
Apr 22, 2020
The test failures are for other directories. |
tmatsuo
commented
Apr 22, 2020
@busunkim96 If you saw resource conflicts between builds, can you file an issue so that we'll be able to fix later? |
…GoogleCloudPlatform/python-docs-samples#3319) `crypto_key_path_path` was added to the library in error and will be removed in a future version of the library
…#3319) `crypto_key_path_path` was added to the library in error and will be removed in a future version of the library
…#3319) `crypto_key_path_path` was added to the library in error and will be removed in a future version of the library
…#3319) `crypto_key_path_path` was added to the library in error and will be removed in a future version of the library
…#3319) `crypto_key_path_path` was added to the library in error and will be removed in a future version of the library
…GoogleCloudPlatform/python-docs-samples#3319) `crypto_key_path_path` was added to the library in error and will be removed in a future version of the library
crypto_key_path_pathwas added to the library in error and will be removed in a future version of the library