Potential failure in gitlab-qa slack reporting
https://ops.gitlab.net/gitlab-org/quality/production/-/jobs/1084234
Posting Slack message to channel: qa-production
/usr/local/bundle/gems/gitlab-qa-5.4.3/lib/gitlab/qa/report/results_in_issues.rb:108:in `report_test': undefined method `web_url' for #<HTTP::Response:0x0000559ff813ee60> (NoMethodError)
from /usr/local/bundle/gems/gitlab-qa-5.4.3/lib/gitlab/qa/report/results_in_issues.rb:50:in `block (2 levels) in invoke!'
from /usr/local/bundle/gems/nokogiri-1.10.9/lib/nokogiri/xml/node_set.rb:238:in `block in each'
from /usr/local/bundle/gems/nokogiri-1.10.9/lib/nokogiri/xml/node_set.rb:237:in `upto'
from /usr/local/bundle/gems/nokogiri-1.10.9/lib/nokogiri/xml/node_set.rb:237:in `each'
from /usr/local/bundle/gems/gitlab-qa-5.4.3/lib/gitlab/qa/report/results_in_issues.rb:49:in `block in invoke!'
from /usr/local/bundle/gems/gitlab-qa-5.4.3/lib/gitlab/qa/report/results_in_issues.rb:47:in `each'
from /usr/local/bundle/gems/gitlab-qa-5.4.3/lib/gitlab/qa/report/results_in_issues.rb:47:in `invoke!'
from /usr/local/bundle/gems/gitlab-qa-5.4.3/lib/gitlab/qa/reporter.rb:68:in `invoke'
from /usr/local/bundle/gems/gitlab-qa-5.4.3/exe/gitlab-qa-report:9:in `<top (required)>'
from /usr/local/bundle/bin/gitlab-qa-report:23:in `load'
from /usr/local/bundle/bin/gitlab-qa-report:23:in `<main>'
We also sometimes see 500 Internal Server Error
when reporting tests that can't have a testcase
tag, because of a DB timeout that occurs when searching via https://gitlab.com/api/v4/projects/gitlab%2Dorg%2Fquality%2Ftestcases/issues
However the fix for that would be to resolve https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/630 so that we can add test-case links to those tests so the reporter doesn't have to search for them.
Edited by Mark Lapierre