-
-
Notifications
You must be signed in to change notification settings - Fork 29
test: use config.version Electron whenever possible
#1740
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1740 +/- ##
==========================================
- Coverage 89.28% 89.06% -0.23%
==========================================
Files 17 17
Lines 905 905
Branches 187 187
==========================================
- Hits 808 806 -2
- Misses 61 62 +1
- Partials 36 37 +1 ☔ View full report in Codecov by Sentry. |
dsanders11
left a comment
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.
Nice! This has been a thorn for a while now, thanks for fixing it. 👍
|
🎉 This PR is included in version 18.3.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Should fix up test stability a bit, where we were getting errors when running
platform=allon an Electron version that wasn't properly pre-downloaded.This regressed after 03347ec upgraded the pre-downloaded Electron version to v27.0.0 but kept a few tests on v1.4.13. With
DEBUGvariables, we can see this in action:@electron/getis colliding onSHASUMS256.txt, similar to what we found in #1540. The fix applied for that PR regressed for the aforementioned reason, but the underlying logic for this change is similar.We should also file this bug as a separate issue on the issue tracker.ref #1552