test_spec: Add CI-secdom-test #17458
Open
+17
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eirikekbjoe
requested review from
harish1992,
ChristopherBittner and
9gcity
|
|
github-actions
bot
added
the
changelog-entry-required
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 30a5c9d46bc06fe24cc2aa4596f85c06d7eb0bec more detailssdk-nrf:
Github labels
List of changed files detected by CI (1)Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
Adding new test specification for secdom public plan Jira: NCSDK-28744 Signed-off-by: Eirik Ekrheim Bjørklund <eirik.bjoerklund@nordicsemi.no>
eirikekbjoe
force-pushed
the
secdom-testspec
branch
from
908ea09
to
30a5c9d
Compare
eirikekbjoe
force-pushed
the
secdom-testspec
branch
3 times, most recently
from
5db2c14
to
c71d0b7
Compare
eirikekbjoe
force-pushed
the
secdom-testspec
branch
from
c71d0b7
to
7e6dfc2
Compare
jangalda-nsc
requested changes
Sep 25, 2024
miha-nordic
reviewed
Sep 26, 2024
|
|
||
| "CI-secdom-test": | ||
| - "samples/bluetooth/multiple_adv_sets/**/*" | ||
| - "samples/nfc/record_text/**/*" |
There was a problem hiding this comment.
Why SecDom CI should be run on NFC and applications changes?
There was a problem hiding this comment.
We are on a later revision of sdk-nrf and want to test our newest release with samples built from latest sdk-nrf.
There was a problem hiding this comment.
Why SecDom CI should be run on NFC and applications changes?
That sample is used to test peripheral access configuration via secdom.
eirikekbjoe
force-pushed
the
secdom-testspec
branch
from
7e6dfc2
to
30a5c9d
Compare
jangalda-nsc
approved these changes
Sep 27, 2024
ChristopherBittner
approved these changes
Sep 27, 2024
|
|
||
| "CI-secdom-test": | ||
| - "samples/bluetooth/multiple_adv_sets/**/*" | ||
| - "samples/nfc/record_text/**/*" |
There was a problem hiding this comment.
Why SecDom CI should be run on NFC and applications changes?
That sample is used to test peripheral access configuration via secdom.
eirikekbjoe
force-pushed
the
secdom-testspec
branch
from
a45b806
to
30a5c9d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding new test specification for public secdom test plan.
Jira: NCSDK-28744