Bug 256283
| Summary: | [WPE] Add new post-commit bots for performance tests with RPis | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Carlos Alberto Lopez Perez <clopez> |
| Component: | Tools / Tests | Assignee: | Carlos Alberto Lopez Perez <clopez> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | aakash_jain, bugs-noreply, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=256277 https://bugs.webkit.org/show_bug.cgi?id=258038 https://bugs.webkit.org/show_bug.cgi?id=260223 |
||
| Bug Depends on: | 255861 | ||
| Bug Blocks: | 249031 | ||
Carlos Alberto Lopez Perez
Now that the tooling for cross-building WebKit for a target device and running tests with it has landed (see bug 249031) it is time to add the bots
The main idea for the bots is the following
1) Build-only bot
- A bot (x86_64) will cross-build WPE for a specific target board like any of this: rpi3-32bits-mesa-vc4, rpi3-32bits-userland, rpi4-32bits-mesa-vc4, rpi3-64bits-mesa-vc4, rpi4-64bits-mesa-vc4
- The bot will also generate the image (OS) that will run on the board. This image will contain everything needed except WPE itself
2) Test-only bots
- This will be a set of RPis boards, each one will boot the image that was generated from the build-only boot (via NFS/tftp)
- The RPi will download the built-product from the test-only boot and run the performance tests
- For running the performance tests it will use the script browserperfdash-benchmark which is a wrapper around the script run-benchmark
- The results of the benchmarks will be uploaded to https://browserperfdash.igalia.com/
The proposed initial config contain this:
1) Two build-only bots for two build configurations:
- WPE-Linux-RPi4-32bits-Mesa-Release-Perf-Build (builds with --cross-target=rpi4-32bits-mesa)
- WPE-Linux-RPi4-64bits-Mesa-Release-Perf-Build (builds with --cross-target=rpi4-64bits-mesa)
2) 16 RPi4 testers for that configurations:
- 8 RPi4 for the 32 bits config
- 8 Rpi4 for the 64 bits config
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Carlos Alberto Lopez Perez
Now that the tooling for cross-building WebKit for a target device and running tests with it has landed (see bug 249031) it is time to add the bots
The main idea for the bots is the following
1) Build-only bot
- A bot (x86_64) will cross-build WPE for a specific target board like any of this: rpi3-32bits-mesa-vc4, rpi3-32bits-userland, rpi4-32bits-mesa-vc4, rpi3-64bits-mesa-vc4, rpi4-64bits-mesa-vc4
- The bot will also generate the image (OS) that will run on the board. This image will contain everything needed except WPE itself
2) Test-only bots
- This will be a set of RPis boards, each one will boot the image that was generated from the build-only boot (via NFS/tftp)
- The RPi will download the built-product from the build-only bot (point 1 above) and run the performance tests
- For running the performance tests it will use the script browserperfdash-benchmark which is a wrapper around the script run-benchmark
- The results of the benchmarks will be uploaded to https://browserperfdash.igalia.com/
The proposed initial config contain this:
1) Two build-only bots for two build configurations:
- WPE-Linux-RPi4-32bits-Mesa-Release-Perf-Build (builds with --cross-target=rpi4-32bits-mesa)
- WPE-Linux-RPi4-64bits-Mesa-Release-Perf-Build (builds with --cross-target=rpi4-64bits-mesa)
2) 16 RPi4 testers for that configurations:
- 8 RPi4 for the 32 bits config
- 8 Rpi4 for the 64 bits config
Carlos Alberto Lopez Perez
Pull request: https://github.com/WebKit/WebKit/pull/13430
EWS
Committed 264798@main (e7e596ed660c): <https://commits.webkit.org/264798@main>
Reviewed commits have been landed. Closing PR #13430 and removing active labels.
Radar WebKit Bug Importer
<rdar://problem/110120132>
Aakash Jain
Restarted build.webkit.org to pick up this change this morning.