On Wed, Oct 19, 2016 at 10:19 AM, Chris Hutten-Czapski
wrote:
> Things that would help me help with this endeavour:
>
> 1: A bug to file patches against
>
I debated this, but given the number of tests involved that seemed like a
bunch of overhead. I've been filing bugs as I fix tests.
> 2: A
On Wed, Oct 19, 2016 at 2:00 AM, Gabriele Svelto
wrote:
> I remember we did a big push in the War on Orange maybe three (or four?)
> years ago. We could do it again; calling out to everybody to take
> intermittent tests in the modules they're familiar with and start fixing
> them. Personally I'd
As of Firefox 52 I intend to turn TLS 1.3 on by default. TLS 1.3 has
been developed using the existing security.tls.version.max preference
to control maximum version.
TLS 1.3 is the next version of TLS, the protocol that secures the web.
TLS 1.3 removes old and unsafe cryptographic primitives, it
I am working on a patch that takes care of most of the warnings in
toolkit/mozapps/extensions/test/xpinstall in
https://bugzilla.mozilla.org/show_bug.cgi?id=1311459
On Tue, Oct 18, 2016 at 3:28 PM, Blake Kaplan wrote:
> Hello everybody,
>
> I've been seeing a pattern of "unsafe" CPOWs causing ou
Things that would help me help with this endeavour:
1: A bug to file patches against
2: A method for detecting if our fix actually fixes the problem
I presume a skeleton of what we're looking for is:
1) Use DXR/ls -r/whatever to find the test file in the tree
2) On the line number(s) mentioned, r
Hi Blake,
On 19/10/2016 00:28, Blake Kaplan wrote:
> I've been seeing a pattern of "unsafe" CPOWs causing our browser-chrome
> mochitests to go intermittently orange. Generally, it seems that a test
> randomly turns orange, gets starred and ignored until RyanVM or another one
> of our sheriffs ge
6 matches
Mail list logo
