-
Notifications
You must be signed in to change notification settings - Fork 946
Fix Saucelabs tests for Firestore unit tests except IE #3095
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
dceb32a
72ebd44
e51cdbf
a6cc7e5
5575a4c
ee87d99
6513829
a288e8c
5f601d6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -271,12 +271,3 @@ export class TestPlatform implements Platform { | |
return this.basePlatform.randomBytes(nBytes); | ||
} | ||
} | ||
|
||
/** Returns true if we are running under Node. */ | ||
export function isNode(): boolean { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Seems like this wasn't being used anywhere, and there's a better version in @firebase/util so I hope it's okay to remove? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @wu-hui might have just started using this. He would probably be delighted to switch to the better version :) |
||
return ( | ||
typeof process !== 'undefined' && | ||
process.title !== undefined && | ||
process.title.indexOf('node') !== -1 | ||
); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know why it is flaky on Safari?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't been able to find any reason. The test relies on two setTimeouts at 1ms and 5ms happening in the correct order, and sometimes Safari doesn't seem to get the order right. I can't find any known bug or issue that might cause that.