Use Checker Framework 3.49.5 #138
mernstAnnotations
13 errors, 6 warnings, and 1 notice
|
android/pom.xml on JDK 11 on ubuntu-latest
Process completed with exit code 1.
|
|
pom.xml on JDK 11 on ubuntu-latest
Process completed with exit code 1.
|
|
pom.xml on JDK 11 on ubuntu-latest
The strategy configuration was canceled because "test.ubuntu-latest_11_android_" failed
|
|
pom.xml on JDK 21 on windows-latest
The operation was canceled.
|
|
pom.xml on JDK 21 on windows-latest
The strategy configuration was canceled because "test.ubuntu-latest_11_android_" failed
|
|
pom.xml on JDK 21 on ubuntu-latest
The operation was canceled.
|
|
pom.xml on JDK 21 on ubuntu-latest
The strategy configuration was canceled because "test.ubuntu-latest_11_android_" failed
|
|
pom.xml on JDK 17 on ubuntu-latest
The operation was canceled.
|
|
pom.xml on JDK 17 on ubuntu-latest
The strategy configuration was canceled because "test.ubuntu-latest_11_android_" failed
|
|
android/pom.xml on JDK 17 on ubuntu-latest
The operation was canceled.
|
|
android/pom.xml on JDK 17 on ubuntu-latest
The strategy configuration was canceled because "test.ubuntu-latest_11_android_" failed
|
|
android/pom.xml on JDK 21 on ubuntu-latest
The operation was canceled.
|
|
android/pom.xml on JDK 21 on ubuntu-latest
The strategy configuration was canceled because "test.ubuntu-latest_11_android_" failed
|
|
android/pom.xml on JDK 11 on ubuntu-latest
Failed to restore: Cache service responded with 400
|
|
pom.xml on JDK 11 on ubuntu-latest
Failed to restore: Cache service responded with 400
|
|
pom.xml on JDK 21 on ubuntu-latest
Failed to restore: Cache service responded with 400
|
|
pom.xml on JDK 17 on ubuntu-latest
Failed to restore: Cache service responded with 400
|
|
android/pom.xml on JDK 17 on ubuntu-latest
Failed to restore: Cache service responded with 400
|
|
android/pom.xml on JDK 21 on ubuntu-latest
Failed to restore: Cache service responded with 400
|
|
pom.xml on JDK 21 on windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|