Hi Matt,
I wanted to follow up on this question you had on DevConf.US 22 [1].
We would like to make these stats available to the community, unfortunately
now it is just a DB query to our Testing Farm database.
So, currently that is: 449 packages
I am attaching lists for proof.
There are also a bunch of shared tmt tests in tests dist-git tests
namespace, seems 83 of them:
https://src.fedoraproject.org/projects/tests/%2A
Best regards,
/M
[1] https://youtu.be/M2FXrUs3YjE?t=3121
--
Miroslav Vadkerti :: Senior Principal QE :: Testing Farm / Linux QE
IRC mvadkert #tft #tmt #osci :: Mobile +420 773 944 252
Remote Czech Republic :: Red Hat Czech s.r.o
Dear all,
You are kindly invited to the meeting:
Fedora CI SIG on 2022-09-07 from 09:30:00 to 10:00:00 America/Chicago
At fedora-ci(a)irc.libera.chat
The meeting will be about:
Fedora CI SIG meeting
More information available at: https://fedoraproject.org/wiki/SIGs/CI
Introduce projects, discuss issues and plans for the future.
Please add topics to discuss into our etherpad: https://etherpad.gnome.org/p/fedora-ci
This meeting is recurring for every other Wednesday.
Source: https://calendar.fedoraproject.org//meeting/9901/
On Fri, 2022-08-26 at 14:58 -0400, Ben Beasley wrote:
> When a Bodhi update is gated on required tests that seem to remain
> “missing” indefinitely, is there anything I can do to re-try them? Or do
> I just have to attempt to waive the missing test results?
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-014e78ee9d
> <https://bodhi.fedoraproject.org/updates/FEDORA-2022-014e78ee9d>
>
> The corresponding update for F38 worked fine. The necessary test results
> appeared and the update passed gating after about 20 minutes.
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-2eed8152f6
Not sure why the re-run tests button is missing and the test didn't
trigger in the first place, but CCing the CI list where someone might
know. Waiving the result seems reasonable, especially since it passed
on Rawhide.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
On Fri, 2022-08-26 at 14:58 -0400, Ben Beasley wrote:
> When a Bodhi update is gated on required tests that seem to remain
> “missing” indefinitely, is there anything I can do to re-try them? Or do
> I just have to attempt to waive the missing test results?
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-014e78ee9d
> <https://bodhi.fedoraproject.org/updates/FEDORA-2022-014e78ee9d>
>
> The corresponding update for F38 worked fine. The necessary test results
> appeared and the update passed gating after about 20 minutes.
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-2eed8152f6
Not sure why the re-run tests button is missing and the test didn't
trigger in the first place, but CCing the CI list where someone might
know. Waiving the result seems reasonable, especially since it passed
on Rawhide.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
Dear all,
You are kindly invited to the meeting:
Fedora CI SIG on 2022-08-24 from 09:30:00 to 10:00:00 America/Chicago
At fedora-ci(a)irc.libera.chat
The meeting will be about:
Fedora CI SIG meeting
More information available at: https://fedoraproject.org/wiki/SIGs/CI
Introduce projects, discuss issues and plans for the future.
Please add topics to discuss into our etherpad: https://etherpad.gnome.org/p/fedora-ci
This meeting is recurring for every other Wednesday.
Source: https://calendar.fedoraproject.org//meeting/9901/
Dear all,
You are kindly invited to the meeting:
Fedora CI SIG on 2022-08-10 from 09:30:00 to 10:00:00 America/Chicago
At fedora-ci(a)irc.libera.chat
The meeting will be about:
Fedora CI SIG meeting
More information available at: https://fedoraproject.org/wiki/SIGs/CI
Introduce projects, discuss issues and plans for the future.
Please add topics to discuss into our etherpad: https://etherpad.gnome.org/p/fedora-ci
This meeting is recurring for every other Wednesday.
Source: https://calendar.fedoraproject.org//meeting/9901/
Hi folks! I was wondering if anyone from the CI team will be at
devconf.us in Boston in August. I have a talk scheduled that's intended
to be a general overview of current automated testing/CI processes in
Fedora, and it'd be great if someone from CI team could co-present on
the details of Fedora CI - I can cover it if nobody will be there, but
probably not as accurately as a specialist.
Thanks a lot!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
Hello,
in this PR:
https://src.fedoraproject.org/rpms/python3.11/pull-request/64
In this Zuul CI job:
https://fedora.softwarefactory-project.io/zuul/build/69d10a1f21e14d959e0223…
I see:
Running abidiff inspection... FAIL
In this rpminspect report:
https://fedora.softwarefactory-project.io/rpminspect-report/?url=https://fe…
(JSON attached)
I see abidiff results as listed as "OK":
"ABI comparison ended unexpectedly."
"Command: abidiff
/var/tmp/rpminspect/local.KjDvKK/before/x86_64/python3-libs-3.11.0~b3-8.fc37.x86_64//usr/lib64/libpython3.11.so.1.0
/var/tmp/rpminspect/local.KjDvKK/after/x86_64/python3-libs-3.11.0~b4-1.fc37.x86_64//usr/lib64/libpython3.11.so.1.0
Functions changes summary: 0 Removed, 0 Changed, 0 Added function Variables
changes summary: 0 Removed, 0 Changed, 0 Added variable Function symbols
changes summary: 0 Removed, 2 Added function symbols not referenced by debug
info Variable symbols changes summary: 0 Removed, 0 Added variable symbol not
referenced by debug info 2 Added function symbols not referenced by debug info:
[A] _PyImport_GetModuleAttr [A] _PyImport_GetModuleAttrString "
What does that even mean?
Why is the result a FAIL when it is listed as OK?
Why is it listed as OK, when it says it ended unexpectedly?
What do I read from the results? Is it OK, not OK, broken?
Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Hello,
I'm debugging tests for my package by pushing and force-pushing to
a PR
https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/1
Things worked fine today a number of times, but then a red "error"
appeared, and since after the last push nothing which would indicate
that tests are being run is shown there.
Is there currently some outage of the CI / tests, or did I break
something in my code?
--
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat
Hello,
please bare with me because my Ansible skills are close to none. I only use it
for Fedora CI.
I've read
https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html…
I have this (simplified) tests.yml:
---
- hosts: localhost
roles:
- role: standard-test-basic
tests:
- smoke:
dir: python/smoke
run: VERSION=3.11 ./venv.sh
required_packages:
- python3.11
- python3.11-devel
Full version in
https://src.fedoraproject.org/rpms/python3.11/blob/rawhide/f/tests/tests.yml
I would like to replace all occurrences of 3.11 with a variable:
---
- hosts: localhost
roles:
- role: standard-test-basic
tests:
- smoke:
dir: python/smoke
run: VERSION={{ pybasever }} ./venv.sh
required_packages:
- python{{ pybasever }}
- python{{ pybasever }}-devel
But where do I put pybasever: '3.11' exactly?
Bonus question: Can I read the tested package name and regex it into the variable?
pybasever: {{ xxx_package_name|pex_regex_replace('^python', '') }}
Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok