The TCK was failing with 12.0.x because it was using the previous
version of the TCK.
My working theory at this point is that because the TCKs are provided
outside of Maven Central via a download and install process they look
unchanged to the caching mechanism used by Git Actions.
Removing the cache appears to hgave fixed the issue.
We'll see how things go.
Mark
On 19/04/2025 16:56, ma...@apache.org wrote:
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git
The following commit(s) were added to refs/heads/main by this push:
new 58e979b Update ci.yml
58e979b is described below
commit 58e979be2fa61ad5f259e021a96e621bcab2d86d
Author: Mark Thomas
AuthorDate: Sat Apr 19 16:56:32 2025 +0100
Update ci.yml
Attempt to fix current CI failure
Remove Maven cache as old WebSocket TCK is being used.
---
.github/workflows/ci.yml | 1 -
1 file changed, 1 deletion(-)
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index effa95f..364a13c 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -40,7 +40,6 @@ jobs:
with:
java-version: ${{ matrix.java }}
distribution: zulu
-cache: 'maven'
- name: Build
run: mvn verify
- name: Upload logs
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
