Skip to content

Random timeout errors with mocha in pipelines #33

@dominik-kropp

Description

@dominik-kropp

We have the same issue as described in #15 and it has been blocking a feature merge for days. Locally, the tests run without issues.

We have tried many things to narrow down the root cause, commenting out tests line by line and trying it without test.data.reset, etc. It appears that whenever there is one test suite with a test.data.reset(), it fails in the pipeline in 80% of the cases.

Unfortunately, there is no trace information and I can't give you a reproducible case. Do you have any ideas how to troubleshoot this further? Can you have a look at the source code for this? Perhaps #15 was missing something?

Image

@cap-js/asyncapi: 1.0.3
@cap-js/attachments: 1.2.1
@cap-js/audit-logging: 0.8.3
@cap-js/cds-test: 0.3.0
@cap-js/cds-types: 0.9.0
@cap-js/change-tracking: 1.0.8
@cap-js/db-service: 1.19.1
@cap-js/hana: 1.8.1
@cap-js/openapi: 1.2.2
@cap-js/sqlite: 1.10.0
@cap-js/telemetry: 1.3.1
@sap/cds: 8.8.3
@sap/cds-common-content: 2.1.0
@sap/cds-compiler: 5.6.0
@sap/cds-dk: 8.9.4
@sap/cds-dk (global): 8.9.2
@sap/cds-fiori: 1.4.1
@sap/cds-foss: 5.0.1
@sap/cds-mtxs: 2.4.2
@sap/eslint-plugin-cds: 3.2.0
Node.js: v22.14.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions