Skip to content
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

Syncing latest changes from upstream main for kubernetes-csi-addons #124

Merged
merged 2 commits into from
Mar 7, 2024

Conversation

df-build-team
Copy link

PR containing the latest commits from upstream main branch

dependabot bot and others added 2 commits March 6, 2024 11:22
Bumps the github-dependencies group in /tools with 1 update: [github.com/operator-framework/operator-sdk](https://github.com/operator-framework/operator-sdk).


Updates `github.com/operator-framework/operator-sdk` from 1.33.0 to 1.34.0
- [Release notes](https://github.com/operator-framework/operator-sdk/releases)
- [Changelog](https://github.com/operator-framework/operator-sdk/blob/master/.goreleaser.yml)
- [Commits](operator-framework/operator-sdk@v1.33.0...v1.34.0)

---
updated-dependencies:
- dependency-name: github.com/operator-framework/operator-sdk
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
The test case was failing if the test was run at some particular
time of the day.

For ex: If the test was triggered @0:15:0, the last scheduled time
will be 23:15:0 of the previous day since we are setting it to an
hour earlier than the current time. Now when we calculate the
getNextSchedule, the next schedule will point to the current day,
when the cron job is scheduled to run at midnight every day. So
in this case, the lastMissed will be pointing to a valid time.
This leads to some test cases to get unexpected value for the
lastMissed time which expects it to be time.Time{}. Though we get
the expected wantErr in such cases too, since we are comparing the
other return values seperately.

To avoid such failures, this patch checks for multiple expected
last scheduled times.
Also the last scheduled time is aligned with the cron job schedule
to keep it relative.

Signed-off-by: karthik-us <[email protected]>
@df-build-team df-build-team requested a review from a team March 7, 2024 08:07
@karthik-us
Copy link
Member

/lgtm
/approve

Copy link

openshift-ci bot commented Mar 7, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: df-build-team, karthik-us

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Mar 7, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 2df2366 into main Mar 7, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants