<!--- 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 seeing this failure on dev.gitlab.com https://ops.gitlab.net/gitlab-org/gitlab-qa/-/jobs/1288831 and on master https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/jobs/588310659 ### Stack trace ``` Create Web IDE file templates user adds .gitignore via file template Android Failure/Error: ide.create_new_file_from_template template[:file_name], template[:name] Capybara::ElementNotFound: Unable to find css "[data-qa-selector=\"file_templates_bar\"],.qa-file-templates-bar" # /usr/local/bundle/gems/capybara-3.29.0/lib/capybara/node/finders.rb:296:in `block in synced_resolve' # /usr/local/bundle/gems/capybara-3.29.0/lib/capybara/node/base.rb:83:in `synchronize' # /usr/local/bundle/gems/capybara-3.29.0/lib/capybara/node/finders.rb:287:in `synced_resolve' # /usr/local/bundle/gems/capybara-3.29.0/lib/capybara/node/finders.rb:52:in `find' # /usr/local/bundle/gems/capybara-3.29.0/lib/capybara/session.rb:749:in `block (2 levels) in <class:Session>' # /usr/local/bundle/gems/capybara-3.29.0/lib/capybara/session.rb:340:in `within' # ./qa/page/base.rb:271:in `within_element' # ./qa/support/page/logging.rb:143:in `within_element' # ./qa/page/project/web_ide/edit.rb:72:in `block in create_new_file_from_template' # ./qa/page/base.rb:49:in `block in wait_until' # ./qa/support/waiter.rb:31:in `block in wait_until' # ./qa/support/repeater.rb:22:in `repeat_until' # ./qa/support/waiter.rb:23:in `wait_until' # ./qa/page/base.rb:48:in `wait_until' # ./qa/page/project/web_ide/edit.rb:71:in `create_new_file_from_template' # ./qa/specs/features/browser_ui/3_create/web_ide/add_file_template_spec.rb:53:in `block (5 levels) in <module:QA>' # ./qa/scenario/actable.rb:16:in `perform' # ./qa/specs/features/browser_ui/3_create/web_ide/add_file_template_spec.rb:52:in `block (4 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:69: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' # /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' # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:37:in `block (2 levels) in setup' # ./qa/specs/runner.rb:71:in `perform' # ./qa/scenario/template.rb:10:in `block in perform' # ./qa/scenario/template.rb:8:in `tap' # ./qa/scenario/template.rb:8:in `perform' # ./qa/scenario/template.rb:33:in `perform' # ./qa/scenario/template.rb:10:in `block in perform' # ./qa/scenario/template.rb:8:in `tap' # ./qa/scenario/template.rb:8:in `perform' # ./qa/scenario/bootable.rb:28:in `launch!' ``` ### 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: - ~P1: Tests that are needed to verify fundamental GitLab functionality. - ~P2: Tests that deal with external integrations which may take a longer time to debug and fix. --> <!-- Select the current milestone if ~P1 or the next milestone if ~P2. -->