-
Notifications
You must be signed in to change notification settings - Fork 21
Closed
Labels
flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
This test failed!
To configure my behavior, see the Flaky Bot documentation.
If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.
commit: 440c725367f35e3cf731fd1e9efb0c0d562e08f9
buildURL: Build Status, Sponge
status: failed
Test output
Response code 403 (Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.)
HTTPError: Response code 403 (Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.)
at EventEmitter. (node_modules/got/index.js:482:24)
at getResponse (node_modules/got/index.js:320:5)
at Immediate. (node_modules/got/index.js:147:6)
at processImmediate (internal/timers.js:461:21)Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.