What hardware is needed to make a Firefox OS phone and can you list them?

2020-06-26 Thread 10alldayrblx
What the title says. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Shutting down legacy Taskcluster deployment

2020-06-26 Thread Mike Hommey
On Fri, Jun 26, 2020 at 08:04:01PM +, Tom Ritter wrote: > On Fri, Jun 26, 2020 at 7:34 PM Andrew Halberstadt wrote: > > > > On Fri, Jun 26, 2020 at 3:14 PM Jeff Muizelaar > > wrote: > >> > >> What percentage of the space used for artifacts is actually builds > >> that are used for

Re: Shutting down legacy Taskcluster deployment

2020-06-26 Thread Tom Ritter
On Fri, Jun 26, 2020 at 7:34 PM Andrew Halberstadt wrote: > > On Fri, Jun 26, 2020 at 3:14 PM Jeff Muizelaar wrote: >> >> What percentage of the space used for artifacts is actually builds >> that are used for mozregression vs other stuff (like debug builds)? Is >> there a way that we could

Re: Shutting down legacy Taskcluster deployment

2020-06-26 Thread Andrew Halberstadt
On Fri, Jun 26, 2020 at 3:14 PM Jeff Muizelaar wrote: > What percentage of the space used for artifacts is actually builds > that are used for mozregression vs other stuff (like debug builds)? Is > there a way that we could somehow have different expiraries for the > different kinds of data? 1

Re: Shutting down legacy Taskcluster deployment

2020-06-26 Thread Jeff Muizelaar
Losing 4 months of mozregression does sort of suck though. Being able to bisect down to a specific push is a lot more helpful than a specific nightly. I have it often enough that I'm annoyed by only having 1 year of builds. What percentage of the space used for artifacts is actually builds that

Re: Shutting down legacy Taskcluster deployment

2020-06-26 Thread Kartikaya Gupta
Thanks for clarifying. If nightlies are still available for that period then I guess that's ok. It will be a slight inconvenience but probably not worth the effort to and save those builds for a few months. On Fri, Jun 26, 2020 at 9:53 AM Chris Cooper wrote: > > I've received multiple replies

Re: Shutting down legacy Taskcluster deployment

2020-06-26 Thread Chris Cooper
I've received multiple replies about mozregression, so I'll provide some more context. Taskcluster artifacts expire by default after one year. This means the legacy cluster currently provides access to artifacts from June 26 to Nov 9, 2019 (Nov 9 was the cutover date to the new deployment). By

Re: Please don't use functions from ctype.h and strings.h

2020-06-26 Thread Jason Orendorff
This turns out to be super easy to do in clang-tidy, so I took bug 1485588. -j On Wed, Jun 24, 2020 at 2:35 PM Chris Peterson wrote: > On 8/27/2018 7:00 AM, Henri Sivonen wrote: > > I think it's worthwhile to have a lint, but regexps are likely to have > > false positives, so using clang-tidy

Re: Intent to ship: returning shared memory to the web

2020-06-26 Thread Lars Hansen
I want to add that enabling shared memory in Firefox also enables wasm thread operations [1]. That proposal is only at stage 2 in the Community Group, but has been in Chrome release since v74, is used in live content on the web (eg Google Earth), and is therefore in its final form for all

Re: Shutting down legacy Taskcluster deployment

2020-06-26 Thread Kartikaya Gupta
Do these legacy artifacts include firefox builds that are used by mozregression? It looks like there's still a reference to the old taskcluster.net URL at https://github.com/mozilla/mozregression/blob/3df977cf7b9c50bdbe8495cde17baeb6c5724be2/mozregression/config.py#L23 which gets used. It would be