IdentityPoolClient for url-sourced subject tokens getAccessToken(): should reject with retrieveSubjectToken error failed

[flaky-bot]

Note: #1291 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

---

commit: 070ec96
buildURL: Build Status, Sponge
status: failed

Test output

Expected values to be strictly deep-equal:
+ actual - expected

Comparison {}


Comparison {
code: '404'
}

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:



actual - expected


Comparison {}



Comparison {
code: '404'
}

at processTicksAndRejections (internal/process/task_queues.js:97:5)

at async Context. (build/test/test.identitypoolclient.js:818:17)

-> /workspace/test/test.identitypoolclient.ts:1037:9

[flaky-bot]

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (070ec96), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[danielbankhead]

Fix: #1589

[flaky-bot]

Oops! Looks like this issue is still flaky. It failed again. 😬

I reopened the issue, but a human will need to close it again.

---

commit: d8e5eb9
buildURL: Build Status, Sponge
status: failed

Test output

Expected values to be strictly deep-equal:
+ actual - expected

Comparison {}


Comparison {
status: 404
}

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:



actual - expected


Comparison {}



Comparison {
status: 404
}

at runMicrotasks ()

at processTicksAndRejections (internal/process/task_queues.js:95:5)

at Context. (test/test.identitypoolclient.ts:1035:9)

[danielbankhead]

Closing in order to get fresher error logs (the error message here are not in the logs for some reason)