[
https://issues.apache.org/jira/browse/OPENJPA-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139656#comment-18139656
]
ASF subversion and git services commented on OPENJPA-3028:
----------------------------------------------------------
Commit 1a6e5d29c11c6a7e48257bc6d62a741fe4a5aff4 in openjpa's branch
refs/heads/OPENJPA-3028-oracle-unittests from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=1a6e5d29c ]
[OPENJPA-3028] Run the test-oracle-docker profile on Oracle Database Free
The profile used gvenzl/oracle-xe 18.4, which has no arm64 image, and
the ojdbc8 19.3 driver. It now starts gvenzl/oracle-free:23-slim and
tests with ojdbc11 23.26.4.0.0 from Maven Central.
The init script did not take effect: it set processes=250 in the spfile
without restarting the database, and the image now reads its init
scripts from /container-entrypoint-initdb.d. It is replaced by a shell
script that raises processes to 1000 and sessions to 1600 and restarts
the database before the image reports it ready, so the test suite no
longer runs out of connections (ORA-12516/ORA-12519).
The EM Express port 5500 is no longer published, and the build matrix
and TCK runner scripts stop the container by its new name.
Usage:
mvn -N -Ptest-oracle-docker docker:start
mvn install -Ptest-oracle-docker
mvn -N -Ptest-oracle-docker docker:stop
> 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)
