Uploaded image for project: 'RHEL Conversions'
  1. RHEL Conversions
  2. RHELC-1736 Exiting with different exit codes when inhibitor found
  3. RHELC-1738

Exitting with different exit codes when inhibitor found - Integration tests

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • 2.2.0
    • None
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • 1
    • Testable
    • rhel-conversions

      The parent issue RHELC-1736 has the label that triggered autocreation of this subtask to track the relative story point estimation for the integration test part of the issue.

      The parent issue description at the time of creation of this issue was:
      When inhibitor is found, convert2rhel analyze and convert2rhel convert gives different exit codes when inhibitor is found.

      • analyze gives 0
      • convert gives 2

      The both should return 2 as it correspond with https://github.com/oamg/convert2rhel/blob/main/convert2rhel/main.py#L74
      I think it's caused by raising an AnalyzeExit https://github.com/oamg/convert2rhel/blob/main/convert2rhel/main.py#L74 before _raise_for_skipped_failures() is called.

      Acceptance criteria:

      • convert2rhel return 2 when inhibitor is found in analyze and convert steps

              ddiblik@redhat.com Daniel Diblik
              rhel-process-autobot RHEL Jira bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: