Failure in spec/ui/page/account_details_page_spec.rb | allows user to update first and last name
### Summary Failing job(s): https://gitlab.com/gitlab-org/customers-gitlab-com/-/jobs/4110738279 Failing spec(s): allows user to update first and last name Corresponding test case(s): https://gitlab.com/gitlab-org/customers-gitlab-com/-/quality/test_cases/2368 ### Stack trace ``` Failure/Error: expect(account_details).to have_success_update Watir::Wait::TimeoutError: timed out after 30 seconds, waiting for true condition on #<Watir::Div: located: false; {:id=>"flash_notice", :text=>/Your account has been updated successfully/, :tag_name=>"div"}> # ./vendor/ruby/2.7.0/gems/watir-7.2.2/lib/watir/wait.rb:43:in `until' # ./vendor/ruby/2.7.0/gems/watir-7.2.2/lib/watir/wait.rb:110:in `wait_until' # ./page/base.rb:215:in `find_element' # ./page/base.rb:42:in `block (3 levels) in singleton class' # ./page/base.rb:53:in `public_send' # ./page/base.rb:53:in `block (3 levels) in singleton class' # ./spec/ui/page/account_details_page_spec.rb:49:in `block (3 levels) in <module:QA>' # ./vendor/ruby/2.7.0/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:124:in `block in run' # ./vendor/ruby/2.7.0/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `loop' # ./vendor/ruby/2.7.0/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `run' # ./vendor/ruby/2.7.0/gems/rspec-retry-0.6.2/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry' # ./vendor/ruby/2.7.0/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:37:in `block (2 levels) in setup' ``` ### Screenshot / HTML page <details><summary>initial</summary> ![allows_user_to_update_first_and_last_name-04132020-913](/uploads/aa97d7e7f99bf10fccd6c3a21d106417/allows_user_to_update_first_and_last_name-04132020-913.png) </details> <details><summary>retry</summary> ![allows_user_to_update_first_and_last_name-04132021-904](/uploads/6a03e90f3b9a3e68a156f33058aaadb8/allows_user_to_update_first_and_last_name-04132021-904.png) </details> ### Possible fixes <!-- Default due date. --> <!-- Base labels. --> <!-- Work classification type label, please apply ignore type label until the investigation is complete and an [issue type](https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification) is determined.--> <!-- Test failure type label, please use just one.--> <!-- Select a label for where the failure was found, e.g. if the failure occurred in a nightly pipeline, select ~"found:nightly". -->
issue