Skip to content

Fix nativeTest failing due to class changes#34951

Merged
terrymanu merged 1 commit intoapache:masterfrom
linghengqian:fix-native
Mar 11, 2025
Merged

Fix nativeTest failing due to class changes#34951
terrymanu merged 1 commit intoapache:masterfrom
linghengqian:fix-native

Conversation

@linghengqian
Copy link
Member

@linghengqian linghengqian commented Mar 11, 2025

Fixes https://github.com/apache/shardingsphere/actions/runs/13765475376 .

Changes proposed in this pull request:

  • Fix nativeTest failing due to class changes.
  • Bump GraalVM Native Build Tools to 0.10.5.
  • Bump GraalVM SDK for org.apache.shardingsphere:shardingsphere-infra-expr-espresso to 24.1.2.
  • Another particular issue is that HiveServer2's insert efficiency is particularly slow after Could not create table after logic database created for MySQL #34816 was fixed, resulting in the need to set max-tolerate-time-difference-milliseconds. This problem does not occur on mysql, postgres, clickhouse, h2database, firebird, opengauss and ms sql server. Maybe something happened inside hiveserver2 .
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 53.07 s <<< FAILURE! -- in org.apache.shardingsphere.test.natived.jdbc.databases.hive.AcidTableTest
[ERROR] org.apache.shardingsphere.test.natived.jdbc.databases.hive.AcidTableTest.assertShardingInLocalTransactions -- Time elapsed: 53.06 s <<< ERROR!
java.sql.SQLException: Algorithm 'Object.SNOWFLAKE' execute failed, reason is: Clock is moving backwards, last time is 1741618344711 milliseconds, current time is 1741618343387 milliseconds..
        at org.apache.shardingsphere.infra.exception.core.external.sql.ShardingSphereSQLException.toSQLException(ShardingSphereSQLException.java:81)
        at org.apache.shardingsphere.infra.exception.dialect.SQLExceptionTransformEngine.toSQLException(SQLExceptionTransformEngine.java:54)
        at org.apache.shardingsphere.driver.jdbc.core.statement.ShardingSpherePreparedStatement.executeUpdate(ShardingSpherePreparedStatement.java:229)
        at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeUpdate(ProxyPreparedStatement.java:61)
        at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeUpdate(HikariProxyPreparedStatement.java)
        at org.apache.shardingsphere.test.natived.commons.repository.OrderItemRepository.insert(OrderItemRepository.java:248)
        at org.apache.shardingsphere.test.natived.commons.TestShardingService.insertData(TestShardingService.java:153)
        at org.apache.shardingsphere.test.natived.commons.TestShardingService.processSuccessInHive(TestShardingService.java:122)
        at org.apache.shardingsphere.test.natived.jdbc.databases.hive.AcidTableTest.assertShardingInLocalTransactions(AcidTableTest.java:95)
        at java.base/java.lang.reflect.Method.invoke(Method.java:580)
        at java.base/java.util.ArrayList.forEach(ArrayList.java:1597)
        at java.base/java.util.ArrayList.forEach(ArrayList.java:1597)

Before committing this PR, I'm sure that I have checked the following options:

  • My code follows the code of conduct of this project.
  • I have self-reviewed the commit code.
  • I have (or in comment I request) added corresponding labels for the pull request.
  • I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
  • I have made corresponding changes to the documentation.
  • I have added corresponding unit tests for my changes.
  • I have updated the Release Notes of the current development version. For more details, see Update Release Note

@linghengqian linghengqian marked this pull request as ready for review March 11, 2025 05:47
@terrymanu terrymanu merged commit de02091 into apache:master Mar 11, 2025
148 checks passed
@linghengqian linghengqian deleted the fix-native branch March 11, 2025 11:12
@linghengqian linghengqian added this to the 5.5.3 milestone May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants