-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
reduce flakiness of doSuccesfulLogin #643
Conversation
ac3dafa
to
40f98e3
Compare
since jenkinsci@ebdd746 it doesn't rely on path anyway
Assert.assertThat(this, loggedInAs(user)); | ||
waitFor().withTimeout(30, TimeUnit.SECONDS).until(() -> { | ||
assertThat(this, not(hasInvalidLoginInformation())); // login hasn't failed | ||
return ExpectedConditions.visibilityOfElementLocated(by.id("jenkins")); // redirect has happened |
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.
I am wondering if this can happen on other places where we also use clickAndWaitToBecomeStale
or until(CapybaraPortingLayerImpl::isStale);
This could likely be the cause (and the fix) of the race condition on creating a new Folder
that has been observed a a few times. https://issues.jenkins.io/browse/JENKINS-64358
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.
Yes it looks like the same class of issue.
I'm seeing regularly flakiness in my ATH such as
I think in some cases the current check is not enough and the navigation happens before the login is really completed.
While working on this area, I notices
doLoginDespiteNoPaths
was useless sincedoLogin
has been changed to not use path since ebdd746. So I deprecated it and removed calls I could find in this ATH.