Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upWait 10 seconds to make sure browser instances are closed #11239
Conversation
|
The change looks working properly: https://travis-ci.org/brave/browser-laptop/jobs/286708254#L3528
|
codecov-io
commented
Oct 3, 2017
•
Codecov Report
@@ Coverage Diff @@
## master #11239 +/- ##
==========================================
- Coverage 52.09% 52.06% -0.04%
==========================================
Files 269 269
Lines 25501 25501
Branches 4062 4062
==========================================
- Hits 13286 13277 -9
- Misses 12215 12224 +9
|
|
+1 from #11508 |
|
Looks good to me but I'm not sure if 10s is an OK number so deferring merge to @bsclifton @bbondy |
|
also pls put ledger tests in test plan too as their files were changed too and rebase against master latest as new tests were added. Thanks |
|
Thanks, the test was added to the 1st post. |
There are several cases where a new browser instance starts with .startApp() before the existing instance is completely closed with .stopApp(). Adding 10 seconds delay should almost assure that the existing instance is closed before new one starts even on a slow machine. Closes #10490 Auditors: Test Plan: 1. Run `npm run test -- --grep='sessionStore test'`
|
Is this fix not needed? I am not quite sure about that. |
|
We're just not tracking things in milestones anymore unless it blocks the release, see #general in slack. Things can get uplifted from backlog as they are done mostly. |
|
@bbondy I have seen that, and I am just wondering if the review on #11239 (review) above is not sufficient. |
|
Do you know how long it adds to the test suite total? |
|
120 seconds are added. As the test runs parallel on Travis, it practically adds 80 seconds (sessionStoreTest). |
Wait 10 seconds to make sure browser instances are closed
Wait 10 seconds to make sure browser instances are closed
Wait 10 seconds to make sure browser instances are closed
|
@luixxiul the tests aren't parallelized like that, unfortunately. There are 8 simple groupings that will run at the same time... The changes here affect 3 groupings. So each of those 3 groups would be affected and delayed, because each group runs in a serial fashion @luixxiul let's keep an eye on tests if you don't mind and ensure this doesn't eat up too much time |
|
++ notes left: |
luixxiul commentedOct 2, 2017
•
edited
There are several cases where a new browser instance starts with .startApp() before the existing instance is completely closed with .stopApp(). Adding 10 seconds delay should almost assure that the existing instance is closed before new one starts on a slow machine.
Closes #10490
Auditors:
Test Plan:
Run
npm run test -- --grep='sessionStore test'Run
npm run test -- --grep='ledger history'Check the Travis result as well
https://travis-ci.org/brave/browser-laptop/jobs/286708254#L3528
Submitter Checklist:
git rebase -ito squash commits (if needed).Test Plan:
Reviewer Checklist:
Tests