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

provide junit ScreenshotOnFailure TestWatcher #2368

Merged
merged 1 commit into from
Sep 29, 2024

Conversation

jukzi
Copy link
Contributor

@jukzi jukzi commented Sep 20, 2024

No description provided.

@HeikoKlare
Copy link
Contributor

HeikoKlare commented Sep 20, 2024

May this be better placed in org.eclipse.core.tests.harness, since it is not related to performance tests?

@akurtakov
Copy link
Member

May this be better placed in org.eclipse.core.tests.harness, since it is not related to performance tests?

Probably even better place is https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/tree/master/eclipse.platform.releng/bundles/org.eclipse.test .

Copy link
Member

@akurtakov akurtakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move to org.eclipse.test bundle.

@jukzi
Copy link
Contributor Author

jukzi commented Sep 20, 2024

Moving it would be a hell of work. Moving the class would be an API breakage. TracingSuite requires it needs to be fixed, Access restrictions need to be fixed... . I don't like how it is either, but to clean up that mess seems too complicated :-(

@akurtakov
Copy link
Member

Tests are not API incl org.eclipse.test. Does it make the task easier?

@jukzi
Copy link
Contributor Author

jukzi commented Sep 20, 2024

technically they are API. Some tests just do not include org.eclipse.test but the performance one. so no it's not helpful.

@akurtakov
Copy link
Member

Everything should be in o.e.test without any breakage so you can patch Screenshots in o.e.test bundle.

@akurtakov
Copy link
Member

Tests in I-build seems to be in good shape now.

Copy link
Member

@akurtakov akurtakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me now.

@jukzi
Copy link
Contributor Author

jukzi commented Sep 27, 2024

Not only seems that build error unrelated but should'nt it have produced an automated version bump @HannesWell ?
org.eclipse.jdt.doc.user: Only qualifier changed for (org.eclipse.jdt.doc.user/3.15.2300.v20240927-0605). Expected to have bigger x.y.z than what is available in baseline (3.15.2300.v20240823-1014) -> [Help 1]

@akurtakov
Copy link
Member

It is caused by #2392

@HannesWell
Copy link
Member

Not only seems that build error unrelated but should'nt it have produced an automated version bump @HannesWell ? org.eclipse.jdt.doc.user: Only qualifier changed for (org.eclipse.jdt.doc.user/3.15.2300.v20240927-0605). Expected to have bigger x.y.z than what is available in baseline (3.15.2300.v20240823-1014) -> [Help 1]

The version-increment workflow is not (yet) setup for this repository. In the current form it would be basically the same as the verification build. I plan to work on a Tycho mojo that should speed that up significantly but in the meantime I think it's not worth the effort to enable it in this repo.

@akurtakov akurtakov merged commit ee54898 into eclipse-platform:master Sep 29, 2024
4 checks passed
@jukzi jukzi deleted the ScreenshotOnFailure branch September 30, 2024 05:45
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.

5 participants