Porting a board - running twister #test #nrf5 #nrf52 #nrf53


Bob Recny <bob@...>
 

Greetings,

I'm preparing some PRs to add our u-blox nRF52 and nRF53 EVK boards to Zephyr. I'd like to run twister locally and seem to have things working. I'm running out of drive space due to the size of the twister output.
What's the best way to either limit what gets tested (i.e. don't need other than nRF5x), or what size drive should I allocate to my VM?

Thanks,
Bob Recny
brec-u-blox


Kumar Gala
 

On Mar 25, 2021, at 6:15 PM, Bob Recny <bob@kittycentral.us> wrote:

Greetings,

I'm preparing some PRs to add our u-blox nRF52 and nRF53 EVK boards to Zephyr. I'd like to run twister locally and seem to have things working. I'm running out of drive space due to the size of the twister output.
What's the best way to either limit what gets tested (i.e. don't need other than nRF5x), or what size drive should I allocate to my VM?

Thanks,
Bob Recny
brec-u-blox
How are you invoking twister? You can do the following for new boards:

./scripts/twister -p <NEW BOARD NAME>

That will limit twister to just build tests for the new board you are adding.

You can also add `-M` to help reduce disk usage

- k