2020-05-18 - Triage report for "Quality"
Hi, @at.ramya @jo_shih @tpazitny @vincywilson @kwiebers
This is a group or stage level triage report that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
Quality + QA unscheduled issues
-
#217705 (closed) Failure in 8_monitor/all_monitor_features_spec.rb and 8_monitor/all_monitor_core_features_spec.rb / Wait condition not met after 360 seconds on pipeline QA, Quality, devopsmonitor, failurebroken-test, found:master, found:nightly, groupapm, test -
#217438 (closed) Flaky qa/specs/features/browser_ui/4_verify/ci_variable/add_remove_ci_variable_spec.rb:38 ~"P3", QA, Quality, devopsverify, failureflaky-test, found:master, test -
#217295 (closed) 2020-05-11 - Triage report for "Quality" QA, Quality, triage report -
#216929 Consider adding more scenarios for testing Performance bar QA, Quality
-
#216853 (closed) Transient failure in qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb QA, Quality, devopscreate, failureflaky-test, found:staging.gitlab.com, test -
#216622 (closed) Transient failure in qa/specs/features/browser_ui/1_manage/login/log_into_mattermost_via_gitlab_spec.rb QA, Quality, devopsmanage, failureinvestigating, found:master, test -
#216493 (closed) Transient failure in qa/specs/features/browser_ui/7_configure/auto_devops/create_project_with_auto_devops_spec.rb QA, Quality, ~"devops::configure", failureinvestigating, found:master, test -
#216058 (closed) Follow-up from "Refactor KubernetesCluster to base and project" QA, Quality, ~"devops::configure", ~"group::configure", ~"technical debt"
-
#214316 (closed) Develop script with gitlab-qa for auto setup for a monitor project QA, Quality, ~"backstage" -
#213676 (closed) Failure in qa/specs/features/ee/browser_ui/secure/security_reports_spec.rb
expected #has_vulnerability?("Prototype pollution attack in mixin-deep") to return true, got false ~"P1", QA, Quality, failurebroken-test, found:staging.gitlab.com, test -
#213524 (closed) Validate recommended NFS configuration QA, Quality, customer -
#208392 (closed) Run package-and-qa
against merged results QA, Quality, eppipeline
-
#208730 (closed) Schedule master pipeline notifications aren't sent when package-and-qa
fails Engineering Productivity, QA, Quality, ~"Quality:test-infra", eppipeline -
#200068 (closed) Set up load testing for WAF ~"Accepting merge requests", QA, Quality, ~"backstage", ~"devops::defend", ~"group::container security" -
#39121 (closed) Test Plan - Defend / WAF Category:WAF, QA, Quality, ~"devops::defend", test-plan -
#212390 (confidential) ~"(confidential)"
-
#196786 (closed) Document common issues causing nondeterministic E2E tests QA, Quality, missed:12.8, missed:12.9 -
#194311 (closed) Refactor/rewrite spec/services/notification_service_spec.rb Engineering Productivity, ~"P3", QA, Quality, meta -
#43105 (closed) [Reason: Bug in Code] Failure in "./qa/specs/features/ee/browser_ui/3_create/repository/file_locking_spec.rb:62" QA, Quality, ~"bug", devopscreate, found:staging.gitlab.com, test -
#197439 Follow-up from "Move Release.perform_before_hooks
to RSpecbefore(:suite)
hook" QA, Quality, ~"backstage"
Heatmap for triage failures
~S1 | ~S2 | ~S3 | ~S4 | No severity | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 14 |
~P2 | 0 | 0 | 1 | 0 | 8 |
~P3 | 0 | 0 | 0 | 0 | 5 |
~P4 | 0 | 0 | 0 | 0 | 4 |
No priority | 0 | 0 | 0 | 0 | 101 |
Heatmap for all triage failures past SLO
~S1 | ~S2 | ~S3 | ~S4 | No severity | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 1 |
~P2 | 0 | 0 | 0 | 0 | 1 |
~P3 | 0 | 0 | 0 | 0 | 0 |
~P4 | 0 | 0 | 0 | 0 | 1 |
No priority | 0 | 0 | 0 | 0 | 1 |
This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
If assignees or people mentioned in this individual triage report need to be amended, please edit group_definition.rb.