Skip to content
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

samples: crypto: psa_tls: Don't test secure-only nrf91 #11862

Conversation

SebastianBoe
Copy link
Contributor

Don't test secure-only nrf91 with psa_tls. NCS applications must use non-secure nrf91 due to a HW limitation in nrf91.

For this reason all nrf9160 samples test only against nrf91_ns and not nrf91 secure-only.

The only reason to test secure-only would be to test a library that would be used by a bootloader, but I can't imagine a bootloader would be doing psa_tls so skip this testing.

Omitting this testing will reduce CI load and decrease maintenance cost.

Don't test secure-only nrf91 with psa_tls. NCS applications must use
non-secure nrf91 due to a HW limitation in nrf91.

For this reason all nrf9160 samples test only against nrf91_ns and not
nrf91 secure-only.

The only reason to test secure-only would be to test a library that
would be used by a bootloader, but I can't imagine a bootloader would
be doing psa_tls so skip this testing.

Omitting this testing will reduce CI load and decrease maintenance
cost.

Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
@github-actions github-actions bot added the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Jul 24, 2023
@NordicBuilder
Copy link
Contributor

Test specification

CI/Jenkins/NRF

  • Integration Platforms

CI/Jenkins/integration

Test Module File based changes Manually selected West overwrite
test-fw-nrfconnect-nrf_crypto X

Detailed information of selected test modules

Note: This message is automatically posted and updated by the CI

@NordicBuilder
Copy link
Contributor

You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds.

Note: This comment is automatically posted by the Documentation Publishing GitHub Action.

Copy link
Contributor

@mswarowsky mswarowsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea

Copy link
Contributor

@Vge0rge Vge0rge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added @stephen-nordic here since it's useful for him to know.

@SebastianBoe
Copy link
Contributor Author

waiting for review from @magnev

@SebastianBoe
Copy link
Contributor Author

this change was not very popular

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants