-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
FXIOS-423 ⁃ [Sync Tests] Sync process does not seem to work using Stage server #6554
Comments
Hi @rfk, are you aware of any change on stage server that may be causing this? thanks! |
No recent changes that come to mind. Are you able to get any logs from the device when running the failing test? If you send me a zip of the logs I'm happy to comb through and look for any clues. |
@rfk Thanks for you quick response :) here you have some logs:
Hope that helps, if not I will try to get better ones with more info if possible |
Oh, wow. I'm getting a similar error when I try to access https://sync-4-us-east-1.stage.mozaws.net directly in the browser. Looks like it may be an Ops issue with the certificates on that host, I'll escalate into an Ops bug. (Edit: filed as https://bugzilla.mozilla.org/show_bug.cgi?id=1637171) |
I don't get that error anymore @rfk, I think that issue is solved for us from that part. If I go to that link I see: But, tests does not work yet. There may be also something on iOS side @garvankeeley. The error after trying to sync manually using sim and stage is this: Does it ring any bell? Thanks! |
I don't see anything that looks like an error there. |
Latest logs:
|
"A server with the specified hostname could not be found." @eoger @rfk firefox-ios/RustFxA/RustFirefoxAccounts.swift Line 119 in 7e7aebb
|
Thanks for the bump, I bet one of the stage sync storage nodes has gone down or changed configuration somehow. I'll follow up with ops and report back here. |
Ref https://bugzilla.mozilla.org/show_bug.cgi?id=1648581 for followup, but if you don't want to follow in bugzilla, I will reflect important updates back here. |
From the video at the top of this bug, it looks like this test may be signing in using a fixed email address of "[email protected]", as defined here. I suspect that this user is assigned to a now-dead storage node in stage. It's not good that the stage servers allow your account to continue to exist in this state, but there is a way to work around it: manually delete and re-create this account via https://accounts.stage.mozaws.net/ and then try running the tests again. This should cause the new user account to be allocated to a new and functioning storage node. (This assumes that you don't have any valuable data synced to that account, but given that the entire storage node seems to be dead, any such data is probably gone already...) |
Thanks @rfk, you are right, that's a fixed account I use to degub the tests. I did what you suggested and that account is working fine. But, the strange things continue...for the tests we create a new account each time, like: email='[email protected]', password='qfTcMcii' With this account, I see this screen, the sync does not work yet.. :( this error is reported:
I'm sorry for keeping you guys busy with this, looks like one error after another, I don't really know how to get to the bottom of this, but my feeling is that there is something going on. Also because we have had these tests working for long time pretty stable but after all the big changes that have happened behind the scenes, they are completely broken :( |
It seems to me we're failing to deserialize the |
Thanks @eoger that has fixed the issue on iOS side and now the testing accounts created work fine \o/ thanks for your help! |
Steps to reproduce
1-Log in with a stage account
2-Go to Settings and wait until you see the
Sync Now
label, tap on it again3-Go to Bookmarks
Expected behavior
The bookmark appears
Actual behavior
The bookmark is not synced. Upon tapping on
Sync Now
briefly showsSyncing
Please see video attached:
https://youtu.be/odZCxvVxJ4g
Note: This is not reproducible manually. Only when using stage server when running the automated tests
All sync integration tests are failing due to that and PR #6508 is blocked due to this.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: