review: fix: Ensure CU-level elements are included when renaming a top-level type #8472
tests.yml
on: pull_request
Tests with Java 17 on windows-latest
9m 36s
Test with coverage
6m 42s
Extra checks
4m 56s
Javadoc quality
2m 19s
reproducible-builds
2m 56s
maven-central-requirements
1m 15s
Codegeneration
1m 44s
Matrix: test-linux
Annotations
7 warnings
Codegeneration
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
Javadoc quality
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
reproducible-builds
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
Extra checks
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
Tests with Java 21 on ubuntu-latest
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
Test with coverage
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
Tests with Java 17 on ubuntu-latest
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|