Skip to content

Commit 4e9a21a

Browse files
committed
Fix broken new/reused disruption test names causing inaccurate flakes
1 parent 9c9ff1f commit 4e9a21a

File tree

1 file changed

+2
-2
lines changed
  • pkg/monitortests/kubeapiserver/disruptionlegacyapiservers

1 file changed

+2
-2
lines changed

pkg/monitortests/kubeapiserver/disruptionlegacyapiservers/monitortest.go

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,8 @@ func NewRecordAvailabilityOnly() monitortestframework.MonitorTest {
3636
}
3737
}
3838
func testNames(owner, disruptionBackendName string) (string, string) {
39-
return fmt.Sprintf("[%s] disruption/%s should be available throughout the test", owner, disruptionBackendName),
40-
fmt.Sprintf("[%s] disruption/%s should be available throughout the test", owner, disruptionBackendName)
39+
return fmt.Sprintf("[%s] disruption/%s connection/new should be available throughout the test", owner, disruptionBackendName),
40+
fmt.Sprintf("[%s] disruption/%s connection/reused should be available throughout the test", owner, disruptionBackendName)
4141
}
4242

4343
func newDisruptionCheckerForKubeAPI(adminRESTConfig *rest.Config) (*disruptionlibrary.Availability, error) {

0 commit comments

Comments
 (0)