We added a bunch of HTTP caching recently, which has (expectedly) been a frequent cause of bugs. By default, HTTP caching is bypassed on localhost, which (also expectedly) can make developers overlook caching bugs. If you're trying to reproduce a bug on localhost, please make sure to un-bypass both the Dynamic and Static Content Response Caches. Details on how that works at [1].
-chris [1] https://oae-community.sakaiproject.org/content#p=ltsrqToCaa/HTTP%20Request%20Caching%20Systems On 7/12/12 10:25 AM, Kent Fitzgerald wrote: > I am seeing a higher than normal number of tickets closed as Cannot > Reproduce. I think this is partially due to the nature of the release. > At the same time, a decent number of those JIRAs are being reopened > because they keep cropping up on the QA environments. > > Before closing a ticket as Cannot Reproduce, can you make sure to > re-test on the environment on which it was reported in additional to > local builds? If you need assistance in reproducing a bug or testing a > fix, I'm happy to help. > > We have seen at least one bug in the past (I don't recall the JIRA at > the moment) that did not manifest on local builds. However, it > manifested reliably on the QA servers and was a bug that needed to be > fixed. > > I've brought qa22 up to the current code base as well. We can use that > to verify bugs on a second environment (beyond local builds). Bert and I > have also used it to verify fixes by deploying jars directly to it. > Please coordinate that kind of testing with me as we don't want to bump > into each other. > > Thanks > -Kent > > > _______________________________________________ > oae-dev mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-dev > _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
