Validation of operational intents: Severity of check 'Failure' was not specified

[wing-utm-sharing-airspace]

Observed behavior
During execution of the Validation of operational intents test scenario, we occasionally see the test crash with the following error message:

Example Test Artifacts:
169ac2c9-1a6a-4e9a-9ab5-e1a915ad72ff.zip

Test check
Failure occurs right after:
Scenario: Validation of operational intents
Case: Validate precision of intersection computations
Step: Attempt to plan Tiny Overlap Conflict Flight

Difference from expected behavior
Would expect the test to report a failure and continue with execution instead of stopping early.

[the-glu]

Based on test artifacts, it's seems that you're running interuss/monitoring/v0.15.0. It's seems to have been fixed in https://github.com/interuss/monitoring/pull/1025/changes#diff-bbf74b9d4d3ab408e52b2478308bd5461fdba547b738beb287a683babfd92ec4R136 that has been released in v0.16.0.

Could you try to update a more recent version or 'manually' apply the patch (taking a recent version of monitoring/uss_qualifier/scenarios/astm/utm/flight_intent_validation/flight_intent_validation.md should do the job) to check if it's still happening?

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.