Master broken by changes on merging release and configure groups
Related gitlab-com/www-gitlab-com!120922 (merged)
This changes are breaking tests in triage-ops
Failures:
1) DevopsLabels DevopsLabels::Context#has_category_label_for_current_stage? returns true if the resource has a stage label and a corresponding category label
Failure/Error: expect(resource).to be_has_category_label_for_current_stage
expected `#<struct labels=[#<struct name="devops::release">, #<struct name="Category:Continuous Delivery">]>.has_category_label_for_current_stage?` to be truthy, got false
# ./spec/lib/devops_labels_spec.rb:523:in `block (4 levels) in <top (required)>'
2) DevopsLabels DevopsLabels::Context#comment_for_intelligent_stage_and_group_labels_inference stage: yes, group: no, category: yes, team: no (50% matching stage) => Group based on stage since feature does not match stage and stage has only one group returns a comment with a /label quick action
Failure/Error: expect(resource.comment_for_intelligent_stage_and_group_labels_inference).to eq %(#{explanation}\n#{label_action})
expected: "Setting label(s) ~\"group::configure\" ~\"section::ops\" based on ~\"devops::configure\" ~\"group::configure\".\n/label ~\"group::configure\" ~\"section::ops\""
got: nil
(compared using ==)
# ./spec/lib/devops_labels_spec.rb:808:in `block (5 levels) in <top (required)>'
3) DevopsLabels DevopsLabels::Context#comment_for_intelligent_stage_and_group_labels_inference stage: yes, group: no, category: yes, team: no (none matching stage) => Group based on stage since feature does not match stage and stage has only one group returns a comment with a /label quick action
Failure/Error: expect(resource.comment_for_intelligent_stage_and_group_labels_inference).to eq %(#{explanation}\n#{label_action})
expected: "Setting label(s) ~\"group::configure\" ~\"section::ops\" based on ~\"devops::configure\" ~\"group::configure\".\n/label ~\"group::configure\" ~\"section::ops\""
got: nil
(compared using ==)
# ./spec/lib/devops_labels_spec.rb:808:in `block (5 levels) in <top (required)>'
4) DevopsLabels DevopsLabels::Context#comment_for_intelligent_stage_and_group_labels_inference stage: yes, group: no, category: yes, team: no (33% matching stage) => Group based on stage since feature does not match stage and stage has only one group returns a comment with a /label quick action
Failure/Error: expect(resource.comment_for_intelligent_stage_and_group_labels_inference).to eq %(#{explanation}\n#{label_action})
expected: "Setting label(s) ~\"group::configure\" ~\"section::ops\" based on ~\"devops::configure\" ~\"group::configure\".\n/label ~\"group::configure\" ~\"section::ops\""
got: nil
(compared using ==)
# ./spec/lib/devops_labels_spec.rb:808:in `block (5 levels) in <top (required)>'
5) DevopsLabels DevopsLabels::Context#stage_has_a_single_group? returns true if the give stage has a single group
Failure/Error: expect(resource.stage_has_a_single_group?('configure')).to be(true)
expected true
got false
# ./spec/lib/devops_labels_spec.rb:658:in `block (4 levels) in <top (required)>'
6) DevopsLabels DevopsLabels::Context#all_category_labels_for_stage returns the stage category labels when given a stage name
Failure/Error: expect(resource.all_category_labels_for_stage('release')).to include('Category:Continuous Delivery', 'Category:Release Evidence')
expected [] to include "Category:Continuous Delivery" and "Category:Release Evidence"
# ./spec/lib/devops_labels_spec.rb:343:in `block (4 levels) in <top (required)>'
Top 10 slowest examples (4.94 seconds, 64.8% of total time):
Triage::AssignDevForVerification#process when there is assignee does not assign dev
2.84 seconds ./spec/processor/assign_dev_for_verification_spec.rb:192
Triage::AssignDevForVerification#process when issue is closed does not assign dev
0.98894 seconds ./spec/processor/assign_dev_for_verification_spec.rb:208
TeeStream.exec writes command stdout and stderr to provided streams
0.26535 seconds ./spec/lib/tee_stream_spec.rb:32
Triage::PercentageRollout with processors having percentage roll out processes the given percentages of events
0.19302 seconds ./spec/triage/percentage_rollout_spec.rb:78
TeeStream.exec captures command status, output and error streams
0.17684 seconds ./spec/lib/tee_stream_spec.rb:21
DevopsLabels.teams_per_user username: "luke", expected_teams: [] returns teams of user
0.11986 seconds ./spec/lib/devops_labels_spec.rb:77
Triage::KeepCacheWarmJob#perform_async schedules next same job
0.10291 seconds ./spec/job/keep_cache_warm_job_spec.rb:53
Triage::KeepCacheWarmJob#perform_async when refreshing raising an error schedules next same job and capture errors
0.10289 seconds ./spec/job/keep_cache_warm_job_spec.rb:69
Triage::CommandMrRequestReview#applicable? when actor is a team member behaves like rate limited does not post a comment if number of commands sent exceeds the allowed limit within the period
0.07311 seconds ./spec/support/rate_limit_shared_examples.rb:4
Triage::CommandMrUnassignReview#applicable? behaves like rate limited does not post a comment if number of commands sent exceeds the allowed limit within the period
0.07148 seconds ./spec/support/rate_limit_shared_examples.rb:4
Top 10 slowest example groups:
Triage::AssignDevForVerification
0.16252 seconds average (3.9 seconds / 24 examples) ./spec/processor/assign_dev_for_verification_spec.rb:9
TeeStream
0.14788 seconds average (0.44363 seconds / 3 examples) ./spec/lib/tee_stream_spec.rb:6
Triage::PercentageRollout
0.06503 seconds average (0.1951 seconds / 3 examples) ./spec/triage/percentage_rollout_spec.rb:8
Triage::KeepCacheWarmJob
0.04267 seconds average (0.21333 seconds / 5 examples) ./spec/job/keep_cache_warm_job_spec.rb:7
Triage::CommandMrUnassignReview
0.00806 seconds average (0.0806 seconds / 10 examples) ./spec/processor/community/command_mr_unassign_review_spec.rb:7
Triage::CommandMrRequestReview
0.00563 seconds average (0.09564 seconds / 17 examples) ./spec/processor/community/command_mr_request_review_spec.rb:7
Triage::Rack::App
0.0055 seconds average (0.011 seconds / 2 examples) ./spec/rack/app_spec.rb:9
FlakyReport
0.00487 seconds average (0.00487 seconds / 1 example) ./spec/lib/flaky_report_spec.rb:6
Triage::CommandMrHelp
0.00458 seconds average (0.06874 seconds / 15 examples) ./spec/processor/community/command_mr_help_spec.rb:7
DiscordMessenger
0.00458 seconds average (0.00916 seconds / 2 examples) ./spec/lib/discord_messenger_spec.rb:6
Finished in 7.62 seconds (files took 2.11 seconds to load)
2716 examples, 6 failures
Failed examples:
rspec ./spec/lib/devops_labels_spec.rb:520 # DevopsLabels DevopsLabels::Context#has_category_label_for_current_stage? returns true if the resource has a stage label and a corresponding category label
rspec './spec/lib/devops_labels_spec.rb[1:7:30:9:1]' # DevopsLabels DevopsLabels::Context#comment_for_intelligent_stage_and_group_labels_inference stage: yes, group: no, category: yes, team: no (50% matching stage) => Group based on stage since feature does not match stage and stage has only one group returns a comment with a /label quick action
rspec './spec/lib/devops_labels_spec.rb[1:7:30:14:1]' # DevopsLabels DevopsLabels::Context#comment_for_intelligent_stage_and_group_labels_inference stage: yes, group: no, category: yes, team: no (none matching stage) => Group based on stage since feature does not match stage and stage has only one group returns a comment with a /label quick action
rspec './spec/lib/devops_labels_spec.rb[1:7:30:12:1]' # DevopsLabels DevopsLabels::Context#comment_for_intelligent_stage_and_group_labels_inference stage: yes, group: no, category: yes, team: no (33% matching stage) => Group based on stage since feature does not match stage and stage has only one group returns a comment with a /label quick action
rspec ./spec/lib/devops_labels_spec.rb:657 # DevopsLabels DevopsLabels::Context#stage_has_a_single_group? returns true if the give stage has a single group
rspec ./spec/lib/devops_labels_spec.rb:342 # DevopsLabels DevopsLabels::Context#all_category_labels_for_stage returns the stage category labels when given a stage name
Randomized with seed 20725