X Tutup
Skip to content

chore(build): use Chromium in Travis for JS tests#5393

Closed
marclaval wants to merge 1 commit intoangular:masterfrom
marclaval:chromeInTravis
Closed

chore(build): use Chromium in Travis for JS tests#5393
marclaval wants to merge 1 commit intoangular:masterfrom
marclaval:chromeInTravis

Conversation

@marclaval
Copy link
Copy Markdown
Contributor

No description provided.

@marclaval
Copy link
Copy Markdown
Contributor Author

Chromium 37, it is not really recent version :/
/cc @IgorMinar

@IgorMinar
Copy link
Copy Markdown
Contributor

Good start but why not download the most recent one and stick it into the
Travis cache?
On Thu, Nov 19, 2015 at 4:13 PM Marc Laval notifications@github.com wrote:

Chromium 37, it is not really recent version :/
/cc @IgorMinar https://github.com/IgorMinar


Reply to this email directly or view it on GitHub
#5393 (comment).

@IgorMinar
Copy link
Copy Markdown
Contributor

ping? @Mlaval do you want to fix up this PR?

I think the intention of the change is good.

@IgorMinar IgorMinar added the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label Dec 2, 2015
@IgorMinar IgorMinar assigned IgorMinar and marclaval and unassigned IgorMinar Dec 2, 2015
@IgorMinar IgorMinar added this to the beta.0 milestone Dec 2, 2015
@marclaval marclaval force-pushed the chromeInTravis branch 5 times, most recently from 8a7d037 to 29b7970 Compare December 15, 2015 17:37
@marclaval marclaval added action: review The PR is still awaiting reviews from at least one requested reviewer and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Dec 15, 2015
@marclaval marclaval assigned IgorMinar and unassigned marclaval Dec 15, 2015
@IgorMinar IgorMinar modified the milestone: beta.0 Dec 15, 2015
@jeffbcross
Copy link
Copy Markdown
Contributor

Closing until @Mlaval decides he's interested in this PR again :)

@jeffbcross jeffbcross closed this Feb 1, 2016
@marclaval
Copy link
Copy Markdown
Contributor Author

I forgot this PR. It was ready for review but clearly lacks some explanations.

@IgorMinar
Copy link
Copy Markdown
Contributor

We should make sure that this PR also fixes #6846.

@Mlaval could you please refresh this PR and address the comments I mentioned above? thanks!

@marclaval
Copy link
Copy Markdown
Contributor Author

All good, the latest stable Chromium for Linux is now downloaded and cached.
It is used to run all JS tests. It should solve #6846 as E2E_BROWSERS is also used there.
@IgorMinar would you mind reviewing this PR please?

Some additional information about how the new install_chromium script, which basically follows the instructions to download an old version of Chromium: https://www.chromium.org/getting-involved/download-chromium

  1. It retrieves the current stable version number from https://www.chromium.org/developers/calendar (via the https://omahaproxy.appspot.com/all file), e.g. 359700 for Chromium 48.
  2. It checks the Travis cache for this specific version
  3. If not available, it downloads and caches it, using the "decrement commit number" trick.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you use trap to reliably restore the variable in case one of the above commands fail?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do

@IgorMinar
Copy link
Copy Markdown
Contributor

the rest looks good

@IgorMinar IgorMinar added action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Feb 8, 2016
@IgorMinar IgorMinar assigned marclaval and unassigned IgorMinar Feb 8, 2016
@IgorMinar
Copy link
Copy Markdown
Contributor

@Mlaval can you also please add the description from #5393 (comment) into the install_chromium.sh bash?

.travis.yml Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh. I see!!! sorry. I missed this line. please ignore all of my comments about caching.

@marclaval
Copy link
Copy Markdown
Contributor Author

Comments added where needed.

To get the build number of the latest stable, I didn't use trap but made this part safe. If something goes wrong (404, bad content returned), CHROMIUM_VERSION will correctly defaults to 352221.

@marclaval marclaval added action: review The PR is still awaiting reviews from at least one requested reviewer and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Feb 10, 2016
@marclaval marclaval assigned IgorMinar and unassigned marclaval Feb 10, 2016
@IgorMinar IgorMinar added pr_state: LGTM action: merge The PR is ready for merge by the caretaker labels Feb 11, 2016
@yjbanov yjbanov removed the action: review The PR is still awaiting reviews from at least one requested reviewer label Feb 19, 2016
@yjbanov
Copy link
Copy Markdown
Contributor

yjbanov commented Feb 21, 2016

Any ETA on landing this? It is blocking #6783

@vsavkin
Copy link
Copy Markdown
Contributor

vsavkin commented Mar 1, 2016

Merged via 391a9ed

@vsavkin vsavkin closed this Mar 1, 2016
@yjbanov
Copy link
Copy Markdown
Contributor

yjbanov commented Mar 1, 2016

@vsavkin: Thanks a bunch!

@marclaval marclaval deleted the chromeInTravis branch December 11, 2017 10:10
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

X Tutup