Pull Request tests failing after rebasing to latest (10/10/25)

[KurtE]

On the very sight possibility that you might be pulling in other Pull requests, I rebased one of my
Pull requests #195 to the latest sources, which did not see any conflicts or the like and all of the tests
had previously passed.

And now the PR shows as test failed. I am almost positive it has nothing to do with my changes
as the errors were on nano33...

[mjs513]

@KurtE

Was just looking at the errors and not sure that the job failure has anything to do with deferred-init PR since its slowing that it failed to compile Blink example. So have a feeling the error is the BLINK sketch test.

[KurtE]

As they did a release of zephyr this morning, thought I would rebase again to the latest.

So I rebased #195 to current stuff and pushed it.

It shows now with a checkmark that it can be merged, however I still get an email message saying not all of the
checks have passed. Looking at this version all of the zephyr_contrib and zephyr_main tests fail to build.

Also question, probably to self is: I synced up to build (in WSL) to latest, did a west update.
And it still updates to:

remote: arduino
      revision: zephyr-arduino-v4.2.0

Last change in here was a week ago:

As that is in west.yml,

but more recent change have been made in the branch
https://github.com/arduino/zephyr/tree/unoq-pr

What should we be testing with