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

[CI] MixedClusterEsqlSpecIT class failing #121594

Open
elasticsearchmachine opened this issue Feb 3, 2025 · 3 comments
Open

[CI] MixedClusterEsqlSpecIT class failing #121594

elasticsearchmachine opened this issue Feb 3, 2025 · 3 comments
Assignees
@not-napoleon
Labels
:Analytics/ES|QL AKA ESQL medium-risk An open issue or test failure that is a medium risk to future releases Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Feb 3, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

undefined

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

undefined

Issue Reasons:

  • [8.x] 16 failures in class org.elasticsearch.xpack.esql.qa.mixed.MixedClusterEsqlSpecIT (1.6% fail rate in 987 executions)
  • [8.x] 10 failures in step 8.14.3_bwc (71.4% fail rate in 14 executions)
  • [8.x] 6 failures in step 8.15.5_bwc (46.2% fail rate in 13 executions)
  • [8.x] 11 failures in pipeline elasticsearch-periodic (78.6% fail rate in 14 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Analytics/ES|QL AKA ESQL >test-failure Triaged test failures from CI Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 3, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-analytical-engine (Team:Analytics)

@alex-spies
Copy link
Contributor

alex-spies commented Feb 4, 2025 •
edited
Loading

One failure looks like an unrelated hickup while spinning up the test cluster:

[2025-02-03T22:48:41,860][INFO ][o.e.c.s.ClusterApplierService] [test-cluster-1] master node changed {previous [{test-cluster-1}{yFB2U-6nSReXo788U_P98g}{EfHDrddHRLqvis8XlHG0mQ}{test-cluster-1}{127.0.0.1}{127.0.0.1:37157}{cdfhilmrstw}{8.18.0}{7000099-8525000}], current []}, term: 3, version: 5, reason: becoming candidate: joinLeaderInTerm
[2025-02-03T22:48:41,862][ERROR][o.e.c.f.AbstractFileWatchingService] [test-cluster-1] shutting down watcher thread with exception java.util.concurrent.ExecutionException: org.elasticsearch.cluster.NotMasterException: no longer master
	at [email protected]/org.elasticsearch.action.support.PlainActionFuture$Sync.getValue(PlainActionFuture.java:279)
	at [email protected]/org.elasticsearch.action.support.PlainActionFuture$Sync.get(PlainActionFuture.java:266)
	at [email protected]/org.elasticsearch.action.support.PlainActionFuture.get(PlainActionFuture.java:96)
	at [email protected]/org.elasticsearch.reservedstate.service.FileSettingsService.processInitialFileMissing(FileSettingsService.java:151)
	at [email protected]/org.elasticsearch.common.file.AbstractFileWatchingService.watcherThread(AbstractFileWatchingService.java:188)
	at java.base/java.lang.Thread.run(Thread.java:1575)
Caused by: org.elasticsearch.cluster.NotMasterException: no longer master

[2025-02-03T22:48:41,865][INFO ][o.e.c.s.ClusterApplierService] [test-cluster-3] master node changed {previous [{test-cluster-1}{yFB2U-6nSReXo788U_P98g}{EfHDrddHRLqvis8XlHG0mQ}{test-cluster-1}{127.0.0.1}{127.0.0.1:37157}{cdfhilmrstw}{8.18.0}{7000099-8525000}], current []}, term: 3, version: 5, reason: becoming candidate: joinLeaderInTerm
[2025-02-03T22:48:41,893][INFO ][o.e.c.f.AbstractFileWatchingService] [test-cluster-1] watcher service stopped
[2025-02-03T22:48:41,893][ERROR][o.e.l.StartupSelfGeneratedLicenseTask] [test-cluster-1] unexpected failure during [maybe generate license for cluster] org.elasticsearch.cluster.NotMasterException: no longer master

[2025-02-03T22:48:41,896][ERROR][o.e.l.StartupSelfGeneratedLicenseTask] [test-cluster-1] unexpected failure during [maybe generate license for cluster] org.elasticsearch.cluster.NotMasterException: no longer master

[2025-02-03T22:48:41,923][ERROR][o.e.l.StartupSelfGeneratedLicenseTask] [test-cluster-1] unexpected failure during [maybe generate license for cluster] org.elasticsearch.cluster.NotMasterException: no longer master

The other build scans show failures in

  • test {date.IN operator with null in list, finds match ASYNC}
  • test {date.Implicit casting strings to dates for IN operator ASYNC}

These are the same as #120158 and #120159, resp.

@alex-spies alex-spies added medium-risk An open issue or test failure that is a medium risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 4, 2025
@alex-spies
Copy link
Contributor

I'll mute these pro-actively, otherwise we get a mute of the whole test suite.

@alex-spies alex-spies mentioned this issue Feb 4, 2025
Merged
elasticsearchmachine pushed a commit that referenced this issue Feb 4, 2025
@alex-spies
Mute failing date mixed cluster tests (#121648)
2bc0d28 
Mute the tests causing
#121594 to avoid getting
the whole test suite muted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@not-napoleon not-napoleon

Labels
:Analytics/ES|QL AKA ESQL medium-risk An open issue or test failure that is a medium risk to future releases Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@not-napoleon @elasticsearchmachine @alex-spies