You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -163,13 +165,34 @@ Run `python3 -m oc_config_validate -models` to get a list of the versions (revis
163
165
#### Timing in gNMI Sets and Gets
164
166
165
167
The Target can take some time to process configurations done via gNMI Set messages. By default, `oc_config_validate` waits 10 seconds after a successful gNMI Set message.
166
-
This time is customized with the `gnmi_set_cooldown_secs` option in the targe configuration or in a command line argument.
168
+
This time is customized with the `gnmi_set_cooldown_secs` option in the target configuration or in a command line argument.
167
169
168
170
Similarly, the Target can take some time to show the expected values in a gNMI Get message.
169
171
Some testcases have a retry mechanism, that will repeat the gNMI Get message and comparisons (against an OC model, against an expected JSON text, or both) until it succeeds or times out.
170
172
171
173
See [here](https://github.com/google/gnxi/blob/master/oc_config_validate/docs/testclasses.md) for more details.
172
174
175
+
#### Timestamped Logging gNMI messages
176
+
177
+
With `log_gnmi` option in the command line argument, all gNMI Messages sent and received are logged with a relative timestamp to the beginning of the test.
178
+
179
+
The gNMI messages logs are in the format `[<relative_time_secs>]gNMI <Operation>(<xpath(s)>) =>|=< <[values]>`. E.g.:
0 commit comments