-
Notifications
You must be signed in to change notification settings - Fork 3k
CI may need to exclude low resource boards #7845
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
Comments
@dannybenor @OPpuolitaival @bulislaw |
@neilwjackson |
Guys to accelerate that it would be better if you use our PREQ process. Create a PREQ and assign it to OP for review. |
@c1728p9 |
Internal Jira reference: https://jira.arm.com/browse/IOTCORE-379 |
Thank you for raising this issue. Please note we have updated our policies and |
Description
Upon the addition of new boards with low resources (mainly RAM, but also flash), few of our tests started failing on these boards. In order to prevent these CI failures, tests were modified to get skipped if these resources cannot be allocated. This solution is sub-optimal and adds overhead in our test code. We should think of a mechanism to distinguish such boards from the "normal" ones and exclude them from our CI, either altogether or partially.
Issue request type
[ ] Question
[x] Enhancement
[ ] Bug
The text was updated successfully, but these errors were encountered: