Error:: Test "should reinstate lost context" at test/unit/shim/promise-shim.test.js:248:13 generated asynchronous activity after the test ended. This activity created the error "AssertionError [ERR_ASSERTION]: current transaction exists" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: A resource generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of null (reading 'acceptTraceContextPayload')" which triggered an uncaughtException event, caught by the test runner. Error:: Test hook "beforeEach" at test/unit/collector/remote-method.test.js:597:5 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'trace')" and would have caused the test to fail, but instead triggered an uncaughtException event. Error:: Test "should handle independent branching legs" at test/unit/instrumentation/core/promises.test.js:54:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: Test "should handle independent branching legs" at test/unit/instrumentation/core/promises.test.js:54:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: Test "should handle jumping to branched catches" at test/unit/instrumentation/core/promises.test.js:64:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: Test "should handle jumping to branched catches" at test/unit/instrumentation/core/promises.test.js:64:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: Test "should handle branching in the middle" at test/unit/instrumentation/core/promises.test.js:74:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: Test "should handle branching in the middle" at test/unit/instrumentation/core/promises.test.js:74:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: Test "should handle jumping across a branch" at test/unit/instrumentation/core/promises.test.js:84:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: Test "should handle jumping across a branch" at test/unit/instrumentation/core/promises.test.js:84:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused the test to fail, but instead triggered an unhandledRejection event. Error:: Test "should handle jumping over a branched catch" at test/unit/instrumentation/core/promises.test.js:94:11 generated asynchronous activity after the test ended. This activity created the error "TypeError: Cannot read properties of undefined (reading 'getSegment')" and would have caused th