Uploaded image for project: 'LAVA'
  1. LAVA
  2. LAVA-1154

LAVA: inform user about source of the timeout

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Minor
    • Resolution: Deferred
    • Fix Version/s: LAVA Community Project
    • Labels:
      None

      Description

      As discovered in CTT-736 it is not clear what is the source of the timeouts in a LAVA test job. Currently the hierarchy looks as follows:

      1. action defined timeouts (coming from the user)
      2. device dictionary (hidden from the user)
      3. job defaults (coming from the user)

      This isn't very useful as a user might be (incorrectly) assuming that not defining a timeout withing action would fall back to test job defaults. As this isn't the case, I see 2 options to resolve this ticket:

      • provide source of the timeout and allow users to read-only access to device dictionaries
      • change the hierarchy so the device dictionary timeouts are only used as a last resort - in case there is no other timeout defined anywhere in the test job.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  neil.williams@linaro.org neil.williams@linaro.org
                  Reporter:
                  milosz.wasilewski@linaro.org Milosz Wasilewski
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Due:
                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel