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

optaweb-employee-rostering-standalone cypress test randomly fails

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • optaweb-employee-rostering
    • None
    • 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28)
    • 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.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-2189 [ERP:frontend] Infinite warnings generation if solver terminating immediately

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-2188 [ERP] optaweb-employee-rostering-standalone handling exit code to avoid failing a build if test finished unsuccessfully

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: