Browser test builds for Echo are failing because they have users on beta labs of the form "EchoUserNew<string>" and "EchoUser".
These users need the new passwords and need credentials stashed in Jenkins.
Browser test builds for Echo are failing because they have users on beta labs of the form "EchoUserNew<string>" and "EchoUser".
These users need the new passwords and need credentials stashed in Jenkins.
We rewetted the passwords last week, seems I have missed the EchoUser :-(
The old and new passwords are at https://office.wikimedia.org/wiki/Selenium_passwords and need to be adjusted or created in the Jenkins credentials store.
On beta cluster, the Echo browser test is configured to use Selenium_user and the password in MEDIAWIKI_PASSWORD_SELENIUM_USER_WMFLABS_ORG . When changing to the credential system, I forgot to update the password for EchoUser on beta.
We also noticed the use of two more users: Selenium user chrome and Selenium user firefox. I have updated the password for both of them.
Looking at the Echo browser tests in tests/browser/features/step_definitions/common_steps.rb it has some logic to create users (EchoUser, EchoUser_firefox ...). Those user will need to have their passwords updated based on the old and new passwords listed at https://office.wikimedia.org/wiki/Selenium_passwords