Spec failure in `spec/features/profile_spec.rb` | Profile account page when I reset feed token resets feed token
Job #1328575620 failed for 27e6117f:
Trace
Failures:
1) Profile account page when I reset feed token resets feed token
Got 1 failure and 1 other error:
1.1) Failure/Error: expect(page).to have_content 'Feed token was successfully reset'
expected to find text "Feed token was successfully reset" in "Skip to content GitLab Menu Help User Settings Profile Account Applications Chat Access Tokens Emails Password Notifications SSH Keys GPG Keys Preferences Active Sessions Authentication log Usage Quotas Collapse sidebar User Settings Access Tokens Personal Access Tokens You can generate a personal access token for each application you use that needs access to the GitLab API. You can also use personal access tokens to authenticate against Git over HTTP. They are the only accepted password when you have Two-Factor Authentication (2FA) enabled. Add a personal access token Enter the name of your application, and we'll return a unique personal access token. Name Expires at Scopes api Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry. read_user Grants read-only access to the authenticated user's profile through the /user API endpoint, which includes username, public email, and full name. Also grants access to read-only API endpoints under /users. read_api Grants read access to the API, including all groups and projects, the container registry, and the package registry. read_repository Grants read-only access to repositories on private projects using Git-over-HTTP or the Repository Files API. write_repository Grants read-write access to repositories on private projects using Git-over-HTTP (not using the API). Projects Set access permissions for this token. All projects Selected projects Active personal access tokens (0) This user has no active personal access tokens. Feed token Your feed token is used to authenticate you when your RSS reader loads a personalized RSS feed or when your calendar application loads a personalized calendar, and is included in those feed URLs. It cannot be used to access any other data. Feed token Keep this token secret. Anyone who gets ahold of it can read activity and issue RSS feeds or your calendar feed as if they were you. You should reset it if that ever happens."
# ./spec/features/profile_spec.rb:78:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:372:in `block (3 levels) in <top (required)>'
# ./spec/support/sidekiq_middleware.rb:9:in `with_sidekiq_server_middleware'
# ./spec/spec_helper.rb:363:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:359:in `block (3 levels) in <top (required)>'
# ./lib/gitlab/application_context.rb:31:in `with_raw_context'
# ./spec/spec_helper.rb:359:in `block (2 levels) in <top (required)>'
1.2) Failure/Error: raise JSConsoleError, message
JSConsoleError:
Unexpected browser console output:
security - Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'.
security - Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'.
# ./spec/support/capybara.rb:196:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:372:in `block (3 levels) in <top (required)>'
# ./spec/support/sidekiq_middleware.rb:9:in `with_sidekiq_server_middleware'
# ./spec/spec_helper.rb:363:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:359:in `block (3 levels) in <top (required)>'
# ./lib/gitlab/application_context.rb:31:in `with_raw_context'
# ./spec/spec_helper.rb:359:in `block (2 levels) in <top (required)>'
Finished in 19 minutes 37 seconds (files took 44.1 seconds to load)