Random errors since 4.6.0 in CI tests

[kirrg001]

refs https://github.com/couchbase/couchnode/issues/132

Hi.

We are seeing random errors with 4.6.0:

@instana/collector: [analyticsindexes] must trace -- UTC: 2025-10-01T07:53:36.739Z (1759305216739) @instana/collector: ##### Test failed: Error: parsing failure @instana/collector: ##### Error stack: Error: parsing failure

@instana/collector: [searchquery] must trace -- UTC: 2025-09-30T13:17:48.450Z (1759238268450) @instana/collector: 1) [searchquery] must trace @instana/collector: npm error Lifecycle script test:ci:tracing:database failed with error: @instana/collector: npm error code 1 @instana/collector: npm error path /artifacts/packages/collector @instana/collector: npm error workspace @instana/[email protected] @instana/collector: npm error location /artifacts/packages/collector @instana/collector: ##### Test failed: Error: internal server failure @instana/collector: ##### Error stack: Error: internal server failure

See our app.js here:

• https://github.com/instana/nodejs/blob/v4.27.0/packages/collector/test/tracing/databases/couchbase/app.js
• https://github.com/instana/nodejs/blob/v4.27.0/packages/collector/test/tracing/databases/couchbase/app.js#L459
• https://github.com/instana/nodejs/blob/v4.27.0/packages/collector/test/tracing/databases/couchbase/app.js#L421

We did not see these random errors before. They appear randomly on our CI tests (x86). This started with the update to 4.6.0. The couchbase server version is the latest 7.6.x.

Thank you!

[thejcfactor]

Hi @kirrg001 -- Can you provide more detail around the issue, please? Can you narrow the scope down from your CI tests to a reproducible example? A reproducible example will be the quickest path to resolution.

• Do you see the same problem using v4.5.1?
  • This would help narrow down if it is related to behavior in the dot-minor upgrade.
• Did the version of the server change?
• Both tests mentioned have multiple steps, can you provide details on which specific step in the test is failing?

[kirrg001]

Hi.

Do you see the same problem using v4.5.1?

No I would say this behavior is new - especially on CI. Although I definitley saw "internal server failure" a couple of times locally before 4.6.0 when running the test.

Did the version of the server change?

No

Both tests mentioned have multiple steps, can you provide details on which specific step in the test is failing?

I have added some more debug information. I will report soon.