Open Bug 1496867 Opened 7 years ago Updated 3 years ago

Detect unused clang patches

Categories

(Firefox Build System :: Task Configuration, task)

task

Tracking

(Not tracked)

People

(Reporter: glandium, Unassigned)

Details

It's easy to overlook the fact that some patches under build/build-clang/ end up unused, on the other hand, we have references to all the json files used in the taskcluster configuration, so we could actually read the json files, and find which patches in the file system are not used. As a bonus, we could use the patch contents in the clang hash (which we currently don't do, we rely on patches never changing)
This sounds like it would be a bit time-consuming in the decision task, yet I don't have a good sense for how useful the change is. Is the resource trade-off a win?
We're already reading the json files, so the added overhead would be json decoding. For a dozen small files. I don't think that's a big addition to overhead.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.