Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dummy commit #397

Closed
wants to merge 1 commit into from
Closed

dummy commit #397

wants to merge 1 commit into from

Conversation

vik-chand
Copy link
Member

test

@github-actions
Copy link

github-actions bot commented Nov 9, 2022

Test Results

     80 files       80 suites   16m 38s ⏱️
3 274 tests 3 249 ✔️ 24 💤 1
3 373 runs  3 348 ✔️ 24 💤 1

For more details on these failures, see this check.

Results for commit cfdedc2.

@laeubi
Copy link
Contributor

laeubi commented Nov 9, 2022

@vik-chand as you can see even the GH suceeds here, but Jenkins failed. Sometimes its the other way round or both fail ...

@vik-chand
Copy link
Member Author

https://ci.eclipse.org/pde/job/eclipse.pde/job/PR-397/1/ failed with 611 API tool failures whereas the next one had other issue.

The equivalent tests in integration build page is fairly stable here https://download.eclipse.org/eclipse/downloads/drops4/I20221109-0600/testresults/html/org.eclipse.pde.api.tools.tests_ep426I-unit-macM1-java17_macosx.cocoa.aarch64_17.html#ApiToolsPluginTestSuite

For 611 failure issue, there is some dependency/config/releng issue in Tycho Surefire/Maven. I am not an expert in that area. I see lot of people has already tried fixing it. In the worst case scenario, we can disable it in ONLY in this workflow ( so that these tests run on Integration build page and issues are detected there). Till couple of years back or little more, I remember that only pde.ui tests used to run with gerrit. I know it is annoying but not a blocker. If there is a way to recreate this API tool problem in eclipse IDE, I will be more than happy to investigate/fix it.

@vik-chand
Copy link
Member Author

Closing this PR since this was a dummy PR

@vik-chand vik-chand closed this Nov 9, 2022
@laeubi
Copy link
Contributor

laeubi commented Nov 9, 2022

@mickaelistria has done some investigations to reproduce it in a local build, maybe he can help here.

And yes its kind of random, what makes it even harder, so I think it is more a timing issue than a problem with the configuration itself.

@vik-chand
Copy link
Member Author

@mickaelistria has done some investigations to reproduce it in a local build, maybe he can help here.

And yes its kind of random, what makes it even harder, so I think it is more a timing issue than a problem with the configuration itself.

Yes, I saw #354. A lot of time has been spent on this. Perhaps a way to disable these 611 tests in this workflow ( the test should still run on Integration build page) may be a better option. If someone can provide that patch with a comment linking to bug , there would work too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants