-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Make Tests job fail quickly instead of timing out on discovery failure. #16439
Merged
andy31415
merged 1 commit into
project-chip:master
from
bzbarsky-apple:fix-test-script-cleanup
Mar 18, 2022
Merged
Make Tests job fail quickly instead of timing out on discovery failure. #16439
andy31415
merged 1 commit into
project-chip:master
from
bzbarsky-apple:fix-test-script-cleanup
Mar 18, 2022
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
If waitForAnyAdvertisement failed, we would not actually clean things up and sit there until the job timed out. Two changes to fix that: 1) Add the app to the app register before calling start() on it, so that the killAll() on the app register has a chance of killing the app. 2) Set self.process immediately, instead of doing it after things that might fail (like waitForAnyAdvertisement), so killing the app actually works.
andy31415
approved these changes
Mar 18, 2022
PR #16439: Size comparison from fea74e6 to ee728c1 Full report (27 builds for cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
andrei-menzopol
pushed a commit
to andrei-menzopol/connectedhomeip
that referenced
this pull request
Apr 14, 2022
…e. (project-chip#16439) If waitForAnyAdvertisement failed, we would not actually clean things up and sit there until the job timed out. Two changes to fix that: 1) Add the app to the app register before calling start() on it, so that the killAll() on the app register has a chance of killing the app. 2) Set self.process immediately, instead of doing it after things that might fail (like waitForAnyAdvertisement), so killing the app actually works.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If waitForAnyAdvertisement failed, we would not actually clean things up and sit there until the job timed out. Two changes to fix that:
Add the app to the app register before calling start() on it, so
that the killAll() on the app register has a chance of killing the
app.
Set self.process immediately, instead of doing it after things that
might fail (like waitForAnyAdvertisement), so killing the app actually
works.
Problem
Failures during test startup end up waiting for the CI job to time out instead of fast-failing.
Change overview
See above.
Testing
Introduced a
raise
inwaitForAnyAdvertisement
and checked that without these changesrun_test_suite.py
never terminates and with the changes it does.