-
Notifications
You must be signed in to change notification settings - Fork 973
Sync tests have failures #11118
Comments
From #11028 (comment) From #11028 (comment) From: #11054 (comment) It seems like the issue fails on master consistently at most since 4 days. |
|
@luixxiul is this only in 0.20.x ? |
As far as the sync tests fail on Travis, this issue seems to be reproduced on other branches. |
Unable to reproduce - I tested with current version of 0.20.x (9bb3c67) and also with the packaged build (both on a clean profile). |
Confirmed this also works as expected with master |
I can confirm some of the tests are broken:
I updated issue title and description |
Updated issue description
Some sync tests are failing
Steps to reproduce
npm run watch-test
npm run test -- --grep="Syncing"
Original issue description
Description
Sync causes an uncaught exception.
If you restart the browser, the browser gets stuck with this error and it does not respond.
Steps to Reproduce
rm -rf node_modules && rm -rf ~/.electron && npm i
npm run watch
andnpm start
Actual result:
The device does not appear on the devices list.
If you restart the browser, the browser gets stuck with that error and it does not respond.
Expected result:
Reproduces how often: [What percentage of the time does it reproduce?]
100% for me. Travis runs reproduce the same issue.
Brave Version
about:brave info:
Brave: 0.21.0
V8: 6.1.534.32
rev: 82d2eac
Muon: 4.4.19
OS Release: 16.7.0
Update Channel: Release
OS Architecture: x64
OS Platform: macOS
Node.js: 7.9.0
Brave Sync: v1.3.5
libchromiumcontent: 61.0.3163.79
Reproducible on current live release:
It is not reproduced for me.
Additional Information
Adding the milestone following the instruction by @bbondy
The text was updated successfully, but these errors were encountered: