binutils/README.md
2023-10-12 12:45:53 +02:00

123 lines
3.6 KiB
Markdown

# binutils tests
##
```shell
$ 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` and`duration` 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
```
* add `verifies` links via `link+` when the test is meant to verify bugzilla or Jira issues
* test applicable to collections only must add `collection-only` tag
* tests sutiable for build gating must add `gate-build` tag
### Test template
```yaml
# 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
| Distro | Flavor | State |
| --------------- | -------------- | :---: |
| RHEL-9.3.0 | system | yes |
| RHEL-9.3.0 | gcc-toolset-13 | yes |
| RHEL-9.3.0 | gcc-toolset-12 | yes |
| RHEL-9.3.0 | gcc-toolset-11 | |
| RHEL-9.2.0 | system | yes |
| RHEL-9.2.0 | gcc-toolset-12 | yes |
| RHEL-9.2.0 | gcc-toolset-11 | yes |
| RHEL-9.1.0 | system | yes |
| RHEL-9.1.0 | gcc-toolset-11 | yes |
| RHEL-8.9.0 | system | yes |
| RHEL-8.9.0 | gcc-toolset-13 | yes |
| RHEL-8.9.0 | gcc-toolset-12 | |
| RHEL-8.9.0 | gcc-toolset-11 | |
| RHEL-8.8.0 | system | yes |
| RHEL-8.8.0 | gcc-toolset-12 | |
| RHEL-8.8.0 | gcc-toolset-11 | |
| RHEL-8.7.0 | system | yes |
| RHEL-8.7.0 | gcc-toolset-11 | |
| RHEL-7.9 | system | |
| RHEL-7.9 | devtoolset-13 | |
| RHEL-6.10 | system | |
| Fedora Rawhide | system | yes |
| Fedora 39 | system | yes |
| Fedora 38 | system | yes |
| Fedora 37 | system | |
| CentOS Stream 9 | system | yes |
| CentOS Stream 9 | gcc-toolset-13 | |
| CentOS Stream 9 | gcc-toolset-12 | |
| CentOS Stream 9 | gcc-toolset-11 | |
| CentOS Stream 8 | system | yes |
| CentOS Stream 8 | gcc-toolset-13 | |
| CentOS Stream 8 | gcc-toolset-12 | |
| CentOS Stream 8 | gcc-toolset-11 | |