-
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
Create a Second Test Context for TestReadInteraction #34041
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Remove stale label or comment or this will be closed in 30 days. |
Hello @arkq, |
Not until pigweed update, which will happen after full migration to ubuntu 24.04. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Remove stale label or comment or this will be closed in 30 days. |
connectedhomeip/src/app/tests/TestReadInteraction.cpp
Lines 232 to 233 in 9d56786
before the migration to pw_unit_tests,
TestReadInteraction
Got executed with two contexts with the second test context havingsSyncScheduler = true
. This was not ported as pw_unit_test doesn't offer a clear way to do that and we had to wait for the migration effort to be finished to do that.A workaround to do this was mentioned @arkq
This workaround should be done after the changes in Updated AppContext, LoopbackMessagingContext, and UDPMessagingContext to serve as PW test fixture classes. #34036 are integrated.
The text was updated successfully, but these errors were encountered: