"older version" check
hi,
I've been testing nightly builds of the mail client since seamonkey, in
the 1990s, and occasionally logging bugs as I find them, in a small
attempt to contribute. Originally I built locally from source, but now
download Daily builds.
My normal method when finding a bug is to bisect using older builds
until I find the build that introduced the problem, hoping that this
might aid someone in finding what caused it.
In trying to do that whilst logging bug 1531434 today, I find that it no
longer seems possible to use older builds with a newer profile: I get a
Firefox (sic) warning, and am given a choice of either creating a fresh
new profile, or Quit.
This seems to be new; I noticed that v66b2 does not have this check, for
example, and allows me to use a current profile that the last few days'
builds (which is all I keep on my system) refuse.
I understand the need to protect against non-backwards compatible
changes, but it seems to me that this check makes alpha testing with
Daily much more onerous.
If a bug only appears with a given set of conditions, as stored in a
Profile, how is one to bisect older builds to find out when it was
introduced, if you can't use that profile with older builds?
I find bugs by /using/ Daily builds, not by "testing" them, so being
able to use my real profile is essential.
Do I have to give up testing, after all these years?
thanks very much.
best regards,
calum.
This is a result of the profile per install feature.
It's not recommended for normal usage, but for testing and such
purposes, you can use the --allow-downgrade command line switch.
Thanks for testing nighties! It's critical that we have enough users
reporting bugs they find there.
-Magnus
On 28-02-2019 22:08, Calum Mackay wrote:
hi,
I've been testing nightly builds of the mail client since seamonkey,
in the 1990s, and occasionally logging bugs as I find them, in a small
attempt to contribute. Originally I built locally from source, but now
download Daily builds.
My normal method when finding a bug is to bisect using older builds
until I find the build that introduced the problem, hoping that this
might aid someone in finding what caused it.
In trying to do that whilst logging bug 1531434 today, I find that it
no longer seems possible to use older builds with a newer profile: I
get a Firefox (sic) warning, and am given a choice of either creating
a fresh new profile, or Quit.
This seems to be new; I noticed that v66b2 does not have this check,
for example, and allows me to use a current profile that the last few
days' builds (which is all I keep on my system) refuse.
I understand the need to protect against non-backwards compatible
changes, but it seems to me that this check makes alpha testing with
Daily much more onerous.
If a bug only appears with a given set of conditions, as stored in a
Profile, how is one to bisect older builds to find out when it was
introduced, if you can't use that profile with older builds?
I find bugs by /using/ Daily builds, not by "testing" them, so being
able to use my real profile is essential.
Do I have to give up testing, after all these years?
thanks very much.
best regards,
calum.
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
thanks very much indeed, Magnus, and also to Jörg who kindly pointed out
the same in the bug I logged today :)
apologies for wasting everyone's time with this email!
cheers,
calum.
On 28/02/2019 8:20 pm, Magnus Melin wrote:
This is a result of the profile per install feature.
It's not recommended for normal usage, but for testing and such
purposes, you can use the --allow-downgrade command line switch.
Thanks for testing nighties! It's critical that we have enough users
reporting bugs they find there.
-Magnus
On 28-02-2019 22:08, Calum Mackay wrote:
hi,
I've been testing nightly builds of the mail client since seamonkey,
in the 1990s, and occasionally logging bugs as I find them, in a small
attempt to contribute. Originally I built locally from source, but now
download Daily builds.
My normal method when finding a bug is to bisect using older builds
until I find the build that introduced the problem, hoping that this
might aid someone in finding what caused it.
In trying to do that whilst logging bug 1531434 today, I find that it
no longer seems possible to use older builds with a newer profile: I
get a Firefox (sic) warning, and am given a choice of either creating
a fresh new profile, or Quit.
This seems to be new; I noticed that v66b2 does not have this check,
for example, and allows me to use a current profile that the last few
days' builds (which is all I keep on my system) refuse.
I understand the need to protect against non-backwards compatible
changes, but it seems to me that this check makes alpha testing with
Daily much more onerous.
If a bug only appears with a given set of conditions, as stored in a
Profile, how is one to bisect older builds to find out when it was
introduced, if you can't use that profile with older builds?
I find bugs by /using/ Daily builds, not by "testing" them, so being
able to use my real profile is essential.
Do I have to give up testing, after all these years?
thanks very much.
best regards,
calum.
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
hey calum,
thanks for doing regression window testing. this is often very helpful. we even have a bugzilla keyword just for that, because it's often so badly needed to find a bug. this kind of help is very appreciated!
(Magnus has already replied to the bug itself. this was interesting for me as well.)
Ben
Am 28. Februar 2019 21:08:08 MEZ schrieb Calum Mackay calum.mackay@cdmnet.org:
hi,
I've been testing nightly builds of the mail client since seamonkey, in
the 1990s, and occasionally logging bugs as I find them, in a small
attempt to contribute. Originally I built locally from source, but now
download Daily builds.
My normal method when finding a bug is to bisect using older builds
until I find the build that introduced the problem, hoping that this
might aid someone in finding what caused it.
In trying to do that whilst logging bug 1531434 today, I find that it
no
longer seems possible to use older builds with a newer profile: I get a
Firefox (sic) warning, and am given a choice of either creating a fresh
new profile, or Quit.
This seems to be new; I noticed that v66b2 does not have this check,
for
example, and allows me to use a current profile that the last few days'
builds (which is all I keep on my system) refuse.
I understand the need to protect against non-backwards compatible
changes, but it seems to me that this check makes alpha testing with
Daily much more onerous.
If a bug only appears with a given set of conditions, as stored in a
Profile, how is one to bisect older builds to find out when it was
introduced, if you can't use that profile with older builds?
I find bugs by /using/ Daily builds, not by "testing" them, so being
able to use my real profile is essential.
Do I have to give up testing, after all these years?
thanks very much.
best regards,
calum.
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
--
Sent from my phone. Please excuse the brevity.
Can someone please share the bug number?
On Fri, Mar 1, 2019 at 8:24 AM Calum Mackay calum.mackay@cdmnet.org wrote:
thanks very much indeed, Magnus, and also to Jörg who kindly pointed out
the same in the bug I logged today :)
apologies for wasting everyone's time with this email!
cheers,
calum.
On 28/02/2019 8:20 pm, Magnus Melin wrote:
This is a result of the profile per install feature.
It's not recommended for normal usage, but for testing and such
purposes, you can use the --allow-downgrade command line switch.
Thanks for testing nighties! It's critical that we have enough users
reporting bugs they find there.
-Magnus
On 28-02-2019 22:08, Calum Mackay wrote:
hi,
I've been testing nightly builds of the mail client since seamonkey,
in the 1990s, and occasionally logging bugs as I find them, in a small
attempt to contribute. Originally I built locally from source, but now
download Daily builds.
My normal method when finding a bug is to bisect using older builds
until I find the build that introduced the problem, hoping that this
might aid someone in finding what caused it.
In trying to do that whilst logging bug 1531434 today, I find that it
no longer seems possible to use older builds with a newer profile: I
get a Firefox (sic) warning, and am given a choice of either creating
a fresh new profile, or Quit.
This seems to be new; I noticed that v66b2 does not have this check,
for example, and allows me to use a current profile that the last few
days' builds (which is all I keep on my system) refuse.
I understand the need to protect against non-backwards compatible
changes, but it seems to me that this check makes alpha testing with
Daily much more onerous.
If a bug only appears with a given set of conditions, as stored in a
Profile, how is one to bisect older builds to find out when it was
introduced, if you can't use that profile with older builds?
I find bugs by /using/ Daily builds, not by "testing" them, so being
able to use my real profile is essential.
Do I have to give up testing, after all these years?
thanks very much.
best regards,
calum.