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

Controller error no device layer inet system shutdown #7605

Conversation

vivien-apple
Copy link
Contributor

Problem

Errors into inet/system does not propagate into CHIPDeviceController::Shutdown if no device layer is used.

Change overview

  • Propage the error

Testing

  • No testing was added since this change affects mostly Android and I expect the tests into src/app/tests/suites/ to generate some tests for it at some point.

@andy31415
Copy link
Contributor

Added "Tested manually" label with the assumption of 'compilation test only'.

"No tests at all but hoping we will have tests later" statement is a bit scary though

@vivien-apple
Copy link
Contributor Author

Added "Tested manually" label with the assumption of 'compilation test only'.

"No tests at all but hoping we will have tests later" statement is a bit scary though

Agreed. So far the controllers that have tests calling Shutdown are chip-tool and Objc. Those 2 have have CHIP_DEVICE_LAYER defined.
I would expect the Java tests to call Shutdown too once we will have them.

…ed and something unexpected happens during inet/system shutdown
@vivien-apple vivien-apple force-pushed the Controller_ErrorNoDeviceLayerInetSystemShutdown branch from 53b874a to 02c1d6b Compare June 15, 2021 08:51
@woody-apple woody-apple merged commit d39933c into project-chip:master Jun 15, 2021
nikita-s-wrk pushed a commit to nikita-s-wrk/connectedhomeip that referenced this pull request Sep 23, 2021
…ed and something unexpected happens during inet/system shutdown (project-chip#7605)
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.

6 participants