CLI flaky tests: propagate maven.settings

[ebullient]

No description provided.

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 37025f1

Status	Name	Step	Failures	Logs	Raw logs
✖	Initial JDK 11 Build	Build	Failures	Logs	Raw logs

Failures

⚙️ Initial JDK 11 Build #

- Failing: devtools/cli 

📦 devtools/cli

✖ Failed to execute goal net.revelc.code:impsort-maven-plugin:1.6.2:check (check-imports) on project quarkus-cli: Imports are not sorted in /home/runner/work/quarkus/quarkus/devtools/cli/src/test/java/io/quarkus/cli/CliNonProjectTest.java

[aloubyansky]

How is this change fixing the issue? Alphanumeric ordering?

[ebullient]

I'm not sure. Grasping at straws for what is going on in that one case sometimes.

The knock-on effect of the annotation is to force all tests to run serially/sequentially. There is one indication in the output that a change was detected... so I'm just wondering if there is any way that methods from the test are running at the same time (as they do all basically work within the same space)..

[ebullient]

Stuart and I looked again, and he made a connection I hadn't regarding where the resources were being pulled from. So I've yanked the test annotations, and replaced w/ a change to propagate maven.settings through tests, too.