Gregory Szorc writes: > On Wed, Nov 30, 2016 at 12:40 PM, Karl Tomlinson <mozn...@karlt.net> wrote: >> When history is rewritten, is there a way to view the original >> history through the web interface, so that autoland tinderbox >> builds can be used to find regression ranges? > > No. Rewritten changesets should result in "replacement" automation results. > So there should be no loss of automation coverage. So there should be no > major impact to things like regression range searching.
Are the "replacement" results tests re-run with builds from the new revisions? Or are the results copied from results for the previous revisions? If so, is this detectable in treeherder somehow? >> https://hg.mozilla.org/integration/autoland/rev/04a37d89a469 >> says "An error occurred while processing your request" > > This is likely bug 1321344. Ugh, it looks like that issue is more > widespread than I thought. I'll try to fix it in the next hour. I thought the "no" answer above would indicate changesets that have been rewritten would no longer be visible through the URLs such as above, but would you expect rewritten changsets to remain visible on these URLs (if bug 1321344 were fixed)? >> Is it necessary to pull autoland and use the evolve extension? > > It isn't necessary to have evolve enabled to pull the autoland repo. But if > evolve is enabled, rewritten changesets that you have pulled from the > autoland repo will disappear automatically. Otherwise your local repo will > keep accumulating old heads now have since been rewritten on the autoland > repo. Thanks. Just to be clear, will pulling from autoland pull old heads that have been rewritten? (i.e. I'm not clear whether the accumulating old heads need to be pulled before the rewrite.) _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
