-
Notifications
You must be signed in to change notification settings - Fork 25k
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] XPackRestIT class failing #111944
Comments
…xpack.test.rest.XPackRestIT #111944
This has been muted on branch main Mute Reasons:
Build Scans:
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
* upstream/main: (91 commits) Mute org.elasticsearch.xpack.test.rest.XPackRestIT org.elasticsearch.xpack.test.rest.XPackRestIT elastic#111944 Add audit_unenrolled_* attributes to fleet-agents template (elastic#111909) Fix windows memory locking (elastic#111866) Update OAuth2 OIDC SDK (elastic#108799) Adds a warning about manually mounting snapshots managed by ILM (elastic#111883) Update geoip fixture files and utility methods (elastic#111913) Updated Function Score Query Test with Explain Fixes for 8.15.1 (elastic#111929) Mute org.elasticsearch.xpack.sql.qa.security.JdbcCsvSpecIT org.elasticsearch.xpack.sql.qa.security.JdbcCsvSpecIT elastic#111923 [ESQL] date nanos binary comparisons (elastic#111908) [DOCS] Documents output_field behavior after multiple inference runs (elastic#111875) Add additional BlobCacheMetrics, expose BlobCacheMetrics via SharedBlobCacheService (elastic#111730) Mute org.elasticsearch.xpack.sql.qa.multi_cluster_with_security.JdbcCsvSpecIT org.elasticsearch.xpack.sql.qa.multi_cluster_with_security.JdbcCsvSpecIT elastic#111923 Mute org.elasticsearch.xpack.sql.qa.multi_cluster_with_security.JdbcCsvSpecIT test {agg-ordering.testHistogramDateTimeWithCountAndOrder_2} elastic#111919 Mute org.elasticsearch.xpack.sql.qa.multi_cluster_with_security.JdbcCsvSpecIT test {date.testDateParseHaving} elastic#111921 Mute org.elasticsearch.xpack.sql.qa.multi_cluster_with_security.JdbcCsvSpecIT test {agg-ordering.testHistogramDateTimeWithCountAndOrder_1} elastic#111918 Mute org.elasticsearch.xpack.sql.qa.multi_cluster_with_security.JdbcCsvSpecIT test {datetime.testDateTimeParseHaving} elastic#111922 Mute org.elasticsearch.xpack.sql.qa.single_node.JdbcCsvSpecIT org.elasticsearch.xpack.sql.qa.single_node.JdbcCsvSpecIT elastic#111923 Mute org.elasticsearch.xpack.sql.qa.single_node.JdbcCsvSpecIT test {agg-ordering.testHistogramDateTimeWithCountAndOrder_1} elastic#111918 Mute org.elasticsearch.xpack.sql.qa.single_node.JdbcCsvSpecIT test {datetime.testDateTimeParseHaving} elastic#111922 Mute org.elasticsearch.xpack.sql.qa.single_node.JdbcCsvSpecIT test {date.testDateParseHaving} elastic#111921 ... # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java
…xpack.test.rest.XPackRestIT elastic#111944
…xpack.test.rest.XPackRestIT elastic#111944
This has been muted on branch 8.15 Mute Reasons:
Build Scans: |
…xpack.test.rest.XPackRestIT #111944
Pinging @elastic/ml-core (Team:ML) |
This has been muted on branch main Mute Reasons:
Build Scans:
|
…xpack.test.rest.XPackRestIT #111944
Hey @elastic/ml-core ! I just noticed that the bot muted the whole of |
From random sample:
|
Looks like it's all 3rd party model downloads, we'll mute these tests and unmute the whole suite - there's work being done to fix/slow down model download |
…csearch.xpack.test.rest.XPackRestIT elastic#111944" This reverts commit b712ab5. # Conflicts: # muted-tests.yml
…csearch.xpack.test.rest.XPackRestIT elastic#111944"
…xpack.test.rest.XPackRestIT #111944
This has been muted on branch main Mute Reasons:
Build Scans:
|
This is unrelated to the original problem. It was automatically re-opened because of a rollup change that was bad. It has been reverted. I will unmute this test. |
…csearch.xpack.test.rest.XPackRestIT elastic#111944" (elastic#113021) This reverts commit b712ab5.
…xpack.test.rest.XPackRestIT elastic#111944
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: