Gijs Kruitbosch wrote on 09/02/2016 11:37 AM: > I am not familiar with this bit of our build architecture, but as far as > I can tell from a quick look it builds bits of the zipfile off the > objdir. So it collects mochitests from $OBJDIR/_tests/testing/mochitest, > where (again, AFAICT) things get installed via manifests.
This is only happening for old test suites but not for more recent ones. But also for reftests we do no longer have to copy all the files to the obj dir first. We package them directly from the source tree into the various *.tests.zip files. But this is all related to directories and not individual files. > We should be doing the same for firefox-ui tests. Not just to avoid > duplication of files in archives, but because otherwise, if we want to > add new tests somewhere else, we both have to add the manifests to the > build system and then modify this build system python file to make sure > they get included in the test archive. That would be wrong. No, this is not what we want to do. Anything related to the obj dir causes a lot of operations and cpu cycles to build those archives (see bug 1283919 comment 1). With having the manifests in place we can also run the tests directly from the source tree. It's true that the situation with a master manifest is not ideal right now, and especially for marionette we have it located in testing/marionette/harness/marionette/test/. Anyway for firefox-ui tests I want to have testing/firefox-ui/tests/(functional|update)-tests.ini. >From here we can reference everything. -- Henrik _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
