[
https://issues.apache.org/jira/browse/OPENJPA-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139647#comment-18139647
]
ASF subversion and git services commented on OPENJPA-3028:
----------------------------------------------------------
Commit de8b65e6e6d5618cba8318cc951d37d330049c90 in openjpa's branch
refs/heads/OPENJPA-3028-oracle-functions from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=de8b65e6e ]
[OPENJPA-3028] Run TestEJBQLFunction.testExtractWEEK on Derby
The test still skipped Derby with the comment that Derby has no function
for the ISO week. DerbyDictionary computes the ISO week since #273 (see
TestExtractDateTimeField), so the test now runs on Derby as well.
> 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)
