You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to investigate whether it's a fetch-mock regression or whether we need to update our tests.
All failures have error messages like
Error: fetch-mock: Adding route with same name or matcher as existing route. See `overwriteRoutes` option.
at Object.FetchMock.addRoute (/Users/runner/runners/2.163.1/work/1/s/common/temp/node_modules/.pnpm/registry.npmjs.org/fetch-mock/8.3.0_node-fetch@2.6.0/node_modules/fetch-mock/cjs/lib/set-up-and-tear-down.js:41:9)
at Object.FetchMock.mock (/Users/runner/runners/2.163.1/work/1/s/common/temp/node_modules/.pnpm/registry.npmjs.org/fetch-mock/8.3.0_node-fetch@2.6.0/node_modules/fetch-mock/cjs/lib/set-up-and-tear-down.js:6:8)
at FetchHttpMock.mockHttpMethod (test/mockHttp.ts:2:35)
at FetchHttpMock.post (test/mockHttp.ts:2:35)
at Context.<anonymous> (test/defaultHttpClientTests.ts:4:2172)
at step (/Users/runner/runners/2.163.1/work/1/s/common/temp/node_modules/.pnpm/registry.npmjs.org/tslib/1.10.0/node_modules/tslib/tslib.js:136:27)
at Object.next (/Users/runner/runners/2.163.1/work/1/s/common/temp/node_modules/.pnpm/registry.npmjs.org/tslib/1.10.0/node_modules/tslib/tslib.js:117:57)
at /Users/runner/runners/2.163.1/work/1/s/common/temp/node_modules/.pnpm/registry.npmjs.org/tslib/1.10.0/node_modules/tslib/tslib.js:110:75
at new Promise (<anonymous>)
at Object.__awaiter (/Users/runner/runners/2.163.1/work/1/s/common/temp/node_modules/.pnpm/registry.npmjs.org/tslib/1.10.0/node_modules/tslib/tslib.js:106:16)
at Context.<anonymous> (test/defaultHttpClientTests.ts:4:1805)
at processImmediate (internal/timers.js:439:21)
The text was updated successfully, but these errors were encountered:
)
* [core-http][test] revert workaround of pinning fetch-mock version
Resolves#6714
There was a regression in fetch-mock
wheresrhys/fetch-mock#493
which is already fixed in the latest version of fetch-mock.
* Update pnpm-lock.yaml
We need to investigate whether it's a fetch-mock regression or whether we need to update our tests.
All failures have error messages like
The text was updated successfully, but these errors were encountered: