-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fix flaky test - TestAuditOn #12101
Fix flaky test - TestAuditOn #12101
Conversation
f5ea5d8
to
1a164e5
Compare
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.
Remind me again, what's the difference between Uploader
and UploadCompleter
? I wonder if we can rename one of them to make things more obvious.
Looks like now
|
Remove expriation update on termianted sessions to prevent race condition between upload processes.
38a539d
to
e54e496
Compare
…ssion tracker to prevent race condition.
e54e496
to
61221a2
Compare
32a7435
to
5193cef
Compare
There is a race condition between the
UploadCompleter
andUploader
. If both attempt to upload the same file, andUploader
loses, thenUploader
will return an error.This race condition became possible with the replacement of the 24 hour grace period in the
UploadCompleter
with the session tracker - #11551.I'm not yet sure how to remove the race condition entirely, but this PR will make it much much more unlikely to unblock integration tests in CI.
This PR reduces the likelihood of this race condition by decoupling the
UploadCompleter
andUploader
, so that theUploacCompleter
will always run on a ten minute interval as opposed to the 5 second interval ofUploaders
.Additionally, the proxy forwarding server does not (before this PR) use the session tracker service, so the
UploadCompleter
could not see whether an upload's session was active and would always try to upload session recordings prematurely.