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

[Backport 2.7] [CI] setup Chrome and utilize binary path #4014

Merged
merged 2 commits into from
May 17, 2023

Conversation

opensearch-trigger-bot[bot]
Copy link
Contributor

Backport 0188d05 from #3997.

Within the CI, the virtual runner that we are utilizing has Chrome
installed already. The version of Chrome is installed periodically.

The most recent version of Chrome requires updates to dependencies
that drop support for Node 14.

This downloads chrome in the CI and then checks the chromedriver
from the environment variable `TEST_BROWSER_BINARY_PATH`.

Signed-off-by: Kawika Avilla <[email protected]>
(cherry picked from commit 0188d05)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

# Conflicts:
#	CHANGELOG.md
@codecov
Copy link

codecov bot commented May 12, 2023

Codecov Report

Merging #4014 (8a2d894) into 2.7 (f9713f0) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              2.7    #4014   +/-   ##
=======================================
  Coverage   66.44%   66.45%           
=======================================
  Files        3229     3229           
  Lines       62045    62045           
  Branches     9597     9597           
=======================================
+ Hits        41226    41232    +6     
+ Misses      18517    18513    -4     
+ Partials     2302     2300    -2     
Flag Coverage Δ
Linux 66.40% <ø> (+<0.01%) ⬆️
Windows 66.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 3 files with indirect coverage changes

@joshuarrrr joshuarrrr added the not in release PRs backported to already shipped releases with no future release planned label May 12, 2023
@abbyhu2000 abbyhu2000 self-assigned this May 16, 2023
@abbyhu2000 abbyhu2000 added the Skip-Changelog PRs that are too trivial to warrant a changelog or release notes entry label May 16, 2023
@kavilla kavilla merged commit 5d4feb2 into 2.7 May 17, 2023
@github-actions github-actions bot deleted the backport/backport-3997-to-2.7 branch May 17, 2023 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not in release PRs backported to already shipped releases with no future release planned Skip-Changelog PRs that are too trivial to warrant a changelog or release notes entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants