Run mash_unittests as ash_unittests --mash, like ash_unittests --mus |
||||||
Issue descriptionThis came up in the meeting today, as part of the discussion on making mustash easier for non-team-members to develop: https://docs.google.com/document/d/1rXhOnmOXiG_C319XerTfZJf-pg6jJx-qZs65ILfda-4/edit This might involve moving some of the tests to a new target (maybe keep mash_unittests for that). Jon, we picked you as a victim because you weren't in the room. :-) Thoughts? I can help with this if needed.
,
May 29 2017
,
May 30 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8d1a3c75e20c8bdc048d29a3020115d3ecdf0e48 commit 8d1a3c75e20c8bdc048d29a3020115d3ecdf0e48 Author: jonross <jonross@chromium.org> Date: Tue May 30 20:03:42 2017 Setup ash_unittests --mash Have ash_unittests handle the --mash flag by setting up the internal config to be mash, as well as setting aura to be non-local. Create filter of blacklisted tests. Update bot configs for new test. TEST=ash_unittests --mash BUG= 722544 Review-Url: https://codereview.chromium.org/2911213002 Cr-Commit-Position: refs/heads/master@{#475638} [modify] https://crrev.com/8d1a3c75e20c8bdc048d29a3020115d3ecdf0e48/ash/test/ash_test_suite.cc [modify] https://crrev.com/8d1a3c75e20c8bdc048d29a3020115d3ecdf0e48/testing/buildbot/chromium.chromiumos.json [modify] https://crrev.com/8d1a3c75e20c8bdc048d29a3020115d3ecdf0e48/testing/buildbot/chromium.fyi.json [modify] https://crrev.com/8d1a3c75e20c8bdc048d29a3020115d3ecdf0e48/testing/buildbot/filters/BUILD.gn [add] https://crrev.com/8d1a3c75e20c8bdc048d29a3020115d3ecdf0e48/testing/buildbot/filters/ash_unittests_mash.filter
,
May 30 2017
,
Aug 1 2017
,
Jan 22 2018
,
Feb 26 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jonr...@chromium.org
, May 15 2017