Skip to content

[Backport 1.8.latest] [Bug] Fix scenarios where --empty flag pushes limit 0 into metadata queries #11294

[Backport 1.8.latest] [Bug] Fix scenarios where --empty flag pushes limit 0 into metadata queries

[Backport 1.8.latest] [Bug] Fix scenarios where --empty flag pushes limit 0 into metadata queries #11294

Triggered via pull request October 11, 2024 21:38
Status Success
Total duration 21m 20s
Artifacts 2

integration.yml

on: pull_request_target
test-metadata
7s
test-metadata
Matrix: test
require-label-comment
8s
require-label-comment
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
snowflake / python 3.8 / ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "integration_results_3.8_ubuntu-latest_snowflake-2024-10-11T21_59_17.csv", "logs". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
integration_results_3.8_ubuntu-latest_snowflake-2024-10-11T21_59_17.csv Expired
76.5 KB
logs Expired
7.57 MB