-
Notifications
You must be signed in to change notification settings - Fork 690
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
[functional testing] Resolve flaky logout in TB tests #3484
Comments
Lately, I've been running the TBB functional test suite in the long-running feature branch @zenmonkeykstop Try running the functional tests frequently on If we cannot find evidence of the flaky logout, then we should close this ticket, as changes elsewhere in the TBB push may have resolved. I also wonder how changes for #3486 will affect occurrence of the flakey logout. |
I don't have more details to report: this was reported by @kushaldas in discussion during a video chat we had. I filed this ticket (along with the other functional testing tickets) to break up the outstanding tasks into individual tickets. I can report that I have not seen this in some time (I ran the tests several times successfully during review of #3628), so if @zenmonkeykstop doesn't hit this when he runs against his instance then 👍 to close |
I'm running the functional tests from The following tests fail:
Will drill down a bit and figure out why; but @conorsch and @kushaldas if the test instance should be set up differently, please advise. |
@zenmonkeykstop Please test it against the local instance using the following command.
|
Oh, my bad @kushaldas - running locally, all tests pass. Will rerun them some more to see if I can trigger the flaky logout failure. |
@kushaldas I've run the tests repeatedly against the local dev instance and have not been able to replicate flaky logout. Everything passes or xfails. 👍 from me. |
thanks @zenmonkeykstop. Closing! |
In the existing Tor Browser functional testing branch, the logout in the journalist interface is sometimes flaky - i.e. it fails to log the user out and the test fails. We need to investigate why this is happening and resolve it prior to merge. Alternatively if it cannot easily be resolved, we should add a retry such that there are not spurious test failures.
Epic: #3659
The text was updated successfully, but these errors were encountered: