be68667153
Complete test result messages have required "system" field. Related running, queued and error messages should define same "system" values. This is required by Greenwave which in addition to item + type + testcase values, also distinguishes test results by unique scenario + system_architecture + system_variant values. For example, if there is a test result with status RUNNING and undefined "system", it would be considered missing by Greenwave until test a completed (or error) result with undefined "system" is published. A message with any other "system" value would be considered as a result of a different test.
44 lines
1,000 B
YAML
44 lines
1,000 B
YAML
$id: fedora-update.test.error
|
|
$schema: http://json-schema.org/draft-07/schema#
|
|
|
|
description:
|
|
Testing has aborted, it was not finished, e.g. because of infrastructure
|
|
error, CI system error, etc. Note that a test failure is not an error.
|
|
Test failures should be exposed under the fedora-update.test.complete
|
|
topic. This is a mandatory message.
|
|
|
|
properties:
|
|
contact:
|
|
$ref: contact.json
|
|
run:
|
|
$ref: run.json
|
|
artifact:
|
|
$ref: fedora-update.json
|
|
pipeline:
|
|
$ref: pipeline.json
|
|
test:
|
|
$ref: test-common.json
|
|
error:
|
|
$ref: error.json
|
|
notification:
|
|
$ref: notification.json
|
|
generated_at:
|
|
$ref: common.json#/properties/generated_at
|
|
version:
|
|
$ref: common.json#/properties/version
|
|
system:
|
|
type: array
|
|
items:
|
|
$ref: system.json
|
|
|
|
required:
|
|
- contact
|
|
- run
|
|
- artifact
|
|
- pipeline
|
|
- test
|
|
- error
|
|
- generated_at
|
|
- version
|
|
|
|
type: object
|