Fix CI test_invalid_rrule_fix test by freezing the time

[jbouwh]

Proposed change

Fix CI test_invalid_rrule_fix test by freezing the time. The test used the current time, but that fails if the current time falls outside of the event scope. Freezing the time fixes consistency the test.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @allenporter, mind taking a look at this pull request as it has been labeled with an integration (google) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of google can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign google Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[jpbede]

Looks good, thanks 👍

[MartinHjelmare]

How was the datetime selected? It doesn't match any of the recurrence dates, which seem to be one Friday a month. Is that correct?

[MartinHjelmare]

It overlaps with one of the Fridays. Is that the idea?

[jbouwh]

The tests takes the current time, I guess that is the reason why this test could pass before. So I picked a time in the past.
Possible the test it self needs improvements too, as this might be a bug. But that is something to be addressed in an other PR.

[jbouwh]

It overlaps with one of the Fridays. Is that the idea?

I was just lucky to find a date and time that made the test pass to be honest.

[frenck]

The thing that went wrong is the calendar entity that was on or off based if the current time fell into the calendar event rule or not.

This made the test flaky by design. This is a correct adjustment IMHO, as it time outside of the event (which was validated by assert state.state == STATE_OFF).

[MartinHjelmare]

Ok, I guess we can merge for now if it passes, but @allenporter should follow up and check if this is intended.