Fixed python & feature test failures caused by Werkzeug 3.1.7 rejecting empty Host header in CSRF token generation. #5287
anilsahoo20Annotations
15 errors and 16 warnings
|
run-python-tests-pg (macos-latest, 17)
Process completed with exit code 2.
|
|
run-python-tests-pg (macos-latest, 14)
Process completed with exit code 2.
|
|
run-python-tests-pg (macos-latest, 15)
Process completed with exit code 2.
|
|
run-python-tests-pg (macos-latest, 18)
Process completed with exit code 2.
|
|
run-python-tests-pg (ubuntu-22.04, 16)
Process completed with exit code 2.
|
|
run-python-tests-pg (ubuntu-22.04, 17)
Process completed with exit code 2.
|
|
run-python-tests-pg (ubuntu-22.04, 18)
Process completed with exit code 2.
|
|
run-python-tests-pg (macos-latest, 16)
Process completed with exit code 2.
|
|
run-python-tests-pg (ubuntu-22.04, 14)
Process completed with exit code 2.
|
|
run-python-tests-pg (windows-latest, 14)
Process completed with exit code 1.
|
|
run-python-tests-pg (windows-latest, 18)
Process completed with exit code 1.
|
|
run-python-tests-pg (windows-latest, 16)
Process completed with exit code 1.
|
|
run-python-tests-pg (windows-latest, 15)
Process completed with exit code 1.
|
|
run-python-tests-pg (windows-latest, 17)
Process completed with exit code 1.
|
|
run-python-tests-pg (ubuntu-22.04, 15)
Process completed with exit code 2.
|
|
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/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, 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. 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 (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/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. 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/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, 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 (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. 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, 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. 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/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 (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/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 (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 (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/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 (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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
regression-log-macos-latest-pg14
|
425 KB |
sha256:fc92d1e8011de2b22ec17a973fdeac5135a43627b18f43410aafbf6206d6b1ea
|
|
|
regression-log-macos-latest-pg15
|
438 KB |
sha256:a82af711fcec21a29d634620436b8a214c6dd8a2c73ed9bfa5b15887d9bd6480
|
|
|
regression-log-macos-latest-pg16
|
439 KB |
sha256:bb563f7bf84488319fc357006c6cb4f8b786914c9991a07f7ce72d6b41098fe9
|
|
|
regression-log-macos-latest-pg17
|
436 KB |
sha256:f87eb01b8d2916ca63f1b151a5cce3951cd5f878cab54eb7827cbe663c1a2a63
|
|
|
regression-log-macos-latest-pg18
|
442 KB |
sha256:5ea3bc21a7198e8542e536480e615fa1aa7b130e84ed81d2dd12a1ff0b70f39b
|
|
|
regression-log-ubuntu-22.04-pg14
|
467 KB |
sha256:23e0892ded2a1fc96acd3f5b8b0daa9d3392814c56d3145ff5002b713b4906bc
|
|
|
regression-log-ubuntu-22.04-pg15
|
475 KB |
sha256:4242cc4f7fd883387c977e5bb3fa8e5da7d8abc74a3e6db89cfe8c8f1afeb623
|
|
|
regression-log-ubuntu-22.04-pg16
|
476 KB |
sha256:10de02c2aede593f4c5bf407f11b2405afa7edb0f5622000a76b3609896e957a
|
|
|
regression-log-ubuntu-22.04-pg17
|
474 KB |
sha256:e41580af6fb73e9f74cc3b5c4bdf2f73f99cfc98355a17d3962527d2da3ebf15
|
|
|
regression-log-ubuntu-22.04-pg18
|
476 KB |
sha256:1883e27d8dc835eb49bbab07255ba29253fe59b2bb3459ba6d61648a31b4fe58
|
|
|
regression-log-windows-latest-pg14
|
461 KB |
sha256:d7400433c15ce7ff7c98c018f865fdde2f16524b7e9a2a480b65eed8201027db
|
|
|
regression-log-windows-latest-pg15
|
469 KB |
sha256:341c66b8ca8a9934d8e6c872c53298c2edda1e493a9d607efd3a1a2e474013e3
|
|
|
regression-log-windows-latest-pg16
|
471 KB |
sha256:f5159c0e15d8a0e5596c4f4e30c223e4c84d519634bc7307bf2b3e527ffec653
|
|
|
regression-log-windows-latest-pg17
|
472 KB |
sha256:1cda7c3c3afa347f9a53b5031804e0b5a00aa8bebda08f0a8dce67b1cd2e98cc
|
|
|
regression-log-windows-latest-pg18
|
470 KB |
sha256:80b232c4319519e3be9eeea0a8689f874f98985457821d5594bffbf66abe60d1
|
|
|
server-log-macos-latest-pg14
|
317 KB |
sha256:a98c73a43c36f555372e5a4612ae5339b317b47cbe3861dab489ba82fe6a6c4f
|
|
|
server-log-macos-latest-pg15
|
323 KB |
sha256:d3f36d938c7751a13e52b1da49578245660c18fc6ca87ac9b2a422653883241e
|
|
|
server-log-macos-latest-pg16
|
325 KB |
sha256:387ae5ab3e9d51b531da801148413d6c63e48d43032122b3d230d8f6115fa778
|
|
|
server-log-macos-latest-pg17
|
323 KB |
sha256:f39987f83aed7e1edbec5bc1fd9027340315c911b592a93ade011badd04c40d6
|
|
|
server-log-macos-latest-pg18
|
326 KB |
sha256:215ab09461f5233abaf5d0044ba32ae2b38b642d5a65f9283dc244649107f0ad
|
|
|
server-log-ubuntu-22.04-pg14
|
334 KB |
sha256:ea2ca7b6f3801a7ff60d323e5e9ee5fbb5719253054dbc6602514bc4cb790e3b
|
|
|
server-log-ubuntu-22.04-pg15
|
341 KB |
sha256:170987d6832adb52de827d672278c3eafee4a21b697e46b4f5b14e38770007d6
|
|
|
server-log-ubuntu-22.04-pg16
|
342 KB |
sha256:4f8ebdde3d9c6913a4c7af59495ebca15d20372ba35a9ad184cf9bd966b2274e
|
|
|
server-log-ubuntu-22.04-pg17
|
342 KB |
sha256:37ac7f76387459c4e460330f52d17310eeeb014290b908bba62583d6c388184f
|
|
|
server-log-ubuntu-22.04-pg18
|
343 KB |
sha256:4288ba168ce4e6afb8818c6c547fc10ae06bc272969c67e6eadc3524950569c8
|
|
|
server-log-windows-latest-pg14
|
339 KB |
sha256:016a96b96da306a6de0547812b192c732c2eb16f59d0f5f45c23b387632a9608
|
|
|
server-log-windows-latest-pg15
|
350 KB |
sha256:2d629c2eb802bce5570aa4a028eb757e29de00494ec0a006fb438d6fda7edfc3
|
|
|
server-log-windows-latest-pg16
|
351 KB |
sha256:e18b291acd052b58860a26a11b670708474dea73b7acc2fb7f5a1fe14c5ee299
|
|
|
server-log-windows-latest-pg17
|
352 KB |
sha256:cffa6ce6a6235027e93219a2b442ee727eab10bf6f8f0a7ac24467e30f2307f3
|
|
|
server-log-windows-latest-pg18
|
351 KB |
sha256:b31ae92cb2bd429b3c44cae7457f183733ddea081688ed983a616b9db4bfae63
|
|