Skip to content

Conversation

@cfriedt
Copy link
Member

@cfriedt cfriedt commented Jun 14, 2025

Ensure that qemu_x86 (the integration platform) is on the allow list for sample.net.sockets.socketpair.s32k148_evb.

INFO: Error found: sample.net.sockets.socketpair.s32k148_evb on
qemu_x86/atom (Not in testsuite platform allow list but is one of the
integration platforms)

https://github.com/zephyrproject-rtos/zephyr/actions/runs/15646760002/job/44085509728?pr=91121

The issue was introduced in 49091ff.

@cfriedt cfriedt added the Hotfix Fix for issues blocking development, i.e. upstream CI issues, tests failing in upstream CI , etc. label Jun 14, 2025
@cfriedt cfriedt requested review from a team and Copilot June 14, 2025 01:19
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the allow list configuration for the sample.net.sockets.socketpair.s32k148_evb integration platform by explicitly including the qemu_x86 platform.

  • Changed the platform_allow attribute from an inline value to a multi-line list to support multiple allowed platforms.
  • Added qemu_x86 alongside the existing s32k148_evb/s32k148 entry.

Copy link
Member

@stephanosio stephanosio left a comment

Choose a reason for hiding this comment

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

Give that sample.net.sockets.socketpair.s32k148_evb is intended to be run only on s32k148_evb/s32k148, wouldn't it make more sense to move integration_platforms from common to under sample.net.sockets.socketpair?

@cfriedt
Copy link
Member Author

cfriedt commented Jun 14, 2025

Give that sample.net.sockets.socketpair.s32k148_evb is intended to be run only on s32k148_evb/s32k148, wouldn't it make more sense to move integration_platforms from common to under sample.net.sockets.socketpair?

To be honest, I think I would prefer to undo the change here that was done just for this one platform in 49091ff and I think the project is generally moving in that direction. E.g. using tier0 platforms for CI mostly.

There are many unique board configurations that can be put in place for many different tests, there are many different shields. Do we really need to take any of them into account to verify that this code works in our CI? Not really.

It's also incredibly easy for NXP to use --alt-config-root to add their own specifications in their own CI.

platform_allow: s32k148_evb/s32k148
platform_allow:
- s32k148_evb/s32k148
- qemu_x86
Copy link
Member

Choose a reason for hiding this comment

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

that looks wrong. This is a specific scenaion for some board, should not have qemu_x86, which is already covered in the previous one. Just move the integration platforms like from common to the main scenario instead.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed!

@nashif
Copy link
Member

nashif commented Jun 14, 2025

Just notcied @stephanosio comment above, same thing I am saying here.

To be honest, I think I would prefer to undo the change here that was done just for this one platform in 49091ff and I think the project is generally moving in that direction. E.g. using tier0 platforms for CI mostly.

yes, fully agree here, this is getting out of hand with per platform sections and configurations, in a freaking sample. This needs to stop.

@cfriedt cfriedt force-pushed the socketpair-s32k148-evb-hotfix branch from 54c9c96 to f4ccf0a Compare June 14, 2025 10:48
@cfriedt cfriedt requested review from nashif and stephanosio June 14, 2025 10:48
stephanosio
stephanosio previously approved these changes Jun 14, 2025
Ensure that qemu_x86 (the integration platform) is on the allow list
for `sample.net.sockets.socketpair.s32k148_evb`.

```
INFO: Error found: sample.net.sockets.socketpair.s32k148_evb on
qemu_x86/atom (Not in testsuite platform allow list but is one of the
integration platforms)
```

Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
@sonarqubecloud
Copy link

@nashif nashif merged commit 4cb9c80 into zephyrproject-rtos:main Jun 14, 2025
21 checks passed
@cfriedt cfriedt deleted the socketpair-s32k148-evb-hotfix branch June 14, 2025 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Networking area: Samples Samples area: Sockets Networking sockets Hotfix Fix for issues blocking development, i.e. upstream CI issues, tests failing in upstream CI , etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants