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

Update all non-deterministic tests to run 3x the normal CI/CD workflow on the release validation pipeline #3458

Closed

Conversation

matthewige
Copy link
Collaborator

@matthewige matthewige commented Apr 16, 2024

Description

Release managers were instructed to run the release validation workflow 3 times to ensure non-deterministic tests had enough time/attempts to run. This change updates the release validation to take care of this, and the manager should now only need to run the workflow once.

Closes #3376

Testing

None.

Documentation

Updated the release process documentation to indicate that only 1 run is required now.

Installation

n/a

@matthewige
Copy link
Collaborator Author

All, is there any way I can test this without merging this PR? (I could not seem to schedule the release validation CI on this branch).

@shpalani
Copy link
Collaborator

All, is there any way I can test this without merging this PR? (I could not seem to schedule the release validation CI on this branch).

To schedule, you need to have "signed-off" added under Labels in the Issue. (Ref: #3261). To test you can 1. temp. create an issue and add the label by yourself, 2. use the existing issue to add the label temp. to trigger.

@matthewige matthewige added signed-off The action requested in this issue is approved (e.g., new release). and removed signed-off The action requested in this issue is approved (e.g., new release). labels Apr 17, 2024
needs: regular
if: github.event_name == 'workflow_dispatch'
uses: ./.github/workflows/reusable-test.yml
with:
name: km_mt_stress_tests
name: km_mt_stress_tests-1
pre_test: .\setup_ebpf_cicd_tests.ps1 -KmTracing $true -KmTraceType "memory"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this require 3 iterations here rather than making .\execute_ebpf_cicd_tests.ps1 have a parameter to handle it in there?

Once potential fixes are merged to the release branch repeat the process until the workflow completes successfully.

Note: If any non-deterministic tests (such as fuzzer or stress) are added in the future, the release validation workflow should be updated to run 3x the normal
CI/CD workflow (either 3x the duration or 3 instances of the test).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any valid reason to run 3 instances of the test (as opposed to 3x the duration)? If so, what is the reason?

@matthewige matthewige marked this pull request as draft May 3, 2024 22:06
@Alan-Jowett
Copy link
Member

@matthewige what is the status of this PR? Is it abandoned? If so, please close it.

@matthewige matthewige closed this Oct 9, 2024
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.

The CI/CD release validation work flows must run the non-deterministic tests multiple times in a loop.
4 participants