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