Comment 18 for bug 1953685
Revision history for this message
|
|
#18 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
(In reply to Ivan Molodetskikh from comment #13)
> > Can you find the commit that fixes things with `mozregression`?
>
> A bit of a problem here. First, `mozregression`, at least in `--find-fix` mode, seems to be converting release numbers to dates, which pulls the build for the next version (so `95` pulls `96.0a`)—not sure if that is intended.
Hm, I guess you can simply use the `--good` and `--bad` parameters, no?
> Second, on the profile that `mozregression` runs even 2021-12-07 gives the 120 FPS lock. When creating a new profile from every instance run by `mozregression` and switching to it twice, neither `94` (`95.0a`), nor `95` (`96.0a`), nor 2021-12-07 exhibit the issue. Nevertheless, when testing tarballs for stable 95 and 2021-12-07 outside of `mozregression`, stable 95 exhibits the issue even when making a new profile, while 2021-12-07 is fine on a new profile as I mentioned above.
This is really odd. I also really don't understand where the 120Hz are supposed to come from.