OpenDevicePartnership / OpenDevicePartnership/patina

[Feature]: Run SCTs periodically

Open
#669 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

complexity:advanced state:backlog type:feature-request urgency:medium
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:

  1. Get SCTs in a state where they can be run without any asserts that result in the SCTs stopping / freezing prematurely
  2. 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:

  1. Compile the latest platform in release
  2. download the VHD
  3. Run the platform with the attached VHD
  4. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.