Skip to content
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

Gazelle API: successful validation reported as undefined #274

Closed
qligier opened this issue Sep 13, 2024 · 3 comments · Fixed by #282
Closed

Gazelle API: successful validation reported as undefined #274

qligier opened this issue Sep 13, 2024 · 3 comments · Fixed by #282
Assignees
Labels
bug Something isn't working

Comments

@qligier
Copy link
Member

qligier commented Sep 13, 2024

In the Gazelle API, when no message is present, the status is computed to undefined instead of successful.

@qligier qligier added the bug Something isn't working label Sep 13, 2024
@qligier qligier self-assigned this Sep 13, 2024
@qligier qligier reopened this Sep 26, 2024
@qligier
Copy link
Member Author

qligier commented Sep 26, 2024

As discussed with Malo, the EVSClient will recalculate the status on its side and PASSED will be changed back to DONE_UNDEFINED.
We need to add an info message to properly pass the validation in the EVSClient.

@oliveregger
Copy link
Member

also related to EHS-831

@oliveregger oliveregger reopened this Oct 10, 2024
@oliveregger
Copy link
Member

fixed in 3.9.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants