Add ID attribute to a button for starting continuous testing so that DEV UI tests select the button and start testing using DEV UI #52950
phillip-krugerci-actions-incremental.yml
on: pull_request
Configure jobs
16s
Attach pull request number
4s
CI Sanity Check
32s
Matrix: native-tests
Matrix: devtools-tests
Matrix: gradle-tests
Matrix: jvm-tests
Matrix: kubernetes-tests
Matrix: maven-tests
Matrix: platform-tests
Matrix: quickstarts-tests
Matrix: virtual-thread-native-tests
Upload build stats to collector
0s
Build report
28s
Annotations
16 errors, 3 warnings, and 42 notices
|
JVM Tests - JDK 21
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Tests - JDK 21
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Tests - JDK 21
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Tests - JDK 17
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Tests - JDK 17
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Tests - JDK 17
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Tests - JDK 17 Windows
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Tests - JDK 17 Windows
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Tests - JDK 17 Windows
Cannot invoke "io.quarkus.funqy.test.Identity.getName()" because "this.val$name" is null
|
|
JVM Integration Tests - JDK 21
setContextClassLoader
|
|
JVM Integration Tests - JDK 21
setContextClassLoader
|
|
JVM Integration Tests - JDK 21
setContextClassLoader
|
|
JVM Integration Tests - JDK 21
Process completed with exit code 1.
|
|
Native Tests - Data1
Process completed with exit code 1.
|
|
Native Tests - Data7
Process completed with exit code 1.
|
|
JVM Integration Tests - JDK 17
Process completed with exit code 1.
|
|
Gradle Tests - JDK 17 Windows
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
|
JVM Integration Tests - JDK 21
No files were found with the provided path: **/build.log. No artifacts will be uploaded.
|
|
JVM Integration Tests - JDK 17
No files were found with the provided path: **/build.log. No artifacts will be uploaded.
|
|
Configure jobs
Resolving Runs-On configuration with:
|
|
Configure jobs
Resolved configuration:
|
|
Initial JDK 17 Build
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Gradle Tests - JDK 17
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Maven Tests - JDK 17
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Devtools Tests - JDK 17
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Devtools Tests - JDK 21
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Quickstarts Compilation - JDK 17
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
JVM Tests - JDK 21
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
JVM Tests - JDK 17
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
JVM Integration Tests - JDK 21
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Kubernetes Tests - JDK 17
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Kubernetes Tests - JDK 21
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Virtual Thread - Messaging
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
MicroProfile TCKs Tests
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Virtual Thread - Main
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Virtual Thread - Security
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Data1
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Main
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Data2
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Data3
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Data5
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Data4
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Build tools and DevTools
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Data7
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Data6
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Amazon
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Messaging1
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Security1
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Messaging2
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Security2
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Security3
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - HTTP
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Misc1
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Misc2
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Cache
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Observability
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Misc3
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - gRPC
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - Spring
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
Native Tests - AWT, ImageIO and Java2D, Packaging .so files
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
|
JVM Integration Tests - JDK 17
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-reports-2-JVM Integration Tests - JDK 17
Expired
|
6.49 MB |
sha256:4cf2d8b9c618096d61c2c1845e1e696f389fba02a5f291120f084b8396173a90
|
|
|
test-reports-JVM Integration Tests - JDK 17
Expired
|
6.05 MB |
sha256:b18651280044da66262154adbae55f0e0c3a7cf05df9fa71a8cd0b744dfa4717
|
|