Skip to content

chore: Disambiguate release workflow names (#6150) #8382

chore: Disambiguate release workflow names (#6150)

chore: Disambiguate release workflow names (#6150) #8382

Triggered via push February 10, 2025 20:00
Status Success
Total duration 10m 27s
Artifacts

tests.yml

on: push
Tests with Java 17 on windows-latest
9m 45s
Tests with Java 17 on windows-latest
Test with coverage
6m 57s
Test with coverage
Extra checks
5m 17s
Extra checks
Javadoc quality
2m 26s
Javadoc quality
reproducible-builds
2m 52s
reproducible-builds
maven-central-requirements
1m 5s
maven-central-requirements
Codegeneration
1m 34s
Codegeneration
Matrix: test-linux
Fit to window
Zoom out
Zoom in

Annotations

32 warnings
maven-central-requirements
Failed to restore: Cache service responded with 429
maven-central-requirements
Failed to restore: Cache service responded with 429
maven-central-requirements
Failed to restore: Cache service responded with 429
Codegeneration
Failed to restore: Cache service responded with 429
Codegeneration
Failed to restore: Cache service responded with 429
Codegeneration
Failed to restore: Cache service responded with 429
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 restore: Cache service responded with 429
Javadoc quality
Failed to restore: Cache service responded with 429
Javadoc quality
Failed to restore: Cache service responded with 429
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 restore: Cache service responded with 429
reproducible-builds
Failed to restore: Cache service responded with 429
reproducible-builds
Failed to restore: Cache service responded with 429
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 restore: Cache service responded with 429
Extra checks
Failed to restore: Cache service responded with 429
Extra checks
Failed to restore: Cache service responded with 429
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 17 on ubuntu-latest
Failed to restore: Cache service responded with 429
Tests with Java 17 on ubuntu-latest
Failed to restore: Cache service responded with 429
Tests with Java 17 on ubuntu-latest
Failed to restore: Cache service responded with 429
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
Test with coverage
Failed to restore: Cache service responded with 429
Test with coverage
Failed to restore: Cache service responded with 429
Test with coverage
Failed to restore: Cache service responded with 429
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 21 on ubuntu-latest
Failed to restore: Cache service responded with 429
Tests with Java 21 on ubuntu-latest
Failed to restore: Cache service responded with 429
Tests with Java 21 on ubuntu-latest
Failed to restore: Cache service responded with 429
Tests with Java 17 on windows-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
Tests with Java 17 on windows-latest
Cache not found for keys: setup-java-Windows-x64-maven-34a127a379a0f535b74e6f32c31f2ed5b825fb70793cdb2dea274e2a8913c0a8