Skip to content

[CI] JdbcFrozenCsvSpecIT class failing #116736

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

Open
elasticsearchmachine opened this issue Nov 13, 2024 · 4 comments
Open

[CI] JdbcFrozenCsvSpecIT class failing #116736

elasticsearchmachine opened this issue Nov 13, 2024 · 4 comments
Labels
:Analytics/SQL SQL querying low-risk An open issue or test failure that is a low 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 Nov 13, 2024

Build Scans:

Reproduction Line:

./gradlew ':x-pack:plugin:sql:qa:server:single-node:javaRestTest' --tests "org.elasticsearch.xpack.sql.qa.single_node.JdbcFrozenCsvSpecIT" -Dtests.method="test {frozen.testShowTables}" -Dtests.seed=1AE51B51242CC4AB -Dtests.locale=ca-ES -Dtests.timezone=Africa/Dar_es_Salaam -Druntime.java=22

Applicable branches:
7.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.sql.SQLException: Server sent bad type [x_content_parse_exception]. Original type was [[-1:71] [sql/query] failed to parse field [time_zone]]. [org.elasticsearch.xcontent.XContentParseException: [-1:71] [sql/query] failed to parse field [time_zone]
	at org.elasticsearch.xcontent.ObjectParser.throwFailedToParse(ObjectParser.java:609)
	at org.elasticsearch.xcontent.ObjectParser.parseValue(ObjectParser.java:604)
	at org.elasticsearch.xcontent.ObjectParser.parseSub(ObjectParser.java:652)
	at org.elasticsearch.xcontent.ObjectParser.parse(ObjectParser.java:320)
	at org.elasticsearch.xcontent.ObjectParser.parse(ObjectParser.java:260)
	at org.elasticsearch.xcontent.ObjectParser.apply(ObjectParser.java:393)
	at org.elasticsearch.xpack.sql.action.SqlQueryRequest.fromXContent(SqlQueryRequest.java:335)
	at org.elasticsearch.xpack.sql.plugin.RestSqlQueryAction.prepareRequest(RestSqlQueryAction.java:51)
	at org.elasticsearch.rest.BaseRestHandler.handleRequest(BaseRestHandler.java:86)
	at org.el
[truncated]

Issue Reasons:

  • [7.17] 3 failures in class org.elasticsearch.xpack.sql.qa.single_node.JdbcFrozenCsvSpecIT (2.6% fail rate in 117 executions)
  • [7.17] 2 failures in pipeline elasticsearch-periodic-platform-support (50.0% fail rate in 4 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Nov 13, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-delivery (Team:Delivery)

@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Nov 13, 2024
@mark-vieira mark-vieira added :Analytics/SQL SQL querying and removed :Delivery/Build Build or test infrastructure labels Nov 18, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Nov 18, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine removed the Team:Delivery Meta label for Delivery team label Nov 18, 2024
@alex-spies alex-spies added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Nov 19, 2024
@alex-spies
Copy link
Contributor

Looks like that's due to the timezone renaming from Europe/Kiev to Europe/Kyiv.

Since this is a narrow edge case, I think this is low risk.

@alex-spies
Copy link
Contributor

I think this is a duplicate of #111214. I'm keeping this open so the bot doesn't come and open a new issue every now and then when this leads to a test failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/SQL SQL querying low-risk An open issue or test failure that is a low 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
Development

No branches or pull requests

3 participants