Modify getClangCMakeBuildFactory and getClangCMakeGCSBuildFactory
to take as input a list of checks instead of a boolean. This makes it possible
to run subsets of the tests and is similar to the pattern used by the
UnifiedTreeBuilder.
Details
Diff Detail
Event Timeline
Thanks, Diana!
List of checks is a good idea.
zorg/buildbot/builders/ClangBuilder.py | ||
---|---|---|
75 | Please do not use mutable objects as defaults. Instead make it None and handle that in the body as the trigger to set a default value. https://docs.python-guide.org/writing/gotchas/#mutable-default-arguments | |
136 | Ditto. | |
186 | Ditto. _getClangCMakeBuildFactory seems the right place to implement that “default check-all” logic. | |
297 | Just for a better UX you may want each check to be a separate build step, if multiple specified. Not a stopper for this patch. |
Thanks, I updated it to use None as a default.
Separate steps for each set of checks sounds like a good idea. Maybe we can add that when we actually have a buildbot that runs at least 2 sets of checks (hopefully this one, in the near future).
Please do not use mutable objects as defaults. Instead make it None and handle that in the body as the trigger to set a default value.
https://docs.python-guide.org/writing/gotchas/#mutable-default-arguments