-
Notifications
You must be signed in to change notification settings - Fork 63
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
Logging: "after all" hook in "Logging" failed #1298
Labels
api: logging
Issues related to the googleapis/nodejs-logging API.
flakybot: flaky
Tells the Flaky Bot not to close or comment on this issue.
flakybot: issue
An issue filed by the Flaky Bot. Should not be added manually.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Comments
flaky-bot
bot
added
flakybot: issue
An issue filed by the Flaky Bot. Should not be added manually.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
labels
Jun 12, 2022
product-auto-label
bot
added
the
api: logging
Issues related to the googleapis/nodejs-logging API.
label
Jun 12, 2022
yoshi-automation
added
🚨
This issue needs some love.
and removed
🚨
This issue needs some love.
labels
Jun 17, 2022
losalex
added
priority: p2
Moderately-important priority. Fix may not be included in next release.
and removed
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
labels
Jun 23, 2022
commit: caed0af Test outputThe specified key does not exist. Error: The specified key does not exist. at new ApiError (node_modules/@google-cloud/storage/build/src/nodejs-common/util.js:79:15) at Util.parseHttpRespBody (node_modules/@google-cloud/storage/build/src/nodejs-common/util.js:214:38) at Util.handleResp (node_modules/@google-cloud/storage/build/src/nodejs-common/util.js:155:117) at /workspace/node_modules/@google-cloud/storage/build/src/nodejs-common/util.js:536:22 at onResponse (node_modules/retry-request/index.js:240:7) at /workspace/node_modules/teeny-request/build/src/index.js:226:13 -> /workspace/node_modules/teeny-request/src/index.ts:333:11 at runMicrotasks () at processTicksAndRejections (internal/process/task_queues.js:97:5) |
Seems flaky |
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. commit: 8b257c6 Test output16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. Error: 16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. at Object.callErrorFromStatus (node_modules/@grpc/grpc-js/build/src/call.js:31:19) -> /workspace/node_modules/@grpc/grpc-js/src/call.ts:81:17 at Object.onReceiveStatus (node_modules/@grpc/grpc-js/build/src/client.js:190:52) -> /workspace/node_modules/@grpc/grpc-js/src/client.ts:352:36 at Object.onReceiveStatus (node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141) -> /workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:462:34 at Object.onReceiveStatus (node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181) -> /workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:424:48 at /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:188:78 -> /workspace/node_modules/@grpc/grpc-js/src/call-stream.ts:330:24 at processTicksAndRejections (internal/process/task_queues.js:79:11) for call at at ServiceClientImpl.makeUnaryRequest (node_modules/@grpc/grpc-js/build/src/client.js:160:30) -> /workspace/node_modules/@grpc/grpc-js/src/client.ts:324:26 at ServiceClientImpl. (node_modules/@grpc/grpc-js/build/src/make-client.js:105:19) -> /workspace/node_modules/@grpc/grpc-js/src/make-client.ts:189:15 at /workspace/build/src/v2/config_service_v2_client.js:311:29 -> /workspace/src/v2/config_service_v2_client.ts:464:25 at wrappedCall (node_modules/google-gax/build/src/paginationCalls/pagedApiCaller.js:86:20) -> /workspace/node_modules/google-gax/src/paginationCalls/pagedApiCaller.ts:107:15 at /workspace/node_modules/google-gax/build/src/normalCalls/timeout.js:44:16 -> /workspace/node_modules/google-gax/src/normalCalls/timeout.ts:54:13 at repeat (node_modules/google-gax/build/src/normalCalls/retries.js:80:25) -> /workspace/node_modules/google-gax/src/normalCalls/retries.ts:104:19 at /workspace/node_modules/google-gax/build/src/normalCalls/retries.js:118:13 -> /workspace/node_modules/google-gax/src/normalCalls/retries.ts:144:7 at OngoingCallPromise.call (node_modules/google-gax/build/src/call.js:67:27) -> /workspace/node_modules/google-gax/src/call.ts:81:23 at PagedApiCaller.call (node_modules/google-gax/build/src/paginationCalls/pagedApiCaller.js:118:25) -> /workspace/node_modules/google-gax/src/paginationCalls/pagedApiCaller.ts:152:19 at /workspace/node_modules/google-gax/build/src/createApiCall.js:84:30 -> /workspace/node_modules/google-gax/src/createApiCall.ts:118:26 at processTicksAndRejections (internal/process/task_queues.js:97:5) |
flaky-bot
bot
added
the
flakybot: flaky
Tells the Flaky Bot not to close or comment on this issue.
label
Sep 17, 2022
flaky |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: logging
Issues related to the googleapis/nodejs-logging API.
flakybot: flaky
Tells the Flaky Bot not to close or comment on this issue.
flakybot: issue
An issue filed by the Flaky Bot. Should not be added manually.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Note: #1151 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: 5e99ce1
buildURL: Build Status, Sponge
status: failed
Test output
The text was updated successfully, but these errors were encountered: