1429203 - Windows clang+lld builds on AWFY

Status: RESOLVED WORKSFORME

(Testing Graveyard :: AWFY, enhancement)

Description

[(Away)]

In order to evaluate the feasibility of building Firefox with clang and lld on Windows, we need to see how the performance compares against MSVC.

What would it take to get Windows clang+lld builds onto AWFY?

I currently produce such builds as one-off pushes on Try. In the future I want to see clang+lld become a more formal Treeherder platform, getting built on every m-c push etc., but I'm not there yet. (Is this required for AWFY?)

Comment 1

[Benjamin Bouvier [:bbouvier] (inactive)]

> I currently produce such builds as one-off pushes on Try. In the future I want to see clang+lld become a more formal Treeherder platform, getting built on every m-c push etc., but I'm not there yet. (Is this required for AWFY?)

For browser benchmarking, AWFY downloads browser builds from Treeherder, finding the latest one and downloading it. So it would be needed to have the clang+lld build on treeherder to have it tested on AWFY, at the moment. (In the past we built on the machines, but that meant much lower benchmark running frequencies: once every several hours vs once per hour)

When we have treeherder builds on every push on, say, inbound, adding it to AWFY would mean:
- adding a few entries in the AWFY database to describe the new line
- adding some code in the helper that downloads builds [1].

Another possibility is to manually trigger benchmarking from Try builds, but at the moment this feature is very limited (only one benchmark can be run for a specific build) and not maintained (the developer who made it left Mozilla).

[1] https://github.com/mozilla/arewefastyet/blob/master/slave/download.py

Comment 2

[(Away)]

Thanks! So it sounds like the path of least resistance for me is to make clang+lld become A Real Treeherder Platform.

Comment 3

[(Away)]

Official builds are now clang-cl and lld-link, so nothing special needs to be done for AWFY.