1
0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-25 01:34:11 +03:00
libvirt/tests/virnetdaemondata
Daniel P. Berrangé 9c1dc67403 tests: fix misc spelling errors reported by codespell
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-10-05 10:28:43 +01:00
..
input-data-admin-server-names.json
input-data-admin.json
input-data-anon-clients.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
input-data-client-auth-pending-failure.json
input-data-client-auth-pending.json
input-data-client-ids.json
input-data-client-timestamp.json
input-data-initial.json
input-data-no-keepalive-required.json
output-data-admin-server-names.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-admin.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-anon-clients.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-client-auth-pending.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-client-ids.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-client-timestamp.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-initial.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-no-keepalive-required.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
README tests: fix misc spelling errors reported by codespell 2020-10-05 10:28:43 +01:00

   virnetservertest data files
   ===========================

The various input-data-*.json files are a record of all the historical
formats that libvirt has been able to produce data for. Every time a
new field is added to the JSON output, a *new* input data file should
be created. We must not add new fields to existing input-data files,
nor must we ever re-structure them if code changes, as we must check
new code handles the legacy formats.

The various output-data-*.json files are the record of what the *new*
JSON output should look like for the correspondingly named input-data
file. It is permissible to change the existing output-data-*.json
files if the format we save in is updated.