| commit | e03df376d50d5748a77be6d88cf594cb3f894ef3 | [log] [tgz] |
|---|---|---|
| author | Joshua Seaton <joshuaseaton@google.com> | Sat Jan 26 13:09:58 2019 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jan 28 22:54:00 2019 +0000 |
| tree | 0567263a4efbe1053206d166282309b38e3c62d4 | |
| parent | 9c65921a50f9e6f1f8ad0e52420933dd9d579e71 [diff] |
[test spec] Define general variables for environments My opinion: -Better to proliferate these variables throughout the tree than complicated, space-hungry scopes (which developers will invariably groan about having to type out). Moreover, these are more easily grep-able. -If we introduce a second nuc, then we can always rename nuc_env to dawson_canyon_env; same for vim2 or any other environment. Bug: IN-497 Change-Id: I54acaa2cee62318be6b7b2bd9ae1a4d33d97d834