-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Galasa is duplicating run info returned to "galasactl runs get" #2049
Comments
Looks like the duplication of results is a client-side defect in galasactl - added a bit more logging locally and ran In this example, the API server returned 751 runs:
But the final summary view showed a total of 1563 runs:
|
This is a client-side issue in the reporting of the tests in the formatting. |
Fix is here: galasa-dev/cli#310 |
delivered |
Describe the bug
Galasactl runs get returns many more runs for test runs that failed due to resource limitations and were requeued by the Galasa Ecosystem. Identified this bug with @eamansour and found that it also applied to the Galasa team's ecosystem.
There also seems to be no indication that a test that has run into a resource limitation error has been requeued, as far as the Galasa RAS is concerned the test is still running. This results in the test being returned by Galasactl runs get with the --active flag when the test has actually long since terminated.
Steps to reproduce
Expected behavior
Runs get should return correct number of tests, ideally returning only actively running tests with --active flag
The text was updated successfully, but these errors were encountered: