Protocol Buffers - Google's data interchange format (grpc依赖)
https://developers.google.com/protocol-buffers/
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
69 lines
3.1 KiB
69 lines
3.1 KiB
# Copyright (c) 2009-2021, Google LLC |
|
# All rights reserved. |
|
# |
|
# Redistribution and use in source and binary forms, with or without |
|
# modification, are permitted provided that the following conditions are met: |
|
# * Redistributions of source code must retain the above copyright |
|
# notice, this list of conditions and the following disclaimer. |
|
# * Redistributions in binary form must reproduce the above copyright |
|
# notice, this list of conditions and the following disclaimer in the |
|
# documentation and/or other materials provided with the distribution. |
|
# * Neither the name of Google LLC nor the |
|
# names of its contributors may be used to endorse or promote products |
|
# derived from this software without specific prior written permission. |
|
# |
|
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND |
|
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED |
|
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE |
|
# DISCLAIMED. IN NO EVENT SHALL Google LLC BE LIABLE FOR ANY |
|
# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES |
|
# (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; |
|
# LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND |
|
# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
|
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS |
|
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
|
|
|
def generated_file_staleness_test(name, outs, generated_pattern): |
|
"""Tests that checked-in file(s) match the contents of generated file(s). |
|
|
|
The resulting test will verify that all output files exist and have the |
|
correct contents. If the test fails, it can be invoked with --fix to |
|
bring the checked-in files up to date. |
|
|
|
Args: |
|
name: Name of the rule. |
|
outs: the checked-in files that are copied from generated files. |
|
generated_pattern: the pattern for transforming each "out" file into a |
|
generated file. For example, if generated_pattern="generated/%s" then |
|
a file foo.txt will look for generated file generated/foo.txt. |
|
""" |
|
|
|
script_name = name + ".py" |
|
script_src = ":staleness_test.py" |
|
|
|
# Filter out non-existing rules so Blaze doesn't error out before we even |
|
# run the test. |
|
existing_outs = native.glob(include = outs) |
|
|
|
# The file list contains a few extra bits of information at the end. |
|
# These get unpacked by the Config class in staleness_test_lib.py. |
|
file_list = outs + [generated_pattern, native.package_name() or ".", name] |
|
|
|
native.genrule( |
|
name = name + "_makescript", |
|
outs = [script_name], |
|
srcs = [script_src], |
|
testonly = 1, |
|
cmd = "cat $(location " + script_src + ") > $@; " + |
|
"sed -i.bak -e 's|INSERT_FILE_LIST_HERE|" + "\\\n ".join(file_list) + "|' $@", |
|
) |
|
|
|
native.py_test( |
|
name = name, |
|
srcs = [script_name], |
|
data = existing_outs + [generated_pattern % file for file in outs], |
|
python_version = "PY3", |
|
deps = [ |
|
":staleness_test_lib", |
|
], |
|
)
|
|
|