-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[WPE][cross-toolchain-helper] Add chromium to webkitdevci images, port to scarthgap yocto release #30143
Conversation
EWS run on previous version of this PR (hash 48f841d) |
Still a draft, need to test this. |
48f841d
to
09a4366
Compare
EWS run on previous version of this PR (hash 09a4366) |
09a4366
to
e6c2e20
Compare
EWS run on previous version of this PR (hash e6c2e20) |
e6c2e20
to
2fe4766
Compare
EWS run on previous version of this PR (hash 2fe4766) |
2fe4766
to
289fdb9
Compare
EWS run on previous version of this PR (hash 289fdb9)
|
289fdb9
to
3dcf5dd
Compare
EWS run on previous version of this PR (hash 3dcf5dd)
|
3dcf5dd
to
ad61d98
Compare
EWS run on previous version of this PR (hash ad61d98) |
NOTE: The netdata apps_groups.conf has been migrated to the repo which hosts the buildbot/ews scripts for the WebKit Perf bots, doesn't need to be part of the yocto definitions. |
ad61d98
to
28ecd29
Compare
EWS run on previous version of this PR (hash 28ecd29) |
I didn't include chromium for the riscv target, not needed there, but properly ported all targets to scarthgap. |
yes, that make sense. |
28ecd29
to
5bc7779
Compare
EWS run on previous version of this PR (hash 5bc7779) |
Worked: |
Thanks! |
5bc7779
to
9ff9ac0
Compare
EWS run on current version of this PR (hash 9ff9ac0) |
9ff9ac0
to
4dfd0f3
Compare
…t to scarthgap yocto release https://bugs.webkit.org/show_bug.cgi?id=275846 Reviewed by Carlos Alberto Lopez Perez. - Port rpi/riscv targets to latest yocto release (scarthgap) - Include Chromium in the webkitdevci image for the rpi targets, for performance comparisions. Therefore we need a recent clang version - the mickledore yocto release is not sufficient. Furthermore we want to build chromium in the most "fair" way, not using some GCC flavour, but strictly following upstream recommendations, to end up with an unbiased comparision. Covered by CI test infrastructure. * Tools/yocto/meta-openembedded_and_meta-webkit.patch: Added. * Tools/yocto/meta-openembedded_backport-libbacktrace-and-newer-netdata-to-mickledore-branch.patch: Removed. * Tools/yocto/riscv/manifest.xml: * Tools/yocto/rpi/bblayers.conf: * Tools/yocto/rpi/local-rpi3-32bits-mesa.conf: * Tools/yocto/rpi/local-rpi3-32bits-userland.conf: * Tools/yocto/rpi/local-rpi3-64bits-mesa.conf: * Tools/yocto/rpi/local-rpi4-32bits-mesa.conf: * Tools/yocto/rpi/local-rpi4-64bits-mesa.conf: * Tools/yocto/rpi/manifest.xml: * Tools/yocto/targets.conf: Canonical link: https://commits.webkit.org/280438@main
4dfd0f3
to
9c523c6
Compare
Committed 280438@main (9c523c6): https://commits.webkit.org/280438@main Reviewed commits have been landed. Closing PR #30143 and removing active labels. |
9c523c6
9ff9ac0
🧪 gtk-wk2