-
Notifications
You must be signed in to change notification settings - Fork 30
samples.snippets.quickstart.quickstart_test: test_quickstart failed #149
Comments
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. When run at the same commit (fb8232d), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge). |
Fixed in #150 |
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: 674f337 Test outputargs = (project_id: "python-docs-samples-tests" cluster { project_id: "python-docs-samples-tests" cluster_name: "py-qs-te... worker_config { num_instances: 2 machine_type_uri: "n1-standard-1" } } } region: "us-central1" ,) kwargs = {'metadata': [('x-goog-api-client', 'gl-python/3.6.13 grpc/1.36.0 gax/1.26.3 gapic/2.3.0')]} |
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: 674f337 Test outputargs = (project_id: "python-docs-samples-tests" cluster { project_id: "python-docs-samples-tests" cluster_name: "py-qs-te... worker_config { num_instances: 2 machine_type_uri: "n1-standard-1" } } } region: "us-central1" ,) kwargs = {'metadata': [('x-goog-api-client', 'gl-python/3.6.13 grpc/1.36.0 gax/1.26.3 gapic/2.3.0')]} |
This looks like a reporting lag. Closing again. |
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: 674f337 Test outputargs = (project_id: "python-docs-samples-tests" cluster { project_id: "python-docs-samples-tests" cluster_name: "py-qs-te... worker_config { num_instances: 2 machine_type_uri: "n1-standard-1" } } } region: "us-central1" ,) kwargs = {'metadata': [('x-goog-api-client', 'gl-python/3.6.13 grpc/1.36.0 gax/1.26.3 gapic/2.3.0')]} |
@busunkim96 I'm scratching my head a bit here. This, #147 and #148 are failing based on an old version of the code that was fixed in PR #150 and I can't reproduce the errors locally. Any idea? |
@bradmiro The periodic build "rewinds" to the latest release to check the samples against the library published on PyPI. If there's nothing blocking the library release, one easy way to get rid of the error is to merge the release PR which will move forward the point to which the periodic build "rewinds" to. Takashi also recently added the option for a second periodic build option to test samples at head. googleapis/synthtool#992 Once that synth PR has trickled through you can choose to have both periodic builds (latest release and HEAD) or just one or the either. |
Gotcha, ok awesome. I have nothing blocking a merge on #138, so maybe we can proceed with that? Let me know if there's any blockers on your side. |
Dataproc 2.0 is the new default image which does not support n1-standard-1. Fixes googleapis/python-dataproc#147, googleapis/python-dataproc#148, googleapis/python-dataproc#149
Dataproc 2.0 is the new default image which does not support n1-standard-1. Fixes googleapis/python-dataproc#147, googleapis/python-dataproc#148, googleapis/python-dataproc#149
Note: #133 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: fb8232d
buildURL: Build Status, Sponge
status: failed
Test output
The text was updated successfully, but these errors were encountered: