The Official 20161120 builds are out

DinGo · Post by **DinGo** » November 20th, 2016, 3:22 pm

Since the 20161117 build Aurora hasn't updated automatically. To update I have to download from the ftp and install.

Can anyone give me any reasons why this is happening?

JayhawksRock · Post by **JayhawksRock** » November 20th, 2016, 4:32 pm

many/most of the the Aurora and Nightly builds do not auto update.... or you may have the never update set in Options. I get promped to update automajicly, Last update 11/14
the pref > app.update.channel aurora

bjherbison · Post by **bjherbison** » November 20th, 2016, 6:24 pm

Text field history stopped working for me with the Sunday 20 November build, but was back when I restarted. No suggestions popped up when I started typing, and down arrow didn't display any history.

It's a behavior I haven't seen before, but it happened only one time.

Fanolian · Post by **Fanolian** » November 20th, 2016, 7:32 pm

avada wrote:
Josa wrote:Can you reproduce it with a brand new profile?
No. I filed a bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1318938 (I attached my about:support there)

In your bug regarding mozregression, you may use mozregression-GUI if you are not familiar with typing parameters in command prompt.

streetwolf · Post by **streetwolf** » November 21st, 2016, 7:02 am

Heads up. https://bugzilla.mozilla.org/show_bug.cgi?id=1293305 might break some add-ons. It's on inbound atm.

HN_FIN · Post by **HN_FIN** » November 21st, 2016, 8:54 am

Aurora updates have been finally re-enabled after the merge / version bump.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 ID:20161121004022 CSet: a99c9599b45835479e6e18da0614b0652d42435a

avada · Post by **avada** » November 21st, 2016, 10:39 am

Fanolian wrote:
avada wrote:
Josa wrote:Can you reproduce it with a brand new profile?
No. I filed a bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1318938 (I attached my about:support there)
In your bug regarding mozregression, you may use mozregression-GUI if you are not familiar with typing parameters in command prompt.

Thanks. It'll come handy in the future.

Josa · Post by **Josa** » November 21st, 2016, 11:03 am

This thread is closed, please use the next one.

Fanolian · Post by **Fanolian** » November 21st, 2016, 11:24 am

avada wrote:
Fanolian wrote:In your bug regarding mozregression, you may use mozregression-GUI if you are not familiar with typing parameters in command prompt.
Thanks. It'll come handy in the future.

Sometimes there are more than 1 bug/commit pushed between the builds you test in the final step.
IMO, for us non-developers, it's better to include the pushlog from the final step. The experts can then determine the most relevant bug from that range (and for quick reference to reproduce your steps in mozregression).

Pushlog can be copied from "Bisection informations" by selecting the last step in "Bisection progress".
https://i.imgur.com/lWDe4NX.png

The Official 20161120 builds are out

Re: The Official 20161120 builds are not yet out

Re: The Official 20161120 builds are not yet out

Re: The Official 20161120 builds are not yet out

Re: The Official 20161120 builds are not yet out

Re: The Official 20161120 builds are not yet out

Re: The Official 20161120 builds are not yet out

Re: The Official 20161120 builds are not yet out

Re: The Official 20161120 builds are out

Re: The Official 20161120 builds are not yet out