-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] OldRepositoryAccessIT testOldRepoAccess failing #115631
Comments
This has been muted on branch main Mute Reasons:
Build Scans: |
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
Pinging @elastic/es-distributed (Team:Distributed) |
Looks like this line is the failure:
marking as low risk since this only concerns shard skipping and it seems we should expect other tests to catch this. Assigning search team as well, to get their eyes on this. |
++ thanks @henningandersen Apologies for the noise |
I'm unable to run this test:
due to
@elastic/es-delivery is this something you can help with? |
I have the same problem locally, and I believe the issue is that you cannot run these tests on an aarch64 system since old versions of Elasticsearch are x64 only. |
This has been muted on branch 8.x Mute Reasons:
Build Scans: |
I noticed yesterday that this hasn't been working for a while on osx due to an issue with the jdk download plugin and how it handles the Zulu jdk 8 download / artifact transform. This bit should be solved via #117120 |
At least in one of the build-scans above I can see
That line in OldRepositoryAccessIT was changed recently (25/10) by https://github.com/elastic/elasticsearch/pull/115314/files#diff-089e10b8f461c2e6a342b3fdb4d430eeea6284cf807472471244b532193a5678R487, so at least that would coincide with the first ocurrences of this failure. |
This has been muted on branch 8.17 Mute Reasons:
Build Scans: |
The test fails reproducibly when we only use one shard here. I'm not sure if that is an intended effect of the changes in #115314 as I don't see any aggregations in the request we are sending later, but I will open a PR that adjusts expectations conditionally and ping @piergm for his opinion when he returns. |
Build Scans:
Reproduction Line:
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
The text was updated successfully, but these errors were encountered: