Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-3729

Telemeter CI issues

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • [Tech Debt] Telemeter integration test
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • NEW
    • 100
    • 100% 100%
    • MON Sprint 250, MON Sprint 251, MON Sprint 252
    • 0

      Epic Goal

      • Improve telemeter flaky integration test

      Why is this important?

           Ci is unstable and root issues are hard to debug this leads to time consumption task. Some binaries are old and the structure of mainly integration test are hard to understand and investigate issues.

      Iissues after rhel update:

       

      Also update binaries and bump go versions is usually hard. When develop new functions or add bugfix sometimes CI rise errors:

      https://github.com/openshift/telemeter/pull/526

      https://github.com/openshift/telemeter/pull/510

      Scenarios

      https://github.com/openshift/telemeter/blob/master/test/integration.sh

      https://github.com/openshift/telemeter/blob/master/test/integration-v2.sh

      Open questions:

      1. Integration test are needed in order to check robustness of code?
      2. Are v1 and v2 needed, are testing same thing?
      3. Should we refactor that tests?
      4. Other solutions?

            mariofer@redhat.com Mario Fernandez Herrero
            mariofer@redhat.com Mario Fernandez Herrero
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: