Skip to content
vertx-core (4.x)

CompositeFuture should support custom future implementations (#5401) #1258

Sign in to view logs

CompositeFuture should support custom future implementations (#5401)

CompositeFuture should support custom future implementations (#5401) #1258

Triggered via push November 21, 2024 13:47
@tsegismonttsegismont
pushed 0b41047
4.x
Status Success
Total duration 18m 50s
Artifacts –

ci-4.x.yml

on: push
Matrix: Run tests
Deploy to OSSRH
58s
Deploy to OSSRH
Fit to window
Zoom out
Zoom in

Annotations

26 errors and 12 warnings
Run tests (ubuntu-latest, 21)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 21)
too many aardvarks!
Run tests (ubuntu-latest, 21)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 21)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 21)
testComplete called after test has completed
Run tests (ubuntu-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8)
too many aardvarks!
Run tests (ubuntu-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
AsyncTestBaseTest#testAssertionFailedFromMainThreadWithNoTestComplete
Run tests (ubuntu-latest, 8)
testComplete called after test has completed
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
too many aardvarks!
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
testComplete called after test has completed
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
too many aardvarks!
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
testComplete called after test has completed
Run tests (windows-latest, 8)
already complete
Run tests (windows-latest, 8)
testComplete called after test has completed
Run tests (windows-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (windows-latest, 8)
too many aardvarks!
Run tests (windows-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (windows-latest, 8)
expected:<[foo]> but was:<[bar]>
Run tests (ubuntu-latest, 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests (ubuntu-latest, 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run tests (ubuntu-latest, 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests (ubuntu-latest, 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run tests (windows-latest, 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests (windows-latest, 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy to OSSRH
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy to OSSRH
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/