You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are no tests that check if filtering vdk_step_name and vdk_step_type works correctly. This is not easy to do, because vdk_step_name and file_name often have the same value. We might have to change how the step name is displayed, so that it's not the same as the file name.
Filtering these two fields doesn't work correctly for json format. This is most likely due to the fact that we're adding the fields directly in the run_step hook, which executes after everything else has been filtered in the run_job hook.
Acceptance criteria
vdk_step_name and vdk_step_type added to functional tests for filtering
bugs with json formatting fixed
The text was updated successfully, but these errors were encountered:
DeltaMichael
changed the title
vdk-structlog: add vdk_step_name to tests
vdk-structlog: add vdk_step_name and vdk_step_type to tests
Nov 3, 2023
DeltaMichael
changed the title
vdk-structlog: add vdk_step_name and vdk_step_type to tests
vdk-structlog: add vdk_step_name and vdk_step_type to tests and fix filtering bugs
Nov 3, 2023
## Why?
Filtering by timestamp, level and vdk_job_name does not work for json
formatting
## What?
- Introduce logic that inserts the correct fields in the json formatter
log record
- Move the metadata filters after the filters that add the job name
- Fix bug in ConsoleMetadataFilters
- Add timestamp to tests
- Enable json tests
## How was this tested?
Ran functional tests locally
## What kind of change is this?
Bugfix
## Follow-up
#2875
Signed-off-by: Dilyan Marinov <[email protected]>
Overview
There are no tests that check if filtering
vdk_step_name
andvdk_step_type
works correctly. This is not easy to do, becausevdk_step_name
andfile_name
often have the same value. We might have to change how the step name is displayed, so that it's not the same as the file name.Filtering these two fields doesn't work correctly for json format. This is most likely due to the fact that we're adding the fields directly in the run_step hook, which executes after everything else has been filtered in the run_job hook.
Acceptance criteria
vdk_step_name
andvdk_step_type
added to functional tests for filteringThe text was updated successfully, but these errors were encountered: