vertx-core (4.x)

Fix a regression in CombinerExecutor implementation introduced with t… #253

Sign in to view logs

Triggered via push August 7, 2023 10:02

vietj

4.x

Status Success

Total duration 23m 17s

Artifacts –

This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci-4.x.yml

on: push

Matrix: Run tests

Deploy to OSSRH

Annotations

25 errors and 6 warnings

Run tests (ubuntu-latest, 8, -PtestNativeTransport)

expected:<[foo]> but was:<[bar]>

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)

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)

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 (ubuntu-latest, 17)

expected:<[foo]> but was:<[bar]>

Run tests (ubuntu-latest, 17)

too many aardvarks!

Run tests (ubuntu-latest, 17)

expected:<[foo]> but was:<[bar]>

Run tests (ubuntu-latest, 17)

expected:<[foo]> but was:<[bar]>

Run tests (ubuntu-latest, 17)

testComplete called after test has completed

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)

AsyncTestBaseTest#testAssertionFailedFromOtherThreadAwaitBeforeAssertAndTestComplete

Run tests (windows-latest, 8)

expected:<[foo]> but was:<[bar]>

Run tests (windows-latest, 8)

expected:<[foo]> but was:<[bar]>

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)

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 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, 17)

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 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 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/