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 mozregress
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 ye
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 ar
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 abo
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
shu
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
6 matches
Mail list logo
