[
https://issues.apache.org/jira/browse/OPENJPA-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18140959#comment-18140959
]
ASF subversion and git services commented on OPENJPA-3028:
----------------------------------------------------------
Commit 8d0b489f5b6bc6241e1d2f364b2e892edb445397 in openjpa's branch
refs/heads/OPENJPA-3028-tck-mysql-sequence from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=8d0b489f5 ]
[OPENJPA-3028] Skip the SEQUENCE tests of the TCK on MySQL
MySQL has no sequence objects. The TCK skips its SEQUENCE tests when
db.supports.sequence is false, which its MySQL profile does not set.
> Jakarta Persistence 3.2 TCK failures on Derby, MySQL and SQL Server
> -------------------------------------------------------------------
>
> Key: OPENJPA-3028
> URL: https://issues.apache.org/jira/browse/OPENJPA-3028
> Project: OpenJPA
> Issue Type: Epic
> Reporter: Richard Zowalla
> Assignee: Richard Zowalla
> Priority: Major
> Attachments: run_de.tar.xz, run_ms.tar.xz, run_my.tar.xz,
> run_or.tar.xz
>
>
> Results of the Jakarta Persistence 3.2 TCK with
> {{openjpa-integration/tck/run-tck32.sh}} (reported by Maxim Solodovnik on
> dev@):
> * PostgreSQL 16: passed
> * MySQL 8.4.8: 2134 tests, 43 errors
> * SQL Server 2017-CU12: 2134 tests, 45 errors
> * Derby: 2134 tests, 184 errors
> The sub-tasks group the errors by cause. Several groups show up on more than
> one database. Where the TCK output only says "<test> failed", the cause still
> has to be found from the TCK logs.
> Note: the TCK build does not work with Maven 3.10.0; 3.9.x works.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
