Fix some misspellings in .proto files.
Also update go binding generated files by generate.sh.
BUG=none
TEST=none
Change-Id: Iab4156c676373d10e5723257c14c90dfda3aa3bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/2120656
Reviewed-by: C Shapiro <shapiroc@chromium.org>
Commit-Queue: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Tested-by: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
diff --git a/go/lab/dut_state.pb.go b/go/lab/dut_state.pb.go
index f96786d..5480f68 100644
--- a/go/lab/dut_state.pb.go
+++ b/go/lab/dut_state.pb.go
@@ -59,7 +59,7 @@
// CR50-related configs by definition shouldn't be a state config, but a build config.
// However, we don't have a way to source it from any external configuration system,
// and it's changed frequently enough to handle cr50 tests, which makes
-// it basically imposible for manual updatings: See crbug.com/1057145 for the
+// it basically impossible for manual updatings: See crbug.com/1057145 for the
// troubles it causes.
//
// So we temporarily set it in state config so that repair job can update it.
diff --git a/go/test/device_condition.pb.go b/go/test/device_condition.pb.go
index edad270..4985358 100644
--- a/go/test/device_condition.pb.go
+++ b/go/test/device_condition.pb.go
@@ -48,7 +48,7 @@
// If not empty, all values in this field must be contained in the
// device.Config.hardware_features list.
HardwareFeatures []device.Config_HardwareFeature `protobuf:"varint,8,rep,packed,name=hardware_features,json=hardwareFeatures,proto3,enum=device.Config_HardwareFeature" json:"hardware_features,omitempty"`
- // If not emtpy, any value in device.Config.hardware_features must not be
+ // If not empty, any value in device.Config.hardware_features must not be
// contained in this field.
NoHardwareFeatures []device.Config_HardwareFeature `protobuf:"varint,9,rep,packed,name=no_hardware_features,json=noHardwareFeatures,proto3,enum=device.Config_HardwareFeature" json:"no_hardware_features,omitempty"`
// If this is not POWER_SUPPLY_UNSPECIFIED, power and device.Config.power
@@ -237,7 +237,7 @@
// the test for such a case.
// On the other hand, chromeos/infra/config is expected to be used for
// disabling tests on a specific board, regardless of versions, because of
-// temporaly infra/lab issue, for example.
+// temporary infra/lab issue, for example.
type ConfigIdCondition struct {
// Condition of device.PlatformId. This condition needs to be satisfied by
// device.ConfigId.platform_id.
diff --git a/go/test/metadata/v1/metadata.pb.go b/go/test/metadata/v1/metadata.pb.go
index 0756b50..27271f9 100644
--- a/go/test/metadata/v1/metadata.pb.go
+++ b/go/test/metadata/v1/metadata.pb.go
@@ -283,7 +283,7 @@
//
// - A variable 'scope' of type DUTCondition.Scope. This variable contains the
// information about a particular Device Under Test being tested for
- // acceptance via `expresssion`.
+ // acceptance via `expression`.
// - Protobuf definitions in this git project (i.e., rooted at infra/proto/).
//
// ### Syntax
@@ -369,7 +369,7 @@
// Protocol buffer scope for interpretation of `expression`.
//
// Scope includes the Device Under Test features that can be targeted for test
-// targetting.
+// targeting.
type DUTCondition_Scope struct {
// Device Under Test specification.
Device *common.Device `protobuf:"bytes,1,opt,name=device,proto3" json:"device,omitempty"`
diff --git a/go/test/plan/v1/plan.pb.go b/go/test/plan/v1/plan.pb.go
index cde3299..daf872c 100644
--- a/go/test/plan/v1/plan.pb.go
+++ b/go/test/plan/v1/plan.pb.go
@@ -198,7 +198,7 @@
//
// - A variable 'scope' of type TestCondition.Scope. This variable contains
// the information about a particular Test being tested for
- // inclusion in the test plan unit via `expresssion`.
+ // inclusion in the test plan unit via `expression`.
// - Protobuf definitions in this git project (i.e., rooted at infra/proto/).
Expression string `protobuf:"bytes,1,opt,name=expression,proto3" json:"expression,omitempty"`
XXX_NoUnkeyedLiteral struct{} `json:"-"`
@@ -246,7 +246,7 @@
Test string `protobuf:"bytes,2,opt,name=test,proto3" json:"test,omitempty"`
// The test attribute name as specified in the test.metadata.Attribute.name
//
- // attibutes are populated from test.metadata.Test.attributes.
+ // attributes are populated from test.metadata.Test.attributes.
Attributes []string `protobuf:"bytes,3,rep,name=attributes,proto3" json:"attributes,omitempty"`
XXX_NoUnkeyedLiteral struct{} `json:"-"`
XXX_unrecognized []byte `json:"-"`
@@ -355,7 +355,7 @@
//
// - A variable 'scope' of type DUTCoverageCondition.Scope. This variable
// contains the information about the set of Devices Under Test being
- // tested for acceptance via `expresssion`.
+ // tested for acceptance via `expression`.
// - Protobuf definitions in this git project (i.e., rooted at infra/proto/)
//
// ### Syntax
diff --git a/go/test/rtd/v1/invocation.pb.go b/go/test/rtd/v1/invocation.pb.go
index ef2ccac..9265041 100644
--- a/go/test/rtd/v1/invocation.pb.go
+++ b/go/test/rtd/v1/invocation.pb.go
@@ -102,7 +102,7 @@
// Contains all configuration data required to interact with a single device
// under test during a test invocation.
type DUT struct {
- // Device Under Test sepcification.
+ // Device Under Test specification.
Device *common.Device `protobuf:"bytes,1,opt,name=device,proto3" json:"device,omitempty"`
// Peripherals information about the lab deployment of the device.
Peripherals *lab.Peripherals `protobuf:"bytes,2,opt,name=peripherals,proto3" json:"peripherals,omitempty"`
diff --git a/src/lab/dut_state.proto b/src/lab/dut_state.proto
index 38f37d2..b9a8f59 100644
--- a/src/lab/dut_state.proto
+++ b/src/lab/dut_state.proto
@@ -24,7 +24,7 @@
// CR50-related configs by definition shouldn't be a state config, but a build config.
// However, we don't have a way to source it from any external configuration system,
// and it's changed frequently enough to handle cr50 tests, which makes
- // it basically imposible for manual updatings: See crbug.com/1057145 for the
+ // it basically impossible for manual updatings: See crbug.com/1057145 for the
// troubles it causes.
//
// So we temporarily set it in state config so that repair job can update it.
diff --git a/src/test/device_condition.proto b/src/test/device_condition.proto
index c3891eb..c218a55 100644
--- a/src/test/device_condition.proto
+++ b/src/test/device_condition.proto
@@ -48,7 +48,7 @@
// device.Config.hardware_features list.
repeated device.Config.HardwareFeature hardware_features = 8;
- // If not emtpy, any value in device.Config.hardware_features must not be
+ // If not empty, any value in device.Config.hardware_features must not be
// contained in this field.
repeated device.Config.HardwareFeature no_hardware_features = 9;
@@ -98,7 +98,7 @@
// the test for such a case.
// On the other hand, chromeos/infra/config is expected to be used for
// disabling tests on a specific board, regardless of versions, because of
-// temporaly infra/lab issue, for example.
+// temporary infra/lab issue, for example.
message ConfigIdCondition {
// Condition of device.PlatformId. This condition needs to be satisfied by
// device.ConfigId.platform_id.
diff --git a/src/test/metadata/v1/metadata.proto b/src/test/metadata/v1/metadata.proto
index 3bc3986..a80cde3 100644
--- a/src/test/metadata/v1/metadata.proto
+++ b/src/test/metadata/v1/metadata.proto
@@ -144,7 +144,7 @@
//
// - A variable 'scope' of type DUTCondition.Scope. This variable contains the
// information about a particular Device Under Test being tested for
- // acceptance via `expresssion`.
+ // acceptance via `expression`.
// - Protobuf definitions in this git project (i.e., rooted at infra/proto/).
//
// ### Syntax
@@ -194,7 +194,7 @@
// Protocol buffer scope for interpretation of `expression`.
//
// Scope includes the Device Under Test features that can be targeted for test
- // targetting.
+ // targeting.
message Scope {
// Device Under Test specification.
test.common.Device device = 1;
diff --git a/src/test/plan/v1/plan.proto b/src/test/plan/v1/plan.proto
index f8838a2..3b3560a 100644
--- a/src/test/plan/v1/plan.proto
+++ b/src/test/plan/v1/plan.proto
@@ -93,7 +93,7 @@
//
// - A variable 'scope' of type TestCondition.Scope. This variable contains
// the information about a particular Test being tested for
- // inclusion in the test plan unit via `expresssion`.
+ // inclusion in the test plan unit via `expression`.
// - Protobuf definitions in this git project (i.e., rooted at infra/proto/).
string expression = 1;
@@ -107,7 +107,7 @@
// The test attribute name as specified in the test.metadata.Attribute.name
//
- // attibutes are populated from test.metadata.Test.attributes.
+ // attributes are populated from test.metadata.Test.attributes.
repeated string attributes = 3;
}
}
@@ -123,7 +123,7 @@
// necessary coverage - Test Platform will determine a set of devices that
// satisfies `expression` and execute the tests in the plan on all selected
// devices.
- // - Plaform may freely choose the exact set of devices used if `expression`
+ // - Platform may freely choose the exact set of devices used if `expression`
// is satisfiable by more than one set.
// - Different tests in the plan may be executed on different sets of devices,
// as long as they all satisfy `expression` individually.
@@ -202,7 +202,7 @@
//
// - A variable 'scope' of type DUTCoverageCondition.Scope. This variable
// contains the information about the set of Devices Under Test being
- // tested for acceptance via `expresssion`.
+ // tested for acceptance via `expression`.
// - Protobuf definitions in this git project (i.e., rooted at infra/proto/)
//
// ### Syntax
diff --git a/src/test/rtd/v1/invocation.proto b/src/test/rtd/v1/invocation.proto
index 467a671..d1f3557 100644
--- a/src/test/rtd/v1/invocation.proto
+++ b/src/test/rtd/v1/invocation.proto
@@ -40,7 +40,7 @@
// Contains all configuration data required to interact with a single device
// under test during a test invocation.
message DUT {
- // Device Under Test sepcification.
+ // Device Under Test specification.
test.common.Device device =1;
// Peripherals information about the lab deployment of the device.
