On Sun, Jul 6, 2014 at 10:02 PM, Joshua Cranmer 🐧 <pidgeo...@gmail.com> wrote:
> Effectively, only xpcshell tests, and the M, M-e10s, and R groups are > represented in the output data. M-e10s is slightly borked: only M-e10s(1) > [I think] is shown, because, well, treeherder didn't distinguish between > the five of them. A similar problem with the debug M(dt1/dt2/dt3) test > suites will arise when I incorporate that data. C++ unit tests are not > present because blobber doesn't run on C++ unit tests for some reason, and > Jit-tests, jetpack tests, and Marionette tests await me hooking in the > upload scripts to those testsuites (and Jit-tests would suffer a similar > numbering problems). The individual testsuites within M-oth may be > mislabeled because I can't sort names properly. > I think this is great work and also very important. Good job! Besides the cppunit tests, there are also C++ unit tests based on GTest that get run as part of the (B) step. For example, all the GTests in security/pkix/test/gtest/* run that way. It would be great to have coverage for those tests incorporated into the reports too, especially because many (most?) of the new certificate verification tests are written that way, instead of through xpcshell test, especially the tests that test edge cases. Cheers, Brian _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
