When running mozreview locally, either directly or through the selenium tests I often hit stale content in Firefox. When I was doing the pull request work, I had to open the review in a new tab or I would end up seeing old html/js content. When working on the selenium tests, I had to add code to create a profile which disabled caching in order to see updates to the change description once Autoland reported status back. I'm not certain if this affects deployed Reviewboard or not. I think there are different code paths there because running locally does not seem to utilize the minimized bundles that are used in production.
I rebased my work on tip and things started magically working. This is either fixed or an intermittent.
Product: Developer Services → MozReview
You need to log in before you can comment on or make changes to this bug.