Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: User Listeners
    • Labels:
      None

      Description

      Our rules for debouncing proximity triggered requests are too timing sensitive to allow their tests to run reliably. When running in a Linux VM, I repeatedly get a test hang as follows, in UserLogonHandlersTestDefs:

      10:51:21.212:  New user session starting: In future, you can visit the URL http://localhost:8081/journal/restore/%3E2019-01-15T10%3A51%3A21.212Z to restore the system's settings as they were at this point
      10:51:21.226:  UserLogonRequest completes successfully with the payload: User with GPII key noUser was successfully logged in.
      10:51:25.928:  Test case listener has not responded after 5000ms - at sequence pos 14 of 18 sequence element {
          "event": "{proximityTriggeredRequest3}.events.onComplete",
          "listener": "kettle.test.assertErrorResponse",
          "args": {
              "message": "Received 429 error due to debounce rules",
              "errorTexts": "Proximity trigger ignored due to bounce rules",
              "statusCode": 429,
              "string": "{arguments}.0",
              "request": "{proximityTriggeredRequest3}"
          }
      } of fixture Testing proximityTriggered logout with debounce
      

      I've observed this failure in many other cases as well, e.g. when testing memory exhaustion in Windows for GPII-3630

        Attachments

          Activity

            People

            • Assignee:
              stegru Steve Grundell
              Reporter:
              amb26 Antranig Basman
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: