On 10/1/13 10:43 AM, Gregory Szorc wrote:
On 10/1/13 10:26 AM, Karl Tomlinson wrote:
Gregory Szorc writes:
Just landed in inbound is a mass conversion of mochitests to use
manifests.
When adding a new test, the process used to be:
1. add new file path/to/test/directory/new-file
2. add "new-file" to MOCHITEST_FILES in
path/to/test/directory/Makefile.in
3. make -C obj/path/to/test/directory
4. run test
Is the following meant to work now?
1. add new file path/to/test/directory/new-file
2. add "[new-file]" in path/to/test/directory/mochitest.ini
3. make -C obj/path/to/test/directory
4. run test
I tried the above without success.
I also tried replacing 3 with "./mach build path/to/test/directory"
without success.
Is there a new passphrase?
Until bug 920184 lands (patch up for review), you'll need to run the
following to ensure test files are up to date:
$ NO_REMOVE=1 mach build install-tests
If you are simply modifying test files (not adding) and your platform
supports symlinks (not Windows), you likely don't have to run this.
I apologize for the temporary inconvenience. We intended bug 920184 to
land as close to the manifest patches as possible. Chaos around Summit
travel is partially to blame :/
Bug 920184 just landed in inbound.
While I'm here,
https://ci.mozilla.org/job/mozilla-central-docs/Build_Documentation/test_manifests.html
contains the documentation for manifests, complete with the set of
variables available to filter on.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
