-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Component/s: Authentication
-
None
-
Needed
-
Summary
Use an appName in failpoints configured in the spec test mongodb-oidc-no-retry.yml.
Motivation
See description of: https://github.com/mongodb/specifications/pull/1891
Who is the affected end user?
Driver developers.
How does this affect the end user?
Occasional test failures.
How likely is it that this problem or use case will occur?
The GCP OIDC task failed 3 of the last 50 runs for the Rust driver.
If the problem does occur, what are the consequences and how severe are they?
Transient test failure. Minor.
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
Acceptance Criteria
- Failpoints in the specification test mongodb-oidc-no-retry.yml are configured with an appName.
- is related to
-
DRIVERS-2415 Implement OIDC SASL mechanism
-
- In Progress
-
- split to
-
CSHARP-5868 Add appName to OIDC test failpoints
-
- Needs Triage
-
-
CXX-3413 Add appName to OIDC test failpoints
-
- Needs Triage
-
-
GODRIVER-3808 Add appName to OIDC test failpoints
-
- Needs Triage
-
-
JAVA-6092 Add appName to OIDC test failpoints
-
- Needs Triage
-
-
NODE-7426 Add appName to OIDC test failpoints
-
- Needs Triage
-
-
PHPLIB-1782 Add appName to OIDC test failpoints
-
- Needs Triage
-
-
RUBY-3769 Add appName to OIDC test failpoints
-
- Needs Triage
-
-
RUST-2356 Add appName to OIDC test failpoints
-
- Needs Triage
-
-
CDRIVER-6232 Add appName to OIDC test failpoints
-
- In Code Review
-
-
PYTHON-5715 Add appName to OIDC test failpoints
-
- In Code Review
-