Many of our tests have inconsistent results.
Generally speaking, developers only run a narrow subset of tests locally
and defer running the full suite of tests to our automation infrastructure.
Within that infrastructure, we have a database of known "intermittent"
failures and tools that attempt
On Wednesday, November 16, 2016 at 3:27:45 AM UTC-5, Gratian Lup wrote:
> Hello,
>
> *I posted this on multiple mailing lists, I'm not sure which is the right
> place for these questions.
>
> I'm a developer on the Microsoft Visual C++ compiler (code optimizer) and I'm
> looking into extending
Hi,
Thanks a lot for your help! I think doing the testing on our machines is a
better approach overall, even from an engineering perspective - in case of
a failure you can just grab the machine and start debugging, recompiling,
etc. The legal work, if possible at all, would be quite complicated
issues to work out. (I'm guessing Microsoft LCA will have an opinion on
mostly-in-the-public-domain Mozilla infrastructure accessing pre-release
Microsoft software.)
Microsoft does release "nightly" compiler builds these days
On Wednesday, November 16, 2016 at 5:23:58 AM UTC-8, Ted Mielczarek wrote:
> Gratian,
>
> One of my coworkers reminded me of something that might be an option for
> you--we have scripts that would allow you to provide a Firefox build
> that you generated (at a publicly accessible URL) and trigger
Gratian,
One of my coworkers reminded me of something that might be an option for
you--we have scripts that would allow you to provide a Firefox build
that you generated (at a publicly accessible URL) and trigger test jobs
on that build in our CI infrastructure. If that's something that sounds
On Wed, Nov 16, 2016, at 03:27 AM, lgrat...@gmail.com wrote:
> Hello,
>
> *I posted this on multiple mailing lists, I'm not sure which is the right
> place for these questions.
Hi Gratian,
Finding the right communication channel always feels like a problem at
Mozilla. :) dev-builds is a fine
7 matches
Mail list logo
