OpenDevicePartnership / OpenDevicePartnership/patina
[Feature]: Run SCTs periodically
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 544
- Forks
- 54
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 30
Description
Feature Overview
SCTs should be run on some type of basis (weekly, nightly, etc) on one or both of the qemu platforms. Results should be reported automatically or any SCT failures should have issues automatically created.
Solution Overview
In preparation:
- Get SCTs in a state where they can be run without any asserts that result in the SCTs stopping / freezing prematurely
- Prepare a VHD containing SCTs that can be attached to the latest build of a qemu platform. The VHD should contain a sequence file of the tests we care about (or all tests, depending). VHD should contain a startup nsh to start tests, and close qemu when finished. Must account for the fact that tests restart the system
In workflow:
- Compile the latest platform in release
- download the VHD
- Run the platform with the attached VHD
- Once finished, attach VHD (or extract results) and evaluate, creating a report and/or creating issues for any newly failed SCTs
Alternatives Considered
Run manually every so often.
Urgency
Medium
Are you going to implement the feature request?
I will implement the feature
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the SCT execution path and the QEMU platform workflow, then review how release builds and attached VHDs are currently handled. Done means SCTs run periodically, survive test-triggered restarts, and produce reports or issues for newly failed tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, embedded-iot, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100