On 2016-12-29 9:34 AM, Ryan VanderMeulen wrote:
> On 12/23/2016 3:21 PM, Nicholas Nethercote wrote:
>> Hooray!
>>
>> What is the name of the job on Treeherder? I see a "Windows 2012 x64 opt
>> Executed by TaskCluster build-win64-clang/opt tc(Bcl)" job (and some
>> minor
>> variations) but I
On 12/23/2016 3:21 PM, Nicholas Nethercote wrote:
Hooray!
What is the name of the job on Treeherder? I see a "Windows 2012 x64 opt
Executed by TaskCluster build-win64-clang/opt tc(Bcl)" job (and some minor
variations) but I suspect that's not the new static analysis one?
There's a tc(S) job
Hooray!
What is the name of the job on Treeherder? I see a "Windows 2012 x64 opt
Executed by TaskCluster build-win64-clang/opt tc(Bcl)" job (and some minor
variations) but I suspect that's not the new static analysis one?
Nick
p.s. Nathan is omitting himself from the list of contributors -- he
As per the subject. This job is strictly for smoketest purposes;
there are no tests being run on the result of the build.
As these are tier-2 builds, build failures will not be cause for
backouts. However, as clang complains about a wider range of problems
than our current MSVC builds do, and
4 matches
Mail list logo