nodejs-docs-samples
nodejs-docs-samples copied to clipboard
GoogleCloudPlatform
run/jobs: generates logs in Cloud Logging failed
Note: #2715 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: e31657fbff8a23445ba3568b471356465323a30c buildURL: Build Status, Sponge status: failed
Test output
The expression evaluated to a falsy value:assert(found)
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert(found)
at Context.<anonymous> (test/system.test.js:93:5)</pre></details>
![flaky-bot[bot] avatar](https://avatars.githubusercontent.com/in/49504?v=4 "Published by a pub.dev verified publisher"){kind=small}
Looks like this issue is flaky. :worried:
I'm going to leave this open and stop commenting.
A human should fix and close this.
When run at the same commit (e31657fbff8a23445ba3568b471356465323a30c), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).
Oops! Looks like this issue is still flaky. It failed again. :grimacing:
I reopened the issue, but a human will need to close it again.
commit: d4eb8c8c3ed5d1d63245b7e7f28de45a95f3dd3e buildURL: Build Status, Sponge status: failed
Test output
The expression evaluated to a falsy value:assert(found)
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert(found)
at Context.<anonymous> (test/system.test.js:93:5)</pre></details>
Looks like #2725 did not resolve this flakiness.
@averikitsch let us know if there are any updates on alternative resolutions.
Oops! Looks like this issue is still flaky. It failed again. :grimacing:
I reopened the issue, but a human will need to close it again.
commit: 2acefcbe2c4d71669b6a28d075312076a17a5fee buildURL: Build Status, Sponge status: failed
Test output
The expression evaluated to a falsy value:assert(found)
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert(found)
at Context.<anonymous> (test/system.test.js:97:5)</pre></details>
The wait time and retry time has been extend multiple times for this sample. Ultimately, the logs do show up in Cloud Logging, but are not found during the test time limit. If the sample job completes its execution successfully, we could assume the sample works as intended and the logs will be present.
