-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Fix 'occured' -> 'occurred' typos across e2e tests and monitors (8 files, 31 instances) #31026
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
Closed
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
26230c2
Fix occured typo in monitortest.go
SAY-5 92185f9
Fix occured typo in disruption.go
SAY-5 d4f3823
Fix occured typo in kernel_rt_latency.go
SAY-5 8625497
Fix occured typo in kernel_rt_functional.go
SAY-5 20eba61
Fix occured typo in machine_config_node.go
SAY-5 5f4569d
Fix occured typo in machines.go
SAY-5 e5ab29a
Fix occured typo in helpers.go
SAY-5 9c4b011
Fix occured typo in pinnedimages.go
SAY-5 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -496,7 +496,7 @@ func waitForPISStatusX(ctx context.Context, oc *exutil.CLI, kubeClient *kubernet | |
| if !success { // handle case when we are expecting the PIS application to fail, so the PIS degraded condition should become true | ||
| framework.Logf("Waiting for PinnedImageSetsDegraded=True") | ||
| conditionMet, err := WaitForMCNConditionStatus(clientSet, node.Name, mcfgv1.MachineConfigNodePinnedImageSetsDegraded, metav1.ConditionTrue, 2*time.Minute, 5*time.Second) | ||
| o.Expect(err).NotTo(o.HaveOccurred(), fmt.Sprintf("Error occured while waiting for PinnedImageSetsDegraded=True: %v", err)) | ||
| o.Expect(err).NotTo(o.HaveOccurred(), fmt.Sprintf("Error occurred while waiting for PinnedImageSetsDegraded=True: %v", err)) | ||
| o.Expect(conditionMet).To(o.BeTrue(), "Error, could not detect PinnedImageSetsDegraded=True.") | ||
|
Comment on lines
+499
to
500
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Minor consistency follow-up: nearby comment still has a typo. Line 499 is fixed, but Line 518 still says Suggested patch- // If we make it here, it means no fatal or non-fatal error has occured & the PIS application conditions were met
+ // If we make it here, it means no fatal or non-fatal error has occurred & the PIS application conditions were metAlso applies to: 518-519 🤖 Prompt for AI Agents |
||
| } else { // handle cases where we are expecting the PIS application to succeed | ||
| mcn, err := clientSet.MachineconfigurationV1().MachineConfigNodes().Get(ctx, node.Name, metav1.GetOptions{}) | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assertion message mismatches the condition being validated.
At Line 379 you wait for
Uncordoned=True, but Lines 380-381 still sayUpdateComplete=True. This makes failures misleading.Suggested patch
🤖 Prompt for AI Agents