Hello again,
I'd like to verify my package is still installable. I have come up with:
--- - hosts: localhost roles: - role: standard-test-basic tags: - classic required_packages: - <tested_pkg_name>
This should be enough to get the new package installed or the CI job fails. Is that assumption correct?
Cau Miro,
On Tue, Apr 28, 2020 at 12:20 PM Miro Hrončok mhroncok@redhat.com wrote:
Hello again,
I'd like to verify my package is still installable. I have come up with:
- hosts: localhost roles:
- role: standard-test-basic tags:
required_packages:
- classic
<tested_pkg_name>
This should be enough to get the new package installed or the CI job fails. Is that assumption correct?
I think that should work, but I will let others give you an authoritative answer here (my knowledge of STR is limited).
However, we are introducing new generic tests that should land in Fedora next month. One of them will be the "installability test" that @Andrei Stepanov astepano@redhat.com created for RHEL.
Thanks, Michal
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On 28. 04. 20 12:31, Michal Srb wrote:
Cau Miro,
o/
On Tue, Apr 28, 2020 at 12:20 PM Miro Hrončok <mhroncok@redhat.com mailto:mhroncok@redhat.com> wrote:
Hello again, I'd like to verify my package is still installable. I have come up with: --- - hosts: localhost roles: - role: standard-test-basic tags: - classic required_packages: - <tested_pkg_name> This should be enough to get the new package installed or the CI job fails. Is that assumption correct?I think that should work, but I will let others give you an authoritative answer here (my knowledge of STR is limited).
Problems so far:
- a failure of this is reported as error in cloud-image-compose, not a failure - the dependency problem is very well hidden (was not able to find it yet)
However, we are introducing new generic tests that should land in Fedora next month. One of them will be the "installability test" that @Andrei Stepanov mailto:astepano@redhat.com created for RHEL.
Would love to see those. Where can I read about the plans?
On Tue, 2020-04-28 at 13:02 +0200, Miro Hrončok wrote:
However, we are introducing new generic tests that should land in Fedora next month. One of them will be the "installability test" that @Andrei Stepanov mailto:astepano@redhat.com created for RHEL.
Would love to see those. Where can I read about the plans?
I'd be interested in that too, given that this is an area with "fun" corner cases, which is why I've never implemented this in openQA. The main problem area is intentionally conflicting packages - especially if a package from an update intentionally conflicts with packages from the base image used for the test, or (depending on exactly how you test) if subpackages from a given source package intentionally conflict with each other.
Well, I think this is not really rocket science…
You test: * GA image → install foo (from GA) → update everything what is coming from foo.src.rpm * GA image → install foo (with enabled updates)
And multiply this foo by all possible combinations of installation of subpackages.
By the way, this does not really have to be executed in any real system, all what you need is repomd. The only thing where VM/container/whatsoever might be useful is detecting file conflicts, but those cases are so rare that I would not aim for them in the beginning at all.
On Tue, Apr 28, 2020 at 5:28 PM Adam Williamson adamwill@fedoraproject.org wrote:
On Tue, 2020-04-28 at 13:02 +0200, Miro Hrončok wrote:
However, we are introducing new generic tests that should land in Fedora next month. One of them will be the "installability test" that @Andrei Stepanov mailto:astepano@redhat.com created for RHEL.
Would love to see those. Where can I read about the plans?
I'd be interested in that too, given that this is an area with "fun" corner cases, which is why I've never implemented this in openQA. The main problem area is intentionally conflicting packages - especially if a package from an update intentionally conflicts with packages from the base image used for the test, or (depending on exactly how you test) if subpackages from a given source package intentionally conflict with each other. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On Tue, Apr 28, 2020 at 5:28 PM Adam Williamson adamwill@fedoraproject.org wrote:
On Tue, 2020-04-28 at 13:02 +0200, Miro Hrončok wrote:
However, we are introducing new generic tests that should land in
Fedora next
month. One of them will be the "installability test" that @Andrei
Stepanov
mailto:astepano@redhat.com created for RHEL.
Would love to see those. Where can I read about the plans?
I'd be interested in that too, given that this is an area with "fun" corner cases, which is why I've never implemented this in openQA. The main problem area is intentionally conflicting packages - especially if a package from an update intentionally conflicts with packages from the base image used for the test, or (depending on exactly how you test) if subpackages from a given source package intentionally conflict with each other.
I think that is fine -- the idea is to show test results to package maintainers and let them decide whether the findings are real bugs or something they expected to happen. They know their stuff :)
Thanks, Michal
-- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
On Tue, Apr 28, 2020 at 1:03 PM Miro Hrončok mhroncok@redhat.com wrote:
On 28. 04. 20 12:31, Michal Srb wrote:
Cau Miro,
o/
On Tue, Apr 28, 2020 at 12:20 PM Miro Hrončok <mhroncok@redhat.com mailto:mhroncok@redhat.com> wrote:
Hello again, I'd like to verify my package is still installable. I have come upwith:
--- - hosts: localhost roles: - role: standard-test-basic tags: - classic required_packages: - <tested_pkg_name> This should be enough to get the new package installed or the CI jobfails.
Is that assumption correct?I think that should work, but I will let others give you an
authoritative answer
here (my knowledge of STR is limited).
Problems so far:
- a failure of this is reported as error in cloud-image-compose, not a
failure
- the dependency problem is very well hidden (was not able to find it yet)
However, we are introducing new generic tests that should land in Fedora
next
month. One of them will be the "installability test" that @Andrei
Stepanov
mailto:astepano@redhat.com created for RHEL.
Would love to see those. Where can I read about the plans?
It's part of the "Common repository and common format for generic tests" initiative that was announced in [1].
The email doesn't mention the installability test explictly, but it's one of the generic tests that we would like to introduce.
Thanks, Michal
[1]: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org/thr...
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
-
Adam Williamson -
Igor Gnatenko -
Michal Srb -
Miro Hrončok