Test what causing the test failure

[laeubi]

• add message changes

[github-actions]

Test Results

106 files  ±0  106 suites  ±0   10m 23s ⏱️ +15s
657 tests ±0  646 ✔️  - 1  10 💤 ±0  1 ❌ +1 
657 runs  ±0  645 ✔️  - 1  11 💤 ±0  1 ❌ +1 

For more details on these failures, see this check.

Results for commit 3de5fcd. ± Comparison against base commit 2adb5ac.

♻️ This comment has been updated with latest results.

[laeubi]

It seems the new dependency causing the test-failure that's really strange...

[laeubi]

@mickaelistria any idea why the test is sensitive to the imports in the manifest?

[mickaelistria]

It may be some activation ordering or something of that sort. For instance with VM detection in JDT, some tests have started to fail because it induced a change in preference initialization order.

[laeubi]

I can run the project when importing it into a runtime-m2e... it also seem to not test m2e but running a java program directly, so this is mystery....

[HannesWell]

@laeubi is this still relevant?

[laeubi]

Yes this is still relevant unless someone can explain why we get a test failure for a completely unrelated change.

Adding org.eclipse.core.variables to the manifest let the test org.eclipse.m2e.jdt.tests.RunTest#testRunTwice fail for no obvious reason.