Skip to content
Housekeeping

Add correct column metadata to all warning checks #3

Sign in to view logs

Add correct column metadata to all warning checks

Add correct column metadata to all warning checks #3

Re-run triggered May 1, 2024 17:18
@rrrenerrrene
#1127
NJichev:add-correct-column-reporting-to-warning-checks
Status Failure
Total duration 42s
Artifacts –

housekeeping.yml

on: pull_request
used mix format
31s
used mix format
tested that for each check there is at least one trigger assertion
18s
tested that for each check there is at least one trigger assertion
tested that for each check all params are covered by tests
24s
tested that for each check all params are covered by tests
all triggers are looked up and confirmed
23s
all triggers are looked up and confirmed
Fit to window
Zoom out
Zoom in

Annotations

10 errors
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.critical/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.notice/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.info/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.error/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.warning/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.emergency/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.warn/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.debug/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L170
test it should report a violation when Logger.log/3 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)
all triggers are looked up and confirmed: test/credo/check/warning/missed_metadata_key_in_logger_config_test.exs#L127
test it should report a violation when Logger.alert/2 is used with disallowed metadata (Credo.Check.Warning.MissedMetadataKeyInLoggerConfigTest)