tests: EventsBySliceSpec cache test hardening #1566
build-test.yml
on: pull_request
Checks
2m 54s
Run test with Postgres
4m 39s
Run test with Postgres and JSONB payload
2m 4s
Run test with Postgres and several data partitions
4m 6s
Run tests with Yugabyte
5m 15s
Run test with H2
3m 59s
Run test with SQL Server
4m 31s
Docs
1m 40s
Annotations
40 warnings
|
Docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, coursier/cache-action@1ff273bff02a8787bc9f1877d347948af647956d, coursier/setup-action@7bde40eee928896f074dbb76d22dd772eed5c65f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0grq6aQAAAAAktE4NShtOSq06xS5sdbGGRE0yRURHRTA5MTkARWRnZQ==
|
|
Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0gbq6aQAAAABOe9hBSX10T4+OCTcc031mRE0yRURHRTA5MTkARWRnZQ==
|
|
Docs
Failed to restore: Cache service responded with 400
|
|
Docs
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres and JSONB payload
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, coursier/cache-action@1ff273bff02a8787bc9f1877d347948af647956d, coursier/setup-action@7bde40eee928896f074dbb76d22dd772eed5c65f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run test with Postgres and JSONB payload
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mbq6aQAAAACSlzD1YAdWT6V9SS2u6xQWRE0yRURHRTA3MTQARWRnZQ==
|
|
Run test with Postgres and JSONB payload
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mLq6aQAAAACIRdHZyjiWRrPdzt/MC56lRE0yRURHRTA3MTQARWRnZQ==
|
|
Run test with Postgres and JSONB payload
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres and JSONB payload
Failed to restore: Cache service responded with 400
|
|
Checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, coursier/cache-action@1ff273bff02a8787bc9f1877d347948af647956d, coursier/setup-action@7bde40eee928896f074dbb76d22dd772eed5c65f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Checks
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zLq6aQAAAADDheD7lp1TTrtBlSFIChCJRE0yRURHRTA3MTEARWRnZQ==
|
|
Checks
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0y7q6aQAAAAC30GAZ/D2fQ5Ptg8VssxiTRE0yRURHRTA3MTEARWRnZQ==
|
|
Checks
Failed to restore: Cache service responded with 400
|
|
Checks
Failed to restore: Cache service responded with 400
|
|
Run test with H2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, coursier/cache-action@1ff273bff02a8787bc9f1877d347948af647956d, coursier/setup-action@7bde40eee928896f074dbb76d22dd772eed5c65f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run test with H2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Dbu6aQAAAACBVIjETvi1RpLk1dRl/PNKRE0yRURHRTA4MDkARWRnZQ==
|
|
Run test with H2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0DLu6aQAAAABGpZBy5LcfQZfn04w3Nhr0RE0yRURHRTA4MDkARWRnZQ==
|
|
Run test with H2
Failed to restore: Cache service responded with 400
|
|
Run test with H2
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres and several data partitions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, coursier/cache-action@1ff273bff02a8787bc9f1877d347948af647956d, coursier/setup-action@7bde40eee928896f074dbb76d22dd772eed5c65f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run test with Postgres and several data partitions
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GLu6aQAAAABEyWVAsTGjSr32Ikt6vIITUEhYMzFFREdFMDYwOQBFZGdl
|
|
Run test with Postgres and several data partitions
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GLu6aQAAAACEwxhgRWsWTp8ikeH1TDVRUEhYMzFFREdFMDYwOQBFZGdl
|
|
Run test with Postgres and several data partitions
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres and several data partitions
Failed to restore: Cache service responded with 400
|
|
Run test with SQL Server
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, coursier/cache-action@1ff273bff02a8787bc9f1877d347948af647956d, coursier/setup-action@7bde40eee928896f074dbb76d22dd772eed5c65f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run test with SQL Server
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0LLu6aQAAAABxxu1Q3fBmTbBUiqAWgYIKRE0yRURHRTA5MjIARWRnZQ==
|
|
Run test with SQL Server
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0LLu6aQAAAABNlAsdNfxxRYPDJEv3gk1wRE0yRURHRTA5MjIARWRnZQ==
|
|
Run test with SQL Server
Failed to restore: Cache service responded with 400
|
|
Run test with SQL Server
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, coursier/cache-action@1ff273bff02a8787bc9f1877d347948af647956d, coursier/setup-action@7bde40eee928896f074dbb76d22dd772eed5c65f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run test with Postgres
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NLu6aQAAAAA6ScfuZWJYR4usTWCkWa6rRE0yRURHRTA5MTEARWRnZQ==
|
|
Run test with Postgres
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0M7u6aQAAAAAred1rK3icTJ47AVKWvKWYRE0yRURHRTA5MTEARWRnZQ==
|
|
Run test with Postgres
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres
Failed to restore: Cache service responded with 400
|
|
Run tests with Yugabyte
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, coursier/cache-action@1ff273bff02a8787bc9f1877d347948af647956d, coursier/setup-action@7bde40eee928896f074dbb76d22dd772eed5c65f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run tests with Yugabyte
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Wbu6aQAAAADsnh19CbhRToeJHmhJojZGRE0yRURHRTA4MTEARWRnZQ==
|
|
Run tests with Yugabyte
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0WLu6aQAAAACclaznUFWjR7mTdM1ze6swRE0yRURHRTA4MTEARWRnZQ==
|
|
Run tests with Yugabyte
Failed to restore: Cache service responded with 400
|
|
Run tests with Yugabyte
Failed to restore: Cache service responded with 400
|