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

[uss_qualifier] scenario config: fix message_signing and validate qualifier run #713

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Shastick
Copy link
Contributor

@Shastick Shastick commented Jun 11, 2024

This PR:

  • introduces a validation block to the message_signing configuration, so that we may more easily detect errors
  • don't expect and pass a priority_preemption_flightsto uft/message_signing.yaml as priorities are not supported

This should result in:

  • failures being detected and reported by the CI
  • the conflict_higher_priority scenario to be skipped

Resolves #693

Test Plan:
I started by introducing the validation, which correctly detected the failure.

Fixing the configuration, the test suite then passes.

@Shastick Shastick force-pushed the message-signing-fixes branch 2 times, most recently from b02d03f to 8653ccd Compare June 11, 2024 09:02
@Shastick Shastick marked this pull request as draft June 11, 2024 10:19
@Shastick
Copy link
Contributor Author

Shastick commented Jun 11, 2024

Taking this to draft, as the message_signing suite should skip the ConflictHigherPriority scenario entirely, and I need to change how the f3548 suite gets configured in order to achieve this

@Shastick Shastick force-pushed the message-signing-fixes branch 4 times, most recently from a78fa3f to 78685e9 Compare June 11, 2024 12:59
@Shastick Shastick marked this pull request as ready for review June 11, 2024 13:00
@Shastick Shastick marked this pull request as draft June 17, 2024 06:31
…lifier run

This PR:
 - introduces a `validation` block to the `message_signing` configuration, so that we may more easily detect errors
 - adds a separate `FlightIntentsResource` that contains conflicting flights that all share the `0` priority
 - use the above new resource to fix `message_signing`, as what is tested by `message_signing` does not support different priorities

Test Plan:
I started by introducing the validation, which correctly detected the failure.

Introducing the new resource then fixed the problem, and a run of `./run_locally.sh configurations.dev.message_signing` then succeeded.
@Shastick Shastick force-pushed the message-signing-fixes branch 2 times, most recently from ac7fcf7 to ed81c1e Compare August 27, 2024 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[scenario failure] configurations.dev.message_signing fails
1 participant