On Tuesday 2016-03-01 09:32 +0800, L. David Baron wrote:
> The W3C is proposing a charter for:
>
> TV Control Working Group
> https://www.w3.org/2016/02/tvcontrol.html
> https://lists.w3.org/Archives/Public/public-new-work/2016Feb/0005.html
>
> Mozilla has the opportunity to send comments o
Hi folks,
On Wed, Mar 2, 2016 at 10:06 AM, Nicholas Alexander
wrote:
> Summary: "The Push API gives web applications the ability to receive
> messages pushed to them from a server, whether or not the web app is in the
> foreground, or even currently loaded, on a user agent. This lets developers
On Wed, Mar 9, 2016 at 12:17 PM, Boris Zbarsky wrote:
> Just to satisfy my curiosity, what is AFL?
>
AFL is American Fuzzy Lop, a fuzzer that uses a combination of compiled-in
code coverage and genetic algorithms. http://lcamtuf.coredump.cx/afl/ It
has found a ton of errors in all sorts of progr
On Wednesday, March 9, 2016 at 12:47:08 PM UTC-8, decod...@googlemail.com wrote:
> >
> > > the sample tests (xpcshell-tests) are extremely complicated to adapt
> >
> > That seems like it would be a problem in any new thing too, right?
>
> Actually no. I adapted our gtests in less than an hour.
>
On 09/03/16 22:17, Bobby Holley wrote:
> I think splitting Gecko into multiple repos is an anti-goal, because we
> derive enormous productivity benefits from using a mono-repo.
>
> If you're serious about proposing that, I would suggest starting a new
> thread to avoid derailing this one.
I'm act
On Wed, Mar 9, 2016 at 12:58 PM, David Rajchenbach-Teller <
dtel...@mozilla.com> wrote:
> I'm assuming that, for the sake of this discussion, Gecko ==
> mozilla-central minus stuff that can be built and distributed on its
> own. In particular, most of toolkit/ is covered by this definition.
>
> Ju
On 3/9/16 3:47 PM, decoder...@googlemail.com wrote:
Actually no. I adapted our gtests in less than an hour.
Does this have to do with the set of things they're testing, or the
style the tests are written in?
- Program is easy to start (doesn't need profiles or long initialization) and
can
I'm assuming that, for the sake of this discussion, Gecko ==
mozilla-central minus stuff that can be built and distributed on its
own. In particular, most of toolkit/ is covered by this definition.
Just looking at things I use/work on, I believe that we could relatively
easily split in distinct mo
>
> > the sample tests (xpcshell-tests) are extremely complicated to adapt
>
> That seems like it would be a problem in any new thing too, right?
Actually no. I adapted our gtests in less than an hour.
>
> > and we can't easily use it with AFL.
>
> Just to satisfy my curiosity, what is AFL?
On 3/9/16 3:06 PM, decoder...@googlemail.com wrote:
Not at all. xpcshell is not very useful for fuzzing. It is slow
OK, fair.
the sample tests (xpcshell-tests) are extremely complicated to adapt
That seems like it would be a problem in any new thing too, right?
and we can't easily use it
> To what extent are we fuzzing things like our url parser and other necko
> bits via our existing shell (xpcshell) that exposes all that stuff?
>
> -Boris
Not at all. xpcshell is not very useful for fuzzing. It is slow, the sample
tests (xpcshell-tests) are extremely complicated to adapt and
On 3/9/16 12:54 PM, twsm...@mozilla.com wrote:
I think Nicolas is right on the mark! JS shell is a good example of using a
shell for fuzzing and I think media and graphics could also get a good deal out
of a shell.
To what extent are we fuzzing things like our url parser and other necko
bits
On Wed, Mar 9, 2016 at 10:45 AM, wrote:
> This seems to be the general response whenever this topic is brought up,
> with good reason. I don't think modularizing Gecko just for the sake of it
> makes much sense. What I think the take away from this should be is: when
> developing a new component
This seems to be the general response whenever this topic is brought up, with
good reason. I don't think modularizing Gecko just for the sake of it makes
much sense. What I think the take away from this should be is: when developing
a new component or maintaining an old one keep in mind that mak
Can you elaborate on which Gecko components you're hoping to fuzz
separately? A lot of the core is pretty heavily-intertwined, so I'm pretty
skeptical that we'd ever be able to separate out DOM, style, and layout
from each other (for example). There are basically two barriers:
(1) These components
On Wednesday, March 9, 2016 at 9:38:55 AM UTC-8, Nicolas B. Pierron wrote:
> This discussion is a follow-up discussion to some emails sent privately by
> accident.
>
> If you have not followed, I will quote David Bryant:
> > Improving release quality is one of the three fundamental goals Platfor
This discussion is a follow-up discussion to some emails sent privately by
accident.
If you have not followed, I will quote David Bryant:
> Improving release quality is one of the three fundamental goals Platform
> Engineering committed to this year. To this end, lmandel built a Bugzilla
> dashb
All,
As a follow-up, Mozilla has been accepted into Google Summer of Code 2016!
What this means to you:
* If you haven't listed a project yet, but are still interested. Please
add it to the ideas page [1] before the student application period
begins (March 14th, 2016)!
* If you have listed a proj
18 matches
Mail list logo
