-
Notifications
You must be signed in to change notification settings - Fork 1.9k
tests: setup GitHub Actions to replace Travis #1497
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
Conversation
…de_redis into @salakar/gh-actions
| if (process.platform !== 'win32') { | ||
| assert.equal(res[3], '9.9999999999999992e+22'); | ||
| } else { | ||
| assert.equal(res[3], '9.9999999999999992e+022'); |
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.
@Salakar I guess this is an issue with Redis itself on Windows?
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.
Maybe, it was consistent across all Node versions and only occured on Windows.
I did make a note of one strange behaviour though, it only started showing up on the newer Windows version Server 2019, didn't show on 2018 as far as I remember.
I have a todo already to try repro on my Windows box over the weekend, so will let you know the outcome here.
Additionally adds testing against many Node.js versions and Redis versions.
Description
Checklist
npm testpass with this change (including linting)?