
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}
23 lines
634 B
Python
Executable File
23 lines
634 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."""
|
|
|
|
from __future__ import print_function
|
|
import signal
|
|
import sys
|
|
import time
|
|
|
|
|
|
def print_signal(sig, *_args):
|
|
print('Signal :{}'.format(sig))
|
|
|
|
|
|
if __name__ == '__main__':
|
|
signal.signal(signal.SIGTERM, print_signal)
|
|
signal.signal(signal.SIGINT, print_signal)
|
|
if sys.platform == 'win32':
|
|
signal.signal(signal.SIGBREAK, print_signal) # pylint: disable=no-member
|
|
time.sleep(2) # gives process time to receive signal.
|