Uploaded image for project: 'OpenShift Core Networking'
  1. OpenShift Core Networking
  2. CORENET-5509

revert the e2e job timeout increase

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • 1
    • None
    • None
    • CORENET Sprint 269, CORENET Sprint 270, CORENET Sprint 271, CORENET Sprint 272, CORENET Sprint 273, CORENET Sprint 274, CORENET Sprint 275, CORENET Sprint 276, CORENET Sprint 277, CORENET Sprint 278

      Because the ovnk build has started taking much longer (graph here), when we have
      to build it before running e2e we had to increase the default timeout from 4h0m to
      6h0m in order to more easily know if the actual e2e tests are passing. The timeouts
      were typically happening in steps after e2e has finished but when it happens the
      job is reported as failed.

      Once we fully understand the reasons why the build is taking longer we should
      revert the change that increased the timeout. It's possible that the build time
      is expected for whatever reason and in that case we can close this ticket with that
      info.

              jluhrsen Jamo Luhrsen
              jluhrsen Jamo Luhrsen
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: