Bug #42607
closed
mgr/dashboard: dashboard e2e Jenkins job failures on Nautilus backport PRs
Added by Laura Paduano over 4 years ago.
Updated about 3 years ago.
- Description updated (diff)
I think that running:
```
npx webdriver-manager update --versions.chrome=$(google-chrome --version | awk '{ print $3 }')
```
before ```npm run e2e:ci -- --webdriverUpdate=false``` solves the problem as it aligns the chromedriver version with chrome browser version.
Notice that we are adding the flag ```--webdriverUpdate=false``` so the chromedriver is not updated after the aforementioned command.
We can add this in master and then backport it to nautilus.
We can add this in master and then backport it to nautilus.
I vote for this to do it automatically. I sometimes need to do that manually in my Docker environment when the Chrome package has been updated.
- Description updated (diff)
- Status changed from New to Fix Under Review
- Pull request ID set to 31352
- Target version changed from v14.2.5 to v15.0.0
- Backport set to nautilus
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #42621: nautilus: mgr/dashboard: dashboard e2e Jenkins job failures on Nautilus backport PRs added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
- Status changed from Resolved to Pending Backport
- Backport changed from nautilus to nautilus, mimic
- Copied to Backport #45917: mimic: mgr/dashboard: dashboard e2e Jenkins job failures on Nautilus backport PRs added
- Status changed from Pending Backport to Resolved
- Project changed from mgr to Dashboard
- Category changed from 151 to Testing & QA
Also available in: Atom
PDF