One comment about the actual expiry date for a crash we are ignoring.

Diff comments:

> diff --git a/profiles/ubuntu-jammy-lunar-desktop-amd64_qemu.yaml 
> b/profiles/ubuntu-jammy-lunar-desktop-amd64_qemu.yaml
> index 29b866b..84ff197 100644
> --- a/profiles/ubuntu-jammy-lunar-desktop-amd64_qemu.yaml
> +++ b/profiles/ubuntu-jammy-lunar-desktop-amd64_qemu.yaml
> @@ -21,4 +21,11 @@
>      - "check-conffile-prompt"
>      - "check-var-crash-empty"
>  
> +  scripts_data:
> +    var_crash_ignore_list:
> +      - pattern: "_usr_libexec_tracker-extract-3.130.crash"
> +        expiry_date: "2024-02-19"

This is probably coincidental but I think having the expiry date being the 
Sunday / Monday closest to 30 days is appropriate as it increases the likely 
hood we'll act on it as opposed to a Friday, but I could be wrong.

> +        bug_link: 
> "https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2049907";
> +
> +
>    run_system_tests: true


-- 
https://code.launchpad.net/~hyask/auto-upgrade-testing-specifications/+git/auto-upgrade-testing-specifications/+merge/458928
Your team Canonical Platform QA Team is requested to review the proposed merge 
of ~hyask/auto-upgrade-testing-specifications:skia/var_crash_ignore_list into 
auto-upgrade-testing-specifications:main.


-- 
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to     : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help   : https://help.launchpad.net/ListHelp

Reply via email to