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
Fail CI on lingering timers (part 3) #91360
Closed
Closed
Conversation
This file contains 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
20 tasks
epenet
force-pushed
the
lingering-timers-3
branch
from
April 13, 2023 15:08
72cf483
to
11e57e3
Compare
This was referenced Apr 13, 2023
epenet
force-pushed
the
lingering-timers-3
branch
2 times, most recently
from
April 14, 2023 04:38
1283b0e
to
b3dd263
Compare
This was referenced Apr 14, 2023
epenet
force-pushed
the
lingering-timers-3
branch
from
April 15, 2023 07:22
b3dd263
to
b9aa28d
Compare
This was referenced Apr 15, 2023
epenet
force-pushed
the
lingering-timers-3
branch
from
April 18, 2023 07:44
b9aa28d
to
962ed09
Compare
This was referenced Apr 18, 2023
epenet
force-pushed
the
lingering-timers-3
branch
from
April 19, 2023 15:14
962ed09
to
18f4412
Compare
This was referenced Apr 19, 2023
This was referenced May 5, 2023
epenet
force-pushed
the
lingering-timers-3
branch
2 times, most recently
from
May 9, 2023 07:49
77671b0
to
bf3bc43
Compare
This was referenced May 9, 2023
epenet
force-pushed
the
lingering-timers-3
branch
from
May 15, 2023 07:58
bf3bc43
to
b1133d9
Compare
epenet
force-pushed
the
lingering-timers-3
branch
from
May 24, 2023 07:42
b1133d9
to
5838fbb
Compare
epenet
force-pushed
the
lingering-timers-3
branch
from
June 8, 2023 07:18
5838fbb
to
677cf71
Compare
epenet
force-pushed
the
lingering-timers-3
branch
from
July 31, 2023 15:36
677cf71
to
2370ed1
Compare
Because there hasn't been any activity on this PR for quite some time now, I've decided to close it for being stale. Feel free to re-open this PR when you are ready to pick up work on it again 👍 ../Frenck |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Proposed change
Follow-up to #89976
This third part prevents lingering timers in integration tests.
Needs:
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: