
Some subdirs have their own .style.yapf files (like //testing/pytype_common/), but most do not. This has lead to a lot of python code in //testing/ naturally being developed with no consistent styling. This can make things a little hard to read when put in the context of other py code throughout the repo that's much more consistent. So this: - adds a basic //testing/.style.yapf file - adds another testing/trigger_scripts/.style.yapf file that's similar but sets indent to 4, since the code in that dir currently uses 4 indents - reformats everything - adds a presubmit checkout to //testing/PRESUBMIT.py to enforce that things stay formatted Bug: 340623285 Change-Id: I2a6707ba2f6f784454d348a19280dca2ca90804b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5540460 Commit-Queue: Ben Pastene <bpastene@chromium.org> Reviewed-by: Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/main@{#1301583}
17 lines
438 B
Python
Executable File
17 lines
438 B
Python
Executable File
#!/usr/bin/env python
|
|
# Copyright 2019 The Chromium Authors
|
|
# Use of this source code is governed by a BSD-style license that can be
|
|
# found in the LICENSE file.
|
|
"""Script for use in test_env unittests."""
|
|
|
|
import os
|
|
import sys
|
|
|
|
import test_env
|
|
|
|
HERE = os.path.dirname(os.path.abspath(__file__))
|
|
TEST_SCRIPT = os.path.join(HERE, 'test_env_test_script.py')
|
|
|
|
if __name__ == '__main__':
|
|
test_env.run_command([sys.executable, TEST_SCRIPT])
|