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
Eventually, the log does get 'End Polling' pushed to it here:
if(log)log.push('End polling');return;
However, log is an empty array by the time it gets back to the assert:
assert(log.indexOf('End polling')!==-1,'did not end polling');
This works in the latest v11 of Node, v11.15.0. This breaks in the next release, which is the first of v12, v12.0.0. I wasn't able to find anything that stands out in the changelog.
This could probably be fixed if we move everything to async/await, but I'm not sure. There might be an easier way.
The text was updated successfully, but these errors were encountered:
mdrichardson
changed the title
All Build Tests Failing
All Builds Have the Same Failing Test
Feb 25, 2020
Zerryth
changed the title
All Builds Have the Same Failing Test
[Engineering] TokenResolver "should end polling" - All Builds Have the Same Failing Test
Feb 25, 2020
Zerryth
added
P1
Painful if we don't fix, won't block releasing
R9
Release 9 - May 15th, 2020
labels
Feb 25, 2020
All of the builds have one test that is currently failing with:
I believe this has something to do with the tests being run in Node v12; they pass with Node v11 and lower.
I'm still digging into why this is, but so far, I've found that:
In the test, we pass in a log here:
Eventually, the log does get
'End Polling'
pushed to it here:However,
log
is an empty array by the time it gets back to the assert:This works in the latest v11 of Node, v11.15.0. This breaks in the next release, which is the first of v12, v12.0.0. I wasn't able to find anything that stands out in the changelog.
This could probably be fixed if we move everything to async/await, but I'm not sure. There might be an easier way.
The text was updated successfully, but these errors were encountered: