libvirt/tests/virnetdaemondata
Martin Kletzander f007940cb2 rpc: Fix error message in virNetServerSetClientLimits
That way it actually fits with what the condition checks for.

Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
2023-01-02 20:39:09 +01:00
..
input-data-admin-server-names.json
input-data-admin.json
input-data-anon-clients.json
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-invalid-max-clients-failure.json rpc: Fix error message in virNetServerSetClientLimits 2023-01-02 20:39:09 +01:00
input-data-no-keepalive-required.json
output-data-admin-server-names.json
output-data-admin.json
output-data-anon-clients.err tests: Check error message in virnetdaemontest 2023-01-02 20:39:08 +01:00
output-data-anon-clients.json
output-data-client-auth-pending-failure.err tests: Check error message in virnetdaemontest 2023-01-02 20:39:08 +01:00
output-data-client-auth-pending.json
output-data-client-ids.json
output-data-client-timestamp.json
output-data-initial.json
output-data-invalid-max-clients-failure.err rpc: Fix error message in virNetServerSetClientLimits 2023-01-02 20:39:09 +01:00
output-data-no-keepalive-required.json
README

   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.