Skip to content
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

Import from @google-cloud/logging makes jest tests hang #1515

Open
goodwin64 opened this issue Jun 29, 2024 · 2 comments
Open

Import from @google-cloud/logging makes jest tests hang #1515

goodwin64 opened this issue Jun 29, 2024 · 2 comments
Assignees
Labels
api: logging Issues related to the googleapis/nodejs-logging API. priority: p3 Desirable enhancement or 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

@goodwin64
Copy link

goodwin64 commented Jun 29, 2024

  1. Is this a client library issue or a product issue?
    It's a library issue.

  2. Did someone already solve this?
    It doesn't seem to be solved - Google doesn't give such results.

  3. Do you have a support contract?
    Yes, I'll duplicate this request there as well.

Environment details

  • OS: MacOS 14.1.1 (23B81), M1 chip
  • Node.js version: 18.17.1
  • yarn version: 1.22.19
  • @google-cloud/logging version: both 11.1.0 and 10.4.0

Steps to reproduce

  1. clone https://github.com/goodwin64/gcp-logging-jest-timeout
  2. yarn install
  3. yarn test
  4. Notice jest warns there are unresolved async operations:
gcp-logging-jest-timeout % yarn test
yarn run v1.22.19
$ jest
 PASS  src/trueBeTrue.test.ts
  true is true
    ✓ should be true (1 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        4.142 s, estimated 5 s
Ran all test suites.
Jest did not exit one second after the test run has completed.

'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.
✨  Done in 8.10s.
@goodwin64 goodwin64 added 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. labels Jun 29, 2024
@product-auto-label product-auto-label bot added the api: logging Issues related to the googleapis/nodejs-logging API. label Jun 29, 2024
@cindy-peng cindy-peng added priority: p3 Desirable enhancement or fix. May not be included in next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jul 9, 2024
@cindy-peng
Copy link
Contributor

Hi @goodwin64 , did you notice this issue in any other google cloud-logging releases other than 11.1.0 and 10.4.0?

@goodwin64
Copy link
Author

Hey @cindy-peng,
just these 2 as I tested just them. Maybe it can be reproduced in older versions too.

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. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants