fix #4660: incrementing the fetch for ping/pong #2640
Annotations
29 errors and 5 warnings
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
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)
Java heap space
|
Run tests (ubuntu-latest, 8)
Java heap space
|
Run tests (ubuntu-latest, 8)
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)
testComplete called after test has completed
|
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, 17)
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 (windows-latest, 8)
already complete
|
Run tests (windows-latest, 8)
testComplete called after test has completed
|
Run tests (windows-latest, 8)
AsyncTestBaseTest#testNoAssertionsNoTestComplete
|
Run tests (windows-latest, 8)
too many aardvarks!
|
Run tests (windows-latest, 8)
AsyncTestBaseTest#testAssertionFailedFromMainThread
|
Run tests (windows-latest, 8)
expected:<[foo]> but was:<[bar]>
|
Run tests (windows-latest, 8)
Process completed with exit code 1.
|
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-java@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
Run tests (ubuntu-latest, 8)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-java@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-java@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
Run tests (ubuntu-latest, 17)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-java@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
Run tests (windows-latest, 8)
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-java@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|