spanner test failed without relevant file changes

[JoeWang1127]

Please make sure you have searched for information in the following guides.

• Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
• Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
• Check our Troubleshooting guide: https://github.com/googleapis/google-cloud-node/blob/main/docs/troubleshooting.md
• Check our FAQ: https://github.com/googleapis/google-cloud-node/blob/main/docs/faq.md
• Check our libraries HOW-TO: https://github.com/googleapis/gax-nodejs/blob/main/client-libraries.md
• Check out our authentication guide: https://github.com/googleapis/google-auth-library-nodejs
• Check out handwritten samples for many of our APIs: https://github.com/GoogleCloudPlatform/nodejs-docs-samples
• Check the API's issue tracker: https://cloud.google.com/support/docs/issue-trackers

Library Name

google-cloud-spanner

A screenshot that you have tested with "Try this API".

This issue is not about API.

Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.

#8505

A step-by-step description of how to reproduce the issue, based on the linked reproduction.

This is not a product issue, see the code change in the linked pull request.

A clear and concise description of what the bug is, and what you expected to happen.

The spanner kokoro test failed without touching spanner-related files, see run logs:
https://btx.cloud.google.com/invocations/86e63eea-4138-4ee6-8850-ad89a12f051a/targets/cloud-devrel%2Fclient-libraries%2Fnodejs%2Fpresubmit%2Fgoogleapis%2Fgoogle-cloud-node%2Fnodejs-spanner%2Fnode18%2Fsystem-test/log

https://btx.cloud.google.com/invocations/912a3b0e-11d3-4976-b444-040499ba1969/targets/cloud-devrel%2Fclient-libraries%2Fnodejs%2Fpresubmit%2Fgoogleapis%2Fgoogle-cloud-node%2Fnodejs-spanner%2Fnode18%2Fsystem-test-regular-session/log

1) Spanner
       instanceConfigs
         should list an instanceConfig's operations without filter:
     Error: 3 INVALID_ARGUMENT: Invalid ListInstanceConfigOperations request
      at callErrorFromStatus (node_modules/@grpc/grpc-js/src/call.ts:84:17)
      at Object.onReceiveStatus (node_modules/@grpc/grpc-js/src/client.ts:360:55)
      at  (node_modules/@grpc/grpc-js/src/call-interface.ts:179:27)
      at Object.onReceiveStatus (src/metrics/interceptor.ts:66:11)
      at InterceptingListenerImpl.onReceiveStatus (node_modules/@grpc/grpc-js/src/call-interface.ts:175:19)
      at  (node_modules/@grpc/grpc-js/src/call-interface.ts:179:27)
      at Object.onReceiveStatus (node_modules/grpc-gcp/src/index.ts:132:15)
      at InterceptingListenerImpl.onReceiveStatus (node_modules/@grpc/grpc-js/src/call-interface.ts:175:19)
      at Object.onReceiveStatus (node_modules/@grpc/grpc-js/src/client-interceptors.ts:466:34)
      at Object.onReceiveStatus (node_modules/@grpc/grpc-js/src/client-interceptors.ts:424:48)
      at  (node_modules/@grpc/grpc-js/src/resolving-call.ts:170:24)
      at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
  for call at
      at ServiceClientImpl.makeUnaryRequest (node_modules/@grpc/grpc-js/src/client.ts:325:42)
      at ServiceClientImpl. (node_modules/@grpc/grpc-js/src/make-client.ts:189:15)
      at  (src/v1/instance_admin_client.ts:527:25)
      at wrappedCall (node_modules/google-gax/build/src/paginationCalls/pagedApiCaller.js:88:20)
      at Immediate. (node_modules/google-gax/build/src/normalCalls/timeout.js:44:16)
      at process.processImmediate (node:internal/timers:478:21)

A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

These tests should pass or not run since no spanner related files changes in the pull request.

[jskeet]

These tests should pass since no spanner related files changes in the pull request.

To be slightly more specific, I'd say the tests shouldn't run since no spanner related files changed in the PR.

I believe that's now fixed - but the test itself still needs to be fixed.

[JoeWang1127]

To be slightly more specific, I'd say the tests shouldn't run since no spanner related files changed in the PR.

Thanks, updated the description.