Skip to content
vertx-core (5.x)

Replace Future eventually function argument by a supplier argument #589

Sign in to view logs

Replace Future eventually function argument by a supplier argument

Replace Future eventually function argument by a supplier argument #589

Triggered via pull request August 31, 2023 11:22
@vietjvietj
opened #4828
future-eventually-replace-fn-by-supplier
Status Success
Total duration 15m 35s
Artifacts –

ci-5.x.yml

on: pull_request
Matrix: CI
Deploy  /  Deploy to OSSRH
Deploy / Deploy to OSSRH
Fit to window
Zoom out
Zoom in

Annotations

26 errors and 5 warnings
CI (ubuntu-latest, 11, -PtestDomainSockets) / Run tests
testComplete called after test has completed
CI (ubuntu-latest, 11, -PtestDomainSockets) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11, -PtestDomainSockets) / Run tests
too many aardvarks!
CI (ubuntu-latest, 11, -PtestDomainSockets) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11, -PtestDomainSockets) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11) / Run tests
testComplete called after test has completed
CI (ubuntu-latest, 11) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11) / Run tests
too many aardvarks!
CI (ubuntu-latest, 11) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 17) / Run tests
testComplete called after test has completed
CI (ubuntu-latest, 17) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 17) / Run tests
too many aardvarks!
CI (ubuntu-latest, 17) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 17) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11, -PtestNativeTransport) / Run tests
testComplete called after test has completed
CI (ubuntu-latest, 11, -PtestNativeTransport) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11, -PtestNativeTransport) / Run tests
too many aardvarks!
CI (ubuntu-latest, 11, -PtestNativeTransport) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11, -PtestNativeTransport) / Run tests
expected:<[foo]> but was:<[bar]>
CI (windows-latest, 11) / Run tests
already complete
CI (windows-latest, 11) / Run tests
testComplete called after test has completed
CI (windows-latest, 11) / Run tests
expected:<[foo]> but was:<[bar]>
CI (windows-latest, 11) / Run tests
too many aardvarks!
CI (windows-latest, 11) / Run tests
AsyncTestBaseTest#testAssertionFailedFromMainThread
CI (windows-latest, 11) / Run tests
expected:<[foo]> but was:<[bar]>
CI (ubuntu-latest, 11, -PtestDomainSockets) / Run tests
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/
CI (ubuntu-latest, 11) / Run tests
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/
CI (ubuntu-latest, 17) / Run tests
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/
CI (ubuntu-latest, 11, -PtestNativeTransport) / Run tests
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/
CI (windows-latest, 11) / Run tests
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/