Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-2188

[ERP] optaweb-employee-rostering-standalone handling exit code to avoid failing a build if test finished unsuccessfully

    XMLWordPrintable

Details

    • 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19)
    • 3
    • NEW
    • NEW

    Description

      in past week there is random failure in optawe-employee-rostering UI test which causes FDB run is halted.

      [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec (run-cypress-tests) on project optaweb-employee-rostering-standalone: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
      org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec (run-cypress-tests) on project optaweb-employee-rostering-standalone: Command execution failed.
      

      Any test in case of failure should be possible to ignore to finish running the whole build list of repositories.

      In case of maven-surefire-plugin or maven-failsafe-plugin tests it is possible to report and ignore the error/failure and continue.

      Interpret exit code from podman in case if the test are failing and in case if there was a problem with podman

       

      Test failed -> Mark build as yellow && Collect test reports && Proceed execution (do not mark build as failing)

      Podman run failed -> Mark build as yellow && Proceed execution (do not mark build as failing)

       

      Attachments

        Issue Links

          Activity

            People

              adupliak Anna Dupliak
              mnovotny@redhat.com Marek Novotny
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: