updated instrucitons in case people get confsued like i did

[ineskhou]

Update Integration Test Instructions

Description

When I was running the integration tests on my computer I ran into some issues because of the changes to the integration tests, zephyr did not install properly. This just tells people where to run make so they don't have any issues.

Related Issues/Tickets

How Has This Been Tested?

• Unit tests
• Integration tests
• Z Tests
• Manual testing (describe steps)

Screenshots / Recordings (if applicable)

Checklist

• Written detailed sdd with requirements, channels, ports, commands, telemetry defined and correctly formatted and spelled
• Have written relevant integration tests and have documented them in the sdd
• Have done a code review with
• Have tested this PR on every supported board with correct board definitions

Further Notes / Considerations

[Mikefly123]

Hey @ineskhou and @hrfarmer. I realize this has already been merged in, but I am a little unclear on what issue is being solved here. You shouldn't have to clone the repo in order to setup an integration test runner, the CI system should be doing that for you when it runs ci.yaml.

Are you guys running into the shadow .west in the parent directory problem? If so I think the fix would actually be to make sure wherever you setup the actions runner is encapsulated in at least one layer of folder structure away from any other Zephyr environments so there aren't conflicts.

For example on the deathstar from home I created a proves-ci/runner folder and then put the runner in there. So if and when the repo creates the .west in the parent directory there is little chance it propagates issues to other repos.

[ineskhou]

There was no west directory created automatically, which causes a “no west” error when running integration tests for the first time. It seems that when we moved the Zephyr-related steps into the Make process, the runner setup started missing a few initialization steps.

When I last set up a runner on this same computer, it worked without needing any extra steps, but yesterday it didn’t work out of the box. The runner is typically located two folders above any West repository, plus the two directories created during setup. However, running make in the folder where everything is automatically cloned resolves the issue.

We decided to update the instructions to have users run make right after encountering the integration test failure, since that made the process clearer.

[ineskhou]

For ref without running make