Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selenium test errors break periodic/continuous builds. #498

Open
dzlier-gcp opened this issue Nov 25, 2019 · 1 comment
Open

Selenium test errors break periodic/continuous builds. #498

dzlier-gcp opened this issue Nov 25, 2019 · 1 comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern.

Comments

@dzlier-gcp
Copy link
Member

Need to update .kokoro/tests/diff_tests.sh and .kokoro/tests/run_tests.sh to download Selenium chrome driver and provide it as an env var to pass Selenium integration tests.

@dzlier-gcp dzlier-gcp self-assigned this Nov 25, 2019
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Nov 26, 2019
@JustinBeckwith JustinBeckwith added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. and removed 🚨 This issue needs some love. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. triage me I really want to be triaged. labels Jan 13, 2020
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Apr 12, 2020
@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label May 23, 2020
@lesv lesv added type: cleanup An internal cleanup or hygiene concern. and removed 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels May 26, 2020
@lesv
Copy link
Contributor

lesv commented May 26, 2020

  • Is this still an issue?
  • Which samples fail because of this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern.
Projects
None yet
Development

No branches or pull requests

4 participants