On Thu, Sep 27, 2018 at 11:19 AM Aaron Klotz <akl...@mozilla.com> wrote:
> 1. Automation > ------------- > > If you are doing some kind of automation that waits for the Firefox > process to finish, you'll find that the initial Firefox process exits > sooner than the browser, appearing to your script that Firefox is > already done when in fact it is still running. This is because, by > default, the launcher process only lives long enough to stand up the > browser process and transfer foreground to the new browser's window. > > In order to make the launcher wait for the browser to complete, pass the > --wait-for-browser flag on the command line. The launcher will wait for > the entire life of the browser process, and will also propagate the > browser process's exit code as its own. The launcher also accepts the > presence of the MOZ_AUTOMATION environment variable as an implicit > --wait-for-browser request. > > I have already fixed up our automation to supply this parameter when > necessary, so I expect everything in Mozilla's CI system to already Just > Work. > Is the --wait-for-browser flag the default in headless mode, since that mode is mostly for automation Thanks, -- Ehsan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
