-
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
TestFailsafeContext crashes when running fake platform
tests (host tests are ok)
#20089
Comments
Tried to reproduce locally and could not. |
failed 7 minutes ago in 1h 30m 14s ... could this be a 90 minute timeout? |
https://github.com/project-chip/connectedhomeip/runs/7103752299?check_suite_focus=true finished in 1:16, so likely not a timeout issue. |
- TestFailSafeContext is now crashy, even though it was just only recently moved in project-chip#20010 and no functional changes were done. - This may be related to other flakiness seen recently on random tests. This PR disables tests that are mostly covered by other test cases and for trivial logic that we won't touch tomorrow. Issue project-chip#20089
Just reproduced. It is not the x64 tests, but the fake tests. Run |
|
fake platform
tests (host tests are ok)
ArmFailsafe seems to fail on startTimer, where LayerImplSelect::mLayerState is Uninitialized. Unsure what must initialize things. |
- TestFailSafeContext is now crashy, even though it was just only recently moved in project-chip#20010 and no functional changes were done. - This may be related to other flakiness seen recently on random tests. This PR disables tests that are mostly covered by other test cases and for trivial logic that we won't touch tomorrow. Issue project-chip#20089
Problem
After merging #20010 master branch seems to consistently crash on linux test (2 crashes in a row, 0 crashes in several previous builds):
See https://github.com/project-chip/connectedhomeip/runs/7103687029?check_suite_focus=true
Proposed Solution
Figure out the reason.
The text was updated successfully, but these errors were encountered: