Description
//telecom/phone_calls/nodejs:test fails about 1 time out of 5.
Environment
- Where TypeDB server runs: grabl
- TypeDB version (and platform): 2.11.1
- TypeDB client: client-nodejs
Reproducible Steps
Steps to create the smallest reproducible scenario:
- Run
bazel test //telecom/phone_calls/nodejs:test --test_output=errors, a few times if necessary.
Expected Output
Passed test.
Actual Output
Failed test, for one of following reasons:
Unhandled promise rejection: TypeDBClientError: Error: 13 INTERNAL: [DBS05] Invalid Database Operation: Database with the name 'phone_calls_nodejs' has been deleted.TypeDBClientError: [CLI7] Client Error: The database 'undefined' does not exist.
Additional information
See logs here: https://grabl.io/dmitrii-ubskii/typedb-examples/61d687c6085ae2f372635105623735841aa30ef1/build/1/performance/1/benchmark-phone-calls-nodejs-test/1/command.log
I initially thought it might be some async weirdness with the cleanup step of some tests being executed after another had already started, but as far as I can tell, jasmine handles that properly. In the same vein, I also considered that perhaps the global variables aren't always fully initialised by the time the tests are executed, but moving the initialisation into the beforeEach() step didn't seem to affect anything.
Description
//telecom/phone_calls/nodejs:testfails about 1 time out of 5.Environment
Reproducible Steps
Steps to create the smallest reproducible scenario:
bazel test //telecom/phone_calls/nodejs:test --test_output=errors, a few times if necessary.Expected Output
Passed test.
Actual Output
Failed test, for one of following reasons:
Unhandled promise rejection: TypeDBClientError: Error: 13 INTERNAL: [DBS05] Invalid Database Operation: Database with the name 'phone_calls_nodejs' has been deleted.TypeDBClientError: [CLI7] Client Error: The database 'undefined' does not exist.Additional information
See logs here: https://grabl.io/dmitrii-ubskii/typedb-examples/61d687c6085ae2f372635105623735841aa30ef1/build/1/performance/1/benchmark-phone-calls-nodejs-test/1/command.log
I initially thought it might be some async weirdness with the cleanup step of some tests being executed after another had already started, but as far as I can tell, jasmine handles that properly. In the same vein, I also considered that perhaps the global variables aren't always fully initialised by the time the tests are executed, but moving the initialisation into the
beforeEach()step didn't seem to affect anything.