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.

Sign up for GitHub

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

Jump to bottom

Fix Jetty-10 failing tests on Windows. #6100

Closed
lachlan-roberts opened this issue Mar 25, 2021 · 5 comments
Closed

Fix Jetty-10 failing tests on Windows. #6100

lachlan-roberts opened this issue Mar 25, 2021 · 5 comments
Assignees
@lachlan-roberts
Labels
Stale For auto-closed stale issues and pull requests

Comments

@lachlan-roberts
Copy link
Contributor

Jetty version
10.0.x

Description
Multiple tests are failing when the jetty-10.0.x tests are run on windows, these should be reviewed and fixed.
@lachlan-roberts lachlan-roberts self-assigned this Mar 25, 2021
@lachlan-roberts
Copy link
Contributor Author

@joakime do you know if this can be closed after the #6581 PR?

@lachlan-roberts
Copy link
Contributor Author

Looks like the windows run on jetty-10.0.x seems to be passing on jenkins.
https://jenkins.webtide.net/job/nightlies/job/jetty-10.0.x-windows-nightly/

Although there is some failures for jdk-17
https://jenkins.webtide.net/job/nightlies/job/jetty-10.0.x-windows-nightly-jdk17/

This was referenced Sep 17, 2021
Merged
Merged
lachlan-roberts added a commit that referenced this issue Sep 22, 2021
@lachlan-roberts
Issue #6100 - fix flaky test MavenMetadataTest
5eb30b6 
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue Sep 23, 2021
@lachlan-roberts
Merge pull request #6888 from eclipse/jetty-10.0.x-6100-WindowsTests
f22bfcb 
Issue #6100 - fix flaky test MavenMetadataTest
@github-actions
Copy link

github-actions bot commented Sep 3, 2022

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Sep 3, 2022
@lachlan-roberts lachlan-roberts removed the Stale For auto-closed stale issues and pull requests label Sep 5, 2022
@github-actions
Copy link

github-actions bot commented Sep 6, 2023

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Sep 6, 2023
@github-actions
Copy link

github-actions bot commented Oct 7, 2023

This issue has been closed due to it having no activity.

@github-actions github-actions bot closed this as completed Oct 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lachlan-roberts lachlan-roberts

Labels
Stale For auto-closed stale issues and pull requests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lachlan-roberts