Fixed an issue where ALT+F5 for execute query in Query Tool shows cro… #5300
khushboovashiAnnotations
15 errors and 16 warnings
|
run-python-tests-pg (windows-latest, 16)
Canceling since a higher priority waiting request for Run Python tests on PostgreSQL @ anilsahoo20:GH-9570 exists
|
|
run-python-tests-pg (windows-latest, 16)
The operation was canceled.
|
|
run-python-tests-pg (windows-latest, 14)
Canceling since a higher priority waiting request for Run Python tests on PostgreSQL @ anilsahoo20:GH-9570 exists
|
|
run-python-tests-pg (windows-latest, 14)
The operation was canceled.
|
|
run-python-tests-pg (windows-latest, 17)
Canceling since a higher priority waiting request for Run Python tests on PostgreSQL @ anilsahoo20:GH-9570 exists
|
|
run-python-tests-pg (windows-latest, 17)
The operation was canceled.
|
|
run-python-tests-pg (windows-latest, 18)
Canceling since a higher priority waiting request for Run Python tests on PostgreSQL @ anilsahoo20:GH-9570 exists
|
|
run-python-tests-pg (windows-latest, 18)
The operation was canceled.
|
|
run-python-tests-pg (ubuntu-22.04, 16)
Canceling since a higher priority waiting request for Run Python tests on PostgreSQL @ anilsahoo20:GH-9570 exists
|
|
run-python-tests-pg (ubuntu-22.04, 16)
The operation was canceled.
|
|
run-python-tests-pg (macos-latest, 15)
Canceling since a higher priority waiting request for Run Python tests on PostgreSQL @ anilsahoo20:GH-9570 exists
|
|
run-python-tests-pg (macos-latest, 15)
The operation was canceled.
|
|
run-python-tests-pg (macos-latest, 17)
Canceling since a higher priority waiting request for Run Python tests on PostgreSQL @ anilsahoo20:GH-9570 exists
|
|
run-python-tests-pg (macos-latest, 17)
The operation was canceled.
|
|
Run Python tests on PostgreSQL
Canceling since a higher priority waiting request for Run Python tests on PostgreSQL @ anilsahoo20:GH-9570 exists
|
|
run-python-tests-pg (macos-latest, 14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (macos-latest, 14)
postgresql@14 has been deprecated because it is not supported upstream! It will be disabled on 2026-11-12.
|
|
run-python-tests-pg (ubuntu-22.04, 17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (windows-latest, 15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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-python-tests-pg (macos-latest, 18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (ubuntu-22.04, 15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (ubuntu-22.04, 18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (macos-latest, 16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (ubuntu-22.04, 14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (windows-latest, 16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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-python-tests-pg (windows-latest, 14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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-python-tests-pg (windows-latest, 17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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-python-tests-pg (windows-latest, 18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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-python-tests-pg (ubuntu-22.04, 16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (macos-latest, 15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-python-tests-pg (macos-latest, 17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
regression-log-macos-latest-pg14
|
1.01 MB |
sha256:140b5bf1a50b4985371f600f8f84a546e794e79e5307c041bd2f05e2b6aafac7
|
|
|
regression-log-macos-latest-pg16
|
1.03 MB |
sha256:a38203bc5fd8c518a2c99967670ef67a69b041d713a00e21a09be48019848da2
|
|
|
regression-log-macos-latest-pg18
|
1.03 MB |
sha256:4634b53909442ea218b41c3ab4ed2b2bf8231c8638e8304fb94917b19276f28b
|
|
|
regression-log-ubuntu-22.04-pg14
|
1.06 MB |
sha256:c8a6b62a81cd6784afedf6f75a5632451fc880f0632b73445d56c9cf654900da
|
|
|
regression-log-ubuntu-22.04-pg15
|
1.07 MB |
sha256:366b2d60e722ff93ed4a874b21f4985d6bae38e108792ff6f50b8cb83816e8c0
|
|
|
regression-log-ubuntu-22.04-pg17
|
1.07 MB |
sha256:dc7a053be7f5d0ed526899cd1ec3cfdbfe31e0ddd71321a93130613492c35936
|
|
|
regression-log-ubuntu-22.04-pg18
|
1.07 MB |
sha256:bdeb1dbf5d5480bb82410e32cee5059ecf15a1dd206d74a28ba064eb22ce09fd
|
|
|
regression-log-windows-latest-pg15
|
1.08 MB |
sha256:87749b954e0b33d4ce1a9ca40a66356062010e2faa50f0a4fc7fdc51921f75b5
|
|
|
server-log-macos-latest-pg14
|
363 KB |
sha256:8a31335645a7a84fdcdb80e4e97a6b27ceabca49ad6d96a7d47523d6205fe3a9
|
|
|
server-log-macos-latest-pg16
|
371 KB |
sha256:f628be5b2c7c6ffa9d1a071cf122123c057dd62b9de93504700e827d6395caae
|
|
|
server-log-macos-latest-pg18
|
368 KB |
sha256:870c51bd42796c94f8f3d746ec246f765c642cf7eb8781443cf9048d9c060cb0
|
|
|
server-log-ubuntu-22.04-pg14
|
386 KB |
sha256:4aea9f2cc22e9b0d27de7e6807ae3387bdde6b01b45fc8b85294294db168dab3
|
|
|
server-log-ubuntu-22.04-pg15
|
401 KB |
sha256:25edcfebb5be11997b2b56f4412a205f0bce93dbebbc619cd097b2355575f472
|
|
|
server-log-ubuntu-22.04-pg17
|
400 KB |
sha256:27f03e48f1d4da35824f8439a2ae8dabe7df219fe2887a13eaf2e9576a086287
|
|
|
server-log-ubuntu-22.04-pg18
|
396 KB |
sha256:7404fc0941cfa58953074a62cac05c07709ab3941d9093efb651657539c61159
|
|
|
server-log-windows-latest-pg15
|
592 KB |
sha256:981e809084181065cc13fd33b718d4ade76d869b69348569aaeaf264e2939afb
|
|