-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Release 4.9.1 - RC 2 - Pyserver integration #26062
Labels
Comments
Closed
API Tier 0 and 1
|
API Tier 2
|
RBAC Tier 0 and 1
|
ReviewLGTM |
juliamagan
changed the title
Release 4.9.1 - RC2 - Pyserver integration
Release 4.9.1 - RC 2 - Pyserver integration
Oct 1, 2024
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following issue aims to run all Pyserver integration tests for the current release candidate, report the results, and open new issues for any encountered errors.
Pyserver integration tests information
Test report procedure
All individual test checks must be marked as:
All test results must have one the following statuses:
Any failing test must be properly addressed with a new issue, detailing the error and the possible cause. It must be included in the
Fixes
section of the current release candidate main issue.Any expected fail or skipped test must have an issue justifying the reason. All auditors must validate the justification for an expected fail or skipped test.
An extended report of the test results must be attached as a zip or txt. This report can be used by the auditors to dig deeper into any possible failures and details.
Conclusions
All tests have been executed and the results can be found below.
All tests have passed and the fails have been reported or justified. I therefore conclude that this issue is finished and OK for this release candidate.
Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.
The text was updated successfully, but these errors were encountered: