Re: status-firefox41: affected

2015-05-31 Thread Sylvestre Ledru
I don't know about this specific issue but I asked to Ryan a few months back that the status firefox would be automatically marked as "fixed" for the current nightly. I guess this is related to this. The "affected" status flags being automatically set started a few weeks ago. Sylvestre Le 31/0

Re: DBM code too old (Re: mozmill test: Hightail ???)

2015-05-31 Thread ishikawa
On 2015年05月31日 01:36, Philip Chee wrote: > On 29/05/2015 22:31, ISHIKAWA, Chiaki wrote: > >> I figured out the particular cause of >> test-cloudfile-backend-hightail.js. >> experienced during |make mozmill| when I simulated "short read" and >> "short write" to files >> under the profile directory

Re: Proposal to alter the coding style to not require the usage of 'virtual' where 'override' is used

2015-05-31 Thread Gerald Squelart
Will there be a blanket change sometime soon? If not, are we supposed to start using the new style in patches now, even when it would clash with nearby old-style overrides/finals in the same file or in the same directory? ___ dev-platform mailing list

Re: status-firefox41: affected

2015-05-31 Thread Philip Chee
On 31/05/2015 16:02, Sylvestre Ledru wrote: > I don't know about this specific issue but I asked to Ryan a few > months back that the status firefox would be automatically marked as > "fixed" for the current nightly. I guess this is related to this. Yahbutt the flag doesn't get changed to fixed wh

Re: status-firefox41: affected

2015-05-31 Thread glob
this started happening via https://bugzilla.mozilla.org/show_bug.cgi?id=972040 please file a bug and we'll apply per-product filtering -- currently it'll be set on any product that has that flag. (i'm not sure why seamonkey has that flag visible on its bugs) -glob Philip Chee wrote: On 31