Skip to content

chromium: build ChromeDriver #34

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

Merged
merged 1 commit into from
Apr 21, 2017
Merged

Conversation

mrchapp
Copy link
Contributor

@mrchapp mrchapp commented Apr 20, 2017

This patch enables the build of ChromeDriver. This comes
in very handy for test automation. More information can
be found here:
https://sites.google.com/a/chromium.org/chromedriver/

Signed-off-by: Daniel Díaz [email protected]


FILES_${PN} = "${bindir}/${BPN} ${datadir}/applications ${sbindir}/ ${libdir}/${BPN}/"
FILES_${PN} += "${bindir} ${libdir}"
FILES_${PN} += "${bindir}/${BPN}/*.pak"
FILES_${PN} += "${bindir}/${BPN}/locales/*.pak"

FILES_${PN}-chromedriver-dbg += "${bindir}/${BPN}/.debug/chromedriver"
Copy link
Member

Choose a reason for hiding this comment

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

Please keep all debug together.

@twoerner
Copy link
Collaborator

By how much does this increase the build time of chromium? If it's a significant amount, it would be better if this were broken out so it is only built for those interested in it specifically.

@mrchapp mrchapp force-pushed the chromedriver-master branch from f49f75b to 0f1c827 Compare April 20, 2017 14:26
@twoerner
Copy link
Collaborator

Or maybe a default-off PACKAGECONFIG?

@fboudra
Copy link

fboudra commented Apr 20, 2017

@mrchapp I prefer if chromedriver is built by default unless the increased build time is significant. In that sense, I do agree with @twoerner . Please share the build time metrics so we can have the full picture.

@otavio
Copy link
Member

otavio commented Apr 20, 2017

Agreed and also a way to disable it might be on package config as well. Be it enabled or not by default.

mrchapp added a commit to mrchapp/meta-96boards that referenced this pull request Apr 20, 2017
This is a temporary bbappend so that ChromeDriver is
included in our builds while this pull request is merged
in upstream meta-browser:
  OSSystems/meta-browser#34

Signed-off-by: Daniel Díaz <[email protected]>
@twoerner
Copy link
Collaborator

twoerner commented Apr 20, 2017

Everyone is welcome, of course, to do their own testing. In my testing I found no increase in overall build time. In fact the time to build with the patch went down by almost a minute. Of course I only did one build of each, but suffice to say it's not impacting build time in my one test at all :-)

current master:
real 47m52.100s
current master + merge request #34:
real 47m12.625s

Methodology:

  1. perform a full core-image-x11 build with chromium added to CORE_IMAGE_EXTRA_INSTALL
  2. $ bitbake -c cleansstate chromium
  3. $ time bitbake chromium (-> time chromium: adding updated version 24.0.1312.52 #1)
  4. $ bitbake -c cleansstate chromium
  5. apply patch
  6. $ time bitbake chromium (-> time Several updates #2)
  7. verify chromedriver was built and packaged

MACHINE = "dragonboard-410c"

@mrchapp
Copy link
Contributor Author

mrchapp commented Apr 20, 2017

@twoerner, fantastic! Lucky you -- my build only took 5 hours and 10 minutes. I added ninja chromedriver as an extra step in do_compile() and that part took 90 seconds. Definitely does not have any significant impact; if anything, it speeds up builds ;)

Would you guys still prefer to add another PACKAGECONFIG for this? Being a separate PACKAGE may suffice, but please advise.

By the way, the .debug part for chromedriver has been fixed, as requested by @otavio, in the original branch (force-pushed, probably messed that one up.)

@otavio
Copy link
Member

otavio commented Apr 21, 2017

Thanks for handling it. I think that adding a build option is worth the work, specially as it is straightforward.

This patch enables the build of ChromeDriver. This comes
in very handy for test automation. More information can
be found here:
  https://sites.google.com/a/chromium.org/chromedriver/

Signed-off-by: Daniel Díaz <[email protected]>
@mrchapp mrchapp force-pushed the chromedriver-master branch from 0f1c827 to d8ca720 Compare April 21, 2017 04:05
@mrchapp
Copy link
Contributor Author

mrchapp commented Apr 21, 2017

Branch refreshed.

mrchapp added a commit to mrchapp/meta-96boards that referenced this pull request Apr 21, 2017
This is a temporary bbappend so that ChromeDriver is
included in our builds while this pull request is merged
in upstream meta-browser:
  OSSystems/meta-browser#34

Signed-off-by: Daniel Díaz <[email protected]>
@otavio otavio merged commit cdb1b11 into OSSystems:master Apr 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants