binutils tests

$ tmt lint --failed-only --outcome-only=fail --outcome-only=warn

$ tmt plan show -vv
$ tmt test show -vv

$ tmt -c distro=$DISTRO -c arch=$ARCH -vv run discover
$ tmt -c distro=$DISTRO -c arch=$ARCH -vv run plan -n '/plans/build-gating/common'
$ tmt -c distro=$DISTRO -c arch=$ARCH -vv run plan -n '/plans/build-gating/kernel-rebuild'
$ tmt -c distro=$DISTRO -c arch=$ARCH -vv run plan -n '/plans/regression'

Adding new tests

Please, follow these rules:

• always define summary andduration fields
• you may define custom description field
• always use + form of list-like fields (require, link, ...): ```yaml # No: tag: foo

tag: - foo

# Yes tag+: - foo `` * addverifieslinks vialink+when the test is meant to verify bugzilla or Jira issues * test applicable to collections only must addcollection-onlytag * tests sutiable for build gating must addgate-build` tag

Test template

# NOTE: DO NOT LEAVE EMPTY FIELDS, NOT EVEN COMMENTED OUT - REMOVE THEM

# TODO: Add proper summary
summary: ...

# TODO: Add a longer description if there's anythign to write about. If not,
# drop the whole field.
# description: ...

# TODO: Add proper duratio
duration: ...

# tag+:
  # TODO: if this is a test for build gating, add this tag
  # - gate-build

  # TODO: if this is a test applicable to collections-only, add this tag
  # - collection-only

# TODO: List bugs verified by the test if there are any.
# link+:
#   - verifies: https://bugzilla.redhat.com/...
#   - verifies: https://issues.redhat.com/...

# TODO: Add additional authors - or the only authors if the default contact
# is not applicable, use `contact` in that case.
# contact+:
#   - Foo Bar <foobar@redhat.com>

# TODO: Add extra required packages
# require+:
#   - ...

# adjust+:
  # TODO: If the test is relevant for one architecture only, use the following rule
  # - when: arch == ...
  #   enabled: false

  # TODO: If the test is relevant for collections only, use the following rule
  # - when: collection is not defined
  #   enabled: false

State of support