After some follow up investigations, it turns out the MacOS tests also rely on this, we just hadn't noticed due to a different bug :-(
Short version: Sorry for wasting your time, you can ignore this thread. All the other feedback we've gotten about general sandbox debugging will still be considered :-) Cheers, Alex On Tue, May 9, 2017 at 2:25 PM, Gian-Carlo Pascutto <g...@mozilla.com> wrote: > On 08-05-17 19:26, Alex Gaynor wrote: > > Hi dev-platform, > > > > Top-line question: Do you rely on being able to run mochitests from a > > packaged build (`--appname`)? > > It seems our Linux tests do, actually: > > https://treeherder.mozilla.org/logviewer.html#?job_id=97391302&repo=try > > "test-linux32/opt-mochitest-e10s-1 tc-M-e10s(1)" launches > > /home/worker/workspace/build/tests/mochitest/runtests.py --total-chunks > 10 --this-chunk 1 > --appname=/home/worker/workspace/build/application/firefox/firefox > --utility-path=tests/bin --extra-profile-file=tests/bin/plugins > > Using --appname. As expected, this then fails because the sandbox didn't > get the exception added and correctly blocks the reading of some test > files that are in a random place: > > /home/worker/workspace/build/tests/mochitest/extensions/ > specialpowers/chrome/specialpowers/content/MozillaLogger.js > > We may need another solution here. > > -- > GCP > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
