Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49524

JenkinsDatabaseSecurityRealmTest#login_and_logout is flaky

XMLWordPrintable

    • Evergreen - Milestone 1

      When analyzing the robustness of the SmokeTest category for JENKINS-49263
      I have found that JenkinsDatabaseSecurityRealmTest#login_and_logout is failing sometimes with the following error:

      expected:<jenkins-acceptance-tests-user (Full Name)> but was:<null (null)>

      I have debugged the problem and the issue seems to be that login is not finished (or at least not shown in the UI)

      Things that I have tried so far:

      • Dynamic wait of 10 seconds for log in link -> Seems to reduce flakiness but did not solve it
      • Refresh the page in case log link is not found to avoid cache problems -> No effect
      • The login form is correctly submitted because the test is automatically redirected to home after logging

      Not sure if this may be a performance issue, but 10 seconds for a login seems more than adequate for me.

      The test has to be fixed and reincorporated into SmokeTest category

          [JENKINS-49524] JenkinsDatabaseSecurityRealmTest#login_and_logout is flaky

          James Nord added a comment -

          rarabaolaza is this still the case?
          I beleive this should have been fixed with https://github.com/jenkinsci/acceptance-test-harness/commit/346961bb68da3fb058a01176a6788146985d90e2

          James Nord added a comment - rarabaolaza is this still the case? I beleive this should have been fixed with https://github.com/jenkinsci/acceptance-test-harness/commit/346961bb68da3fb058a01176a6788146985d90e2

          Mark Waite added a comment -

          Assumed fixed long ago.

          Mark Waite added a comment - Assumed fixed long ago.

            cactusmachete Ahilya Sinha
            rarabaolaza Raul Arabaolaza
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: