ahal: any thoughts on why new `cram` tests wouldn't get picked up? The test manifest stuff is so involved that I'm never quite sure what's supposed to happen... see [this try task](https://treeherder.mozilla.org/jobs?repo=try&revision=75380daf4707bbaef1dc2836eafb98b238a02ce8&selectedTaskRun=Q53hSXRUTh60z5pxPv8Tug.0). Locally, `mach cramtest mobile/android` works. But I have `--enable-application=mobile/android`: is this due to some conditional inclusion of `moz.build` files? Should I: 1. put these `cram` tests in some global location, like `/build` (which has tests that do not seem to be run, just FYI)? 2. name the `.t` file in the command, so they always get found? 3. something else? Thanks!
Bug 1570400 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
ahal: any thoughts on why new `cram` tests wouldn't get picked up? The test manifest stuff is so involved that I'm never quite sure what's supposed to happen... see [this try task](https://treeherder.mozilla.org/jobs?repo=try&revision=75380daf4707bbaef1dc2836eafb98b238a02ce8&selectedTaskRun=Q53hSXRUTh60z5pxPv8Tug.0). Locally, `mach cramtest mobile/android` works. But I have `--enable-application=mobile/android`: is this due to some conditional inclusion of `moz.build` files? Should I: 1. put these `cram` tests in some global location, like `/build` (which has tests that do not seem to be run, just FYI)? 2. name the `.t` file in the command, so they always get found? 3. something else entirely? Maybe narrow clones are to blame? Thanks!