<!--- Before opening a new QA failure issue, make sure to first search for it in the QA failures board: https://gitlab.com/groups/gitlab-org/-/boards/1385578 The issue should have the following: - The relative path of the failing spec file in the title, e.g. if the login test fails, include `qa/specs/features/browser_ui/1_manage/login/log_in_spec.rb` in the title. This is required so that existing issues can easily be found by searching for the spec file. - If the issue is about multiple test failures, include the path for each failing spec file in the description. - A link to the failing job. - The stack trace from the job's logs in the "Stack trace" section below. - A screenshot (if available), and HTML capture (if available), in the "Screenshot / HTML page" section below. ---> ### Summary Job https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/1706669 and https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/1706104 ### Stack trace ``` Failures: 1) API basics user creates a project with a file and deletes them afterwards Failure/Error: expect_status(200) expected: 200 got: 400 (compared using ==) # /usr/local/bundle/gems/airborne-0.3.4/lib/airborne/request_expectations.rb:36:in `expect_status' # ./qa/specs/features/api/3_create/repository/files_spec.rb:27:in `block (2 levels) in <module:QA>' # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run' # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop' # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run' # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry' # ./spec/spec_helper.rb:70:in `block (2 levels) in <top (required)>' # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run' # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop' ``` ### Screenshot / HTML page <!-- Attach the screenshot and HTML snapshot of the page from the job's artifacts: 1. Download the job's artifacts and unarchive them. 1. Open the `gitlab-qa-run-2020-*/gitlab-{ce,ee}-qa-*/{,ee}/{api,browser_ui}/<path to failed test>` folder. 1. Select the `.png` and `.html` files that appears in the job logs (look for `HTML screenshot: /path/to/html/page.html` / `Image screenshot: `/path/to/html/page.png`). 1. Drag and drop them here. Note: You don't need to include a screenshot if the information it contains can be included as text. Include the text instead. E.g., error 500/404, "Retry later" errors, etc. If you include multiple screenshots it can be helpful to hide all but the first in a details/summary element, to avoid excessive scrolling: <details><summary>Expand for screenshot</summary> drag and drop the screenshot here </details> --> ### Possible fixes <!-- Default due date. --> <!-- Base labels. --> <!-- Test failure type label, please use just one.--> <!-- Choose the stage that appears in the test path, e.g. ~"devops::create" for `qa/specs/features/browser_ui/3_create/web_ide/add_file_template_spec.rb`. --> <!-- Select a label for where the failure was found, e.g. if the failure occurred in a nightly pipeline, select ~"found:nightly". --> <!-- https://about.gitlab.com/handbook/engineering/quality/guidelines/#priorities: - ~"priority::1": Tests that are needed to verify fundamental GitLab functionality. - ~"priority::2": Tests that deal with external integrations which may take a longer time to debug and fix. --> <!-- Select the current milestone if ~"priority::1" or the next milestone if ~"priority::2". --> ### Reports (9) 1. 2023-07-14: https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/10601379 (https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/2115149) 1. 2023-08-03: https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/10787894 (https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/2180311) 1. 2023-08-22: https://ops.gitlab.net/gitlab-org/quality/staging-canary/-/jobs/10985926 (https://ops.gitlab.net/gitlab-org/quality/staging-canary/-/pipelines/2241731) 1. 2023-08-23: https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/10996917 (https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/2245131) 1. 2023-09-12: https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/11179379 (https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/2305072) 1. 2023-09-19: https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/11265144 (https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/2330412) 1. 2023-09-20: https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/11271915 (https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/2332301) 1. 2023-11-09: https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/11829283 (https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/2503257) 1. 2023-11-17: https://ops.gitlab.net/gitlab-org/quality/staging-canary/-/jobs/11935508 (https://ops.gitlab.net/gitlab-org/quality/staging-canary/-/pipelines/2536473)