-
Notifications
You must be signed in to change notification settings - Fork 472
Conformance test timings aren't logged #2951
Copy link
Copy link
Open
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/regressionCategorizes issue or PR as related to a regression from a prior release.Categorizes issue or PR as related to a regression from a prior release.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Description
Metadata
Metadata
Assignees
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/regressionCategorizes issue or PR as related to a regression from a prior release.Categorizes issue or PR as related to a regression from a prior release.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
No status
/kind bug
What steps did you take and what happened:
When running the conformance tests, the new Experiment / stopwatch approach in
#2941 doesn't seem to log the test durations anywhere, although the Gomega docs say it should be there.