Fedora 28 updates-testing report
The following Fedora 28 Security updates need testing: Age URL 355 https://bodhi.fedoraproject.org/updates/FEDORA-2018-d510cfd7eb jgraphx-3.6.0.0-6.fc28 304 https://bodhi.fedoraproject.org/updates/FEDORA-2018-d7aeaa74da nodejs-brace-expansion-1.1.11-1.fc28 303 https://bodhi.fedoraproject.org/updates/FEDORA-2018-bc073fdc1a nodejs-atob-2.1.1-1.fc28 179 https://bodhi.fedoraproject.org/updates/FEDORA-2018-cc4b7af297 xerces-c27-2.7.0-28.fc28 131 https://bodhi.fedoraproject.org/updates/FEDORA-2018-aa3752ac3c nginx-1.14.1-1.fc28 111 https://bodhi.fedoraproject.org/updates/FEDORA-2018-cc86ef9e22 squid-4.4-1.fc28 107 https://bodhi.fedoraproject.org/updates/FEDORA-2018-b18f9dd65b tomcat-8.5.35-1.fc28 38 https://bodhi.fedoraproject.org/updates/FEDORA-2019-86412405d5 bind-9.11.5-4.P4.fc28 26 https://bodhi.fedoraproject.org/updates/FEDORA-2019-b2d986c3e9 freerdp-2.0.0-49.20190304git435872b.fc28 gnome-boxes-3.28.5-2.fc28 pidgin-sipe-1.24.0-3.fc28 remmina-1.3.3-1.fc28 25 https://bodhi.fedoraproject.org/updates/FEDORA-2019-63029a7692 libu2f-host-1.1.8-1.fc28 25 https://bodhi.fedoraproject.org/updates/FEDORA-2019-694e3aa4e8 ntp-4.2.8p13-1.fc28 12 https://bodhi.fedoraproject.org/updates/FEDORA-2019-3348cb4934 libssh2-1.8.1-1.fc28 11 https://bodhi.fedoraproject.org/updates/FEDORA-2019-c595a93536 libarchive-3.3.3-6.fc28 11 https://bodhi.fedoraproject.org/updates/FEDORA-2019-86f32cbab1 python3-3.6.8-3.fc28 9 https://bodhi.fedoraproject.org/updates/FEDORA-2019-9f28451404 ghostscript-9.26-4.fc28 7 https://bodhi.fedoraproject.org/updates/FEDORA-2019-3f561ba0be golang-googlecode-go-crypto-0-0.25.20190324gitb7391e9.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-ba19e79e9a thunderbird-60.6.1-1.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd54b80806 fuse-2.9.9-1.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-46df367eed gnutls-3.6.5-3.fc28 3 https://bodhi.fedoraproject.org/updates/FEDORA-2019-8b8c774b84 aria2-1.34.0-4.fc28 3 https://bodhi.fedoraproject.org/updates/FEDORA-2019-2903a24dce clamav-0.101.2-1.fc28 3 https://bodhi.fedoraproject.org/updates/FEDORA-2019-0927602e59 chromium-73.0.3683.86-2.fc28 2 https://bodhi.fedoraproject.org/updates/FEDORA-2019-c1e6c6edd9 ntfs-3g-2017.3.23-11.fc28 The following Fedora 28 Critical Path updates have yet to be approved: Age URL 111 https://bodhi.fedoraproject.org/updates/FEDORA-2018-9f541b469b nfs-utils-2.3.3-1.rc2.fc28 75 https://bodhi.fedoraproject.org/updates/FEDORA-2019-78153d357c totem-pl-parser-3.26.2-1.fc28 67 https://bodhi.fedoraproject.org/updates/FEDORA-2019-e9c4843d39 volume_key-0.3.12-2.fc28 66 https://bodhi.fedoraproject.org/updates/FEDORA-2019-bb30467485 ostree-2019.1-2.fc28 rpm-ostree-2019.1-1.fc28 58 https://bodhi.fedoraproject.org/updates/FEDORA-2019-cb4a3023ef iproute-4.20.0-1.fc28 41 https://bodhi.fedoraproject.org/updates/FEDORA-2019-6c4e362bd0 dhcp-4.3.6-22.fc28 dnsperf-2.2.1-1.fc28 bind-dyndb-ldap-11.1-13.fc28 bind-9.11.5-2.P1.fc28 35 https://bodhi.fedoraproject.org/updates/FEDORA-2019-68e7e119bb udisks2-2.7.6-3.fc28 21 https://bodhi.fedoraproject.org/updates/FEDORA-2019-c4107ac9d3 koji-1.17.0-5.fc28 20 https://bodhi.fedoraproject.org/updates/FEDORA-2019-cb98bf5ace fedfind-4.2.2-1.fc28 python-productmd-1.20-1.fc28 17 https://bodhi.fedoraproject.org/updates/FEDORA-2019-d95d1a1e0e libseccomp-2.4.0-0.fc28 17 https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea42f2be87 fedora-repos-28-7 12 https://bodhi.fedoraproject.org/updates/FEDORA-2019-e60ecc03b4 python-productmd-1.21-1.fc28 12 https://bodhi.fedoraproject.org/updates/FEDORA-2019-457ab67a6c psmisc-23.1-3.1.fc28 12 https://bodhi.fedoraproject.org/updates/FEDORA-2019-3348cb4934 libssh2-1.8.1-1.fc28 12 https://bodhi.fedoraproject.org/updates/FEDORA-2019-155f8c72c2 osinfo-db-20190319-1.fc28 11 https://bodhi.fedoraproject.org/updates/FEDORA-2019-86f32cbab1 python3-3.6.8-3.fc28 11 https://bodhi.fedoraproject.org/updates/FEDORA-2019-c595a93536 libarchive-3.3.3-6.fc28 9 https://bodhi.fedoraproject.org/updates/FEDORA-2019-a7ea886082 polkit-0.115-2.3.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-46df367eed gnutls-3.6.5-3.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-a0ae4e93b9 sssd-1.16.4-2.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-812d4a31f7 audit-2.8.5-2.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd54b80806 fuse-2.9.9-1.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-ba19e79e9a thunderbird-60.6.1-1.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-4574633aa0 pcre2-10.32-9.fc28 5 https://bodhi.fedoraproject.org/updates/FEDORA-2019-764312c529 nspr-4.21.0-1.fc28 nss-3.43.0-1.fc28 3 https://bodhi.fedoraproject.org/up
Re: dnf system-upgrade download --refresh --releasever=30 errors
On 4/1/19 2:00 PM, Brandon Johnson wrote: I ran into this as well just today upgrading a test system 29 to 30. Was a bug ever opened for this? I can go hunt for it or open a new one but Id rather just add to the existing... https://bugzilla.redhat.com/show_bug.cgi?id=1625259 I ran into this when upgrading a system to F29 because there were duplicate entries due to a failed upgrade attempt earlier. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: qemu
On 4/1/19 11:07 AM, pmkel...@frontier.com wrote: I got curious about qemu today. I read a little about it at the qemu website. Then I checked to see if their was any qemu on my fedora workstation. I found that there are many qemu items installed. From the names of the installed items and what I read at the website, I started guessing that fedora may be running on top of qemu. Is this right? Not correct. qemu appears to have been split into many modules that provide different parts of the functionality. Unless you're running Fedora in Boxes or something similar, you're not using qemu right now. I think libvirtd is started by default in workstation though, but qemu won't be running until you create and start a VM. One guess was that qemu might me on top of the hardware with the kernel and fedora on top of qemu. Only if you're running Fedora on a virtual machine. And even in that case, there's still another kernel between qemu and the hardware. I suppose that qemu might be used for a few things where integrating them into the bigger structure might not be feasible, or qemu might just be the basis for Boxes. qemu is the basis for Boxes and by default libvirt as well. qemu is the software piece that emulates the hardware for a virtual machine. It uses kvm when possible to run faster. Is any of this close or am I on the wrong track? Is their anything I can read that will help me understand the software hierarchy of fedora? I'm not sure what you mean by the software hierarchy. It's the same as most other Linux distributions. The Linux kernel runs directly on the hardware and everything else runs from there. If you run Fedora in a virtual machine, then the host kernel runs on the hardware, qemu runs on that kernel, then qemu starts the virtual BIOS which runs another Linux kernel and all the other software on top of that. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: dnf system-upgrade download --refresh --releasever=30 errors
Brandon Johnson composed on 2019-04-01 17:00 (UTC-0400): > Was a bug ever opened for this? https://bugzilla.redhat.com/show_bug.cgi?id=1667300 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: dnf system-upgrade download --refresh --releasever=30 errors
I ran into this as well just today upgrading a test system 29 to 30. Was a bug
ever opened for this? I can go hunt for it or open a new one but Id rather
just add to the existing...
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: firefox
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: hplip
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: libsane-hpaio
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: hplip-libs
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: tpm2-abrmd-selinux
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: python3-hawkey
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: python3-libdnf
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: libdnf
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
callback
self._elemProgress(key, amount)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 303, in
_elemProgress
transaction_list = self._extract_cbkey(key)
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 244, in
_extract_cbkey
raise RuntimeError("TransactionItem not found for key: %s" % cbkey)
RuntimeError: TransactionItem not found for key: kernel-tools
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/yum/rpmtrans.py", line 260, in
ca
Re: Blocking criteria proposal for F30+: Printing
On Mon, 2019-02-11 at 11:56 -0500, Stephen Gallagher wrote: > On Fri, Nov 16, 2018 at 7:18 PM Adam Williamson > wrote: > > On Thu, 2018-09-20 at 08:33 -0400, Stephen Gallagher wrote: > > > There was a bug[1] filed recently that indicated that printing was > > > broken on certain printers. As a result of that discussion, it became > > > apparent that there was no criteria for printing to work at all, which > > > seems like an oversight. > > > > > > I discussed this briefly with Matthias Clasen this morning and he > > > agreed that this should be treated as blocking for Workstation. > > > > > > I'd like to propose that we add the following criteria to Beta for Fedora > > > 30+: > > > * Printing must work on at least one printer available to Fedora QA. > > > "Work" is defined as the output from the device matching a preview > > > shown on the GNOME print preview display. (Note that differences in > > > color reproduction are not considered "non-working".) > > > > > > and this to Final for Fedora 30+: > > > * Printing must work on at least one printer using each of the > > > following drivers: > > > (I don't know which ones to specify here, but we ought to try to > > > figure out a cross-section that covers a large swath of our expected > > > user base). > > > > So as with the optical media proposal we had quite a lively discussion > > on this one, then it got stuck a bit. Stephen, can you take a look at > > all the followups and either restate or revise the proposal? Thanks! > > Sorry that it's taken me so long to get back to this. > > I think the feedback on this has been mostly positive on the Beta > criteria, but I'd like to tweak the phrasing a bit and see if this > comes off more favorable: > > I'd like to propose that we add the following criteria to Beta for Fedora 30+: > * Printing must work on at least one printer available to Fedora QA. > "Work" is defined as the output from the device matching a preview > shown on the GNOME print preview display. (Note that differences in > color reproduction are not considered "non-working".) > > and this to Final for Fedora 30+: > * Printing must work on at least one printer using each of the > following drivers: > - The built-in print-to-PDF driver > - The generic IPP driver > > To clarify, this does not mean that all printers need to function > properly that use the IPP driver, just that at least one does (so we > know that printing as a whole is unbroken). Contrary to the first > proposal, we won't specify any particular hardware makes or models > that must work. > > How does that sound to people? There was broad support for this proposal both on lists and in meetings, so I am now implementing it with minor tweaks. Thanks Stephen! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: "Basic graphics mode" feature and criterion discussion
On Mon, Apr 1, 2019 at 3:04 PM Adam Williamson
wrote:
> So, here's the specific text I propose. At Basic we would change this
> requirement:
>>
> To read only:
>
> "The boot menu for all release-blocking installer and live images
> should include an entry which causes both installation and the
> installed system to use a generic, highly compatible video driver (such
> as 'vesa')."
>
This seems reasonable to me. +1
> At Final we would add this requirement:
>
> "The generic video driver option ('basic graphics mode') on all
> release-blocking installer and live images must function as intended
> (launching the installer or desktop and attempting to use a generic
> driver), and there must be no bugs that clearly prevent the installer
> or desktop from being reached in this configuration on all systems or
> on wide classes of hardware."
>
Am I correct in my interpretation that this failing on a narrow set of
hardware or configurations would NOT be considered a blocker?
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
Pronouns: he/him
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: "Basic graphics mode" feature and criterion discussion
On Tue, 2019-03-26 at 14:30 -0600, Chris Murphy wrote:
> My two cents:
>
> If there's a fallback option, and if the user selects it, they
> shouldn't end up in an unambiguous state. Right now we're seeing
> systems hanging. I'd rather see a crash than a hang where the user
> can't get to a shell, and sees no useful information on the screen
> that tells them why they're hung up; or even generically that "by now
> you should see a login screen and if you don't we've faceplanted
> somewhere, sorry".
>
> Maybe split the criterion:
>
> Basic criterion: installation media must have a basic video boot entry
> that uses the accepted fallback boot parameter(s), e.g. nomodeset. The
> criterion just means the media must have the menu entry, and that it
> passes something intentional for this purpose as a boot parameter.
>
> Final criterion: installation media's basic video boot entry should
> either work (we get a successful graphical boot), or it should
> faceplant in some unambiguous way.
>
> If it's not possible to ensure basic video either works as intended or
> faceplants unambiguously; then I suggest dropping any beta or final
> criterion. And also I wonder if it's at all useful to include some
> kind of heads up description for the basic video boot entry? Like,
> "this may not work at all" or "wait 5 minutes for graphical boot,
> after 10 minutes assume it failed". Haha - I have no idea. Just
> something so they aren't waiting around going WTF? Now what?
So kinda aggregating all the response to this discussion, I propose we
go with a modified version of Chris' proposal.
1. We retain the 'entry must exist' part of the criterion at Basic (but
at that point it does not have to *work* - the idea is to ensure it's
testable so we catch bugs in it at that point)
2. We move the rest of the criterion to Final and tweak it a bit to
specify that it must be at least somewhat capable of reaching the
installer or desktop. We do not adopt Chris' "or faceplant
unambiguously" proposal, people seemed to prefer just requiring it to
work.
So, here's the specific text I propose. At Basic we would change this
requirement:
"The boot menu for all supported installer and live images should
include an entry which causes both installation and the installed
system to use a generic, highly compatible video driver (such as
'vesa'). This mechanism should work correctly, launching the installer
or desktop and attempting to use the generic driver."
To read only:
"The boot menu for all release-blocking installer and live images
should include an entry which causes both installation and the
installed system to use a generic, highly compatible video driver (such
as 'vesa')."
i.e. remove the second sentence (and change 'supported' to 'release-
blocking' - that is a better form of words that should have been used
all along).
At Final we would add this requirement:
"The generic video driver option ('basic graphics mode') on all
release-blocking installer and live images must function as intended
(launching the installer or desktop and attempting to use a generic
driver), and there must be no bugs that clearly prevent the installer
or desktop from being reached in this configuration on all systems or
on wide classes of hardware."
How does that sound to everyone? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Problem participating in the QA meetings
On 4/1/19 10:37 AM, pmkel...@frontier.com wrote: > I have been lurking at the last few QA meetings, but I must still be > missing something. I followed all the reference pages people were kind > enough to send me. I have Hex Chat set up and I registered at the > website. In fact when I re-did the registration command today, it said > the tablepc is already registered. You may be missing the 'identify' step. After your irc nick is registered, you need to identify to show that it's you (and not some random person trying to use your nick). /msg nickserv identify password where password is the one you setup when you registered. > I can watch the conversations in the discussion panel. I can type > something and it will appear in the discussion panel, but it seems like > no one else can see what I said. Also my name doesn't appear on the list > of attendees when the minutes come out. The only clue I have is that my > user name appears in red. I suppose that might be to mark what I type. > > Any help will be appreciated. Yeah, sorry about this... spammers made us set many of the channels so that registered/identified people only can 'speak'. ;( kevin signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: qemu
On Mon, 2019-04-01 at 14:07 -0400, pmkel...@frontier.com wrote: > I got curious about qemu today. I read a little about it at the qemu > website. Then I checked to see if their was any qemu on my fedora > workstation. I found that there are many qemu items installed. From the > names of the installed items and what I read at the website, I started > guessing that fedora may be running on top of qemu. Is this right? > > One guess was that qemu might me on top of the hardware with the kernel > and fedora on top of qemu. > > I suppose that qemu might be used for a few things where integrating > them into the bigger structure might not be feasible, or qemu might just > be the basis for Boxes. > > Is any of this close or am I on the wrong track? Is their anything I can > read that will help me understand the software hierarchy of fedora? qemu runs virtual machines. In that respect it is like VMware or Virtualbox or Parallels. libvirt, virt-manager and Boxes are all higher-level tools for running and managing virtual machines that, by default, run virtual machines via qemu. When you install Fedora to an actual hardware PC and then boot it, qemu is not involved in any way. But if you create a virtual machine in virt-manager or Boxes, that virtual machine is probably run by qemu. qemu is installed by default on Workstation because Boxes is part of Workstation and uses it. Does that clarify things? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
2019-04-01 @ 15:00 UTC - Fedora QA Meeting - Minutes
== #fedora-meeting: Fedora QA Meeting == Meeting started by adamw at 15:00:30 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2019-04-01/fedora-qa.2019-04-01-15.00.log.html . Meeting summary --- * Roll call (adamw, 15:00:39) * Previous meeting follow-up (adamw, 15:08:38) * "adamw to work with sgallagh on putting those [printing] criteria into practice [i.e. production]" - not yet done, we will do it this week (adamw, 15:11:53) * "adamw and sgallagh to find or write test cases to back the printing criteria" - not yet done, we will also try and work on that soon (adamw, 15:12:04) * ACTION: adamw to put proposed printing criteria into production (adamw, 15:12:20) * ACTION: adamw to get printing test cases written and added to matrices (adamw, 15:12:31) * "adamw to ask sumantro to make contingency plans for upcoming test days if composes are still not available" - that got sorted out in the end, we had images for the test days (adamw, 15:13:12) * Fedora 30 status (adamw, 15:17:38) * Fedora 30 Beta will be released tomorrow (adamw, 15:17:44) * Common Bugs page is ready: https://fedoraproject.org/wiki/Common_F30_bugs (adamw, 15:17:57) * otherwise no news on Fedora 30, we believe it is currently in solid shape and will move forward with Final testing (adamw, 15:23:14) * Release criteria / test case proposal status (adamw, 15:24:24) * as noted in 'previous meeting follow-up', the printing criteria process is still ongoing (adamw, 15:24:40) * wide agreement at meeting that the existing 'basic graphics' criterion should apply more or less unmodified at Final (adamw, 15:31:18) * ACTION: adamw to implement move of 'basic graphics' criterion to Final and follow up on mailing lists (adamw, 15:31:52) * Test Day / community event status (adamw, 15:34:18) * Silverblue test day will be 2019-04-05 (adamw, 15:35:19) * Modularity test day completed successfully (adamw, 15:35:26) * Modularity test day results suggest many modules are broken (including Docker), we are concerned about this (adamw, 15:39:36) * LINK: https://communityblog.fedoraproject.org/modularity-hackfest-march-2019/ (sgallagh, 15:49:06) * ACTION: lruzicka and sumantro to look over specific issues that came up in the modularity test day and talk to sgallagh about possible improvements, especially re. modules with no default profile (adamw, 15:49:17) * Open floor (adamw, 15:54:55) Meeting ended at 16:00:07 UTC. Action Items * adamw to put proposed printing criteria into production * adamw to get printing test cases written and added to matrices * adamw to implement move of 'basic graphics' criterion to Final and follow up on mailing lists * lruzicka and sumantro to look over specific issues that came up in the modularity test day and talk to sgallagh about possible improvements, especially re. modules with no default profile Action Items, by person --- * adamw * adamw to put proposed printing criteria into production * adamw to get printing test cases written and added to matrices * adamw to implement move of 'basic graphics' criterion to Final and follow up on mailing lists * lruzicka * lruzicka and sumantro to look over specific issues that came up in the modularity test day and talk to sgallagh about possible improvements, especially re. modules with no default profile * sgallagh * lruzicka and sumantro to look over specific issues that came up in the modularity test day and talk to sgallagh about possible improvements, especially re. modules with no default profile * sumantro * lruzicka and sumantro to look over specific issues that came up in the modularity test day and talk to sgallagh about possible improvements, especially re. modules with no default profile * **UNASSIGNED** * (none) People Present (lines said) --- * adamw (85) * lruzicka (36) * sgallagh (35) * cmurf (33) * zodbot (14) * sumantro (12) * kparal (10) * coremodule (6) * satellit (5) * frantisekz (5) * tflink (2) * jlanda (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
qemu
I got curious about qemu today. I read a little about it at the qemu website. Then I checked to see if their was any qemu on my fedora workstation. I found that there are many qemu items installed. From the names of the installed items and what I read at the website, I started guessing that fedora may be running on top of qemu. Is this right? One guess was that qemu might me on top of the hardware with the kernel and fedora on top of qemu. I suppose that qemu might be used for a few things where integrating them into the bigger structure might not be feasible, or qemu might just be the basis for Boxes. Is any of this close or am I on the wrong track? Is their anything I can read that will help me understand the software hierarchy of fedora? Have a Great Day! Pat (tablepc) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora 30-20190401.n.0 compose check report
Missing expected images: Atomichost qcow2 x86_64 Atomichost raw-xz x86_64 Failed openQA tests: 6/144 (x86_64), 1/2 (arm) ID: 375428 Test: x86_64 Workstation-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/375428 ID: 375451 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/375451 ID: 375465 Test: x86_64 universal install_btrfs URL: https://openqa.fedoraproject.org/tests/375465 ID: 375467 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/375467 ID: 375502 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/375502 ID: 375513 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/375513 ID: 375518 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/375518 Soft failed openQA tests: 15/144 (x86_64), 4/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 375382 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/375382 ID: 375383 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/375383 ID: 375384 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/375384 ID: 375385 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/375385 ID: 375391 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/375391 ID: 375411 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/375411 ID: 375412 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/375412 ID: 375427 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/375427 ID: 375430 Test: x86_64 Workstation-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/375430 ID: 375431 Test: x86_64 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/375431 ID: 375435 Test: i386 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/375435 ID: 375488 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/375488 ID: 375497 Test: x86_64 universal install_anaconda_text URL: https://openqa.fedoraproject.org/tests/375497 ID: 375505 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/375505 ID: 375529 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/375529 ID: 375530 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/375530 ID: 375531 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/375531 ID: 375533 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/375533 ID: 375547 Test: i386 universal upgrade_desktop_32bit URL: https://openqa.fedoraproject.org/tests/375547 Passed openQA tests: 123/144 (x86_64), 20/24 (i386) Skipped non-gating openQA tests: 1 of 170 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Problem participating in the QA meetings
I have been lurking at the last few QA meetings, but I must still be missing something. I followed all the reference pages people were kind enough to send me. I have Hex Chat set up and I registered at the website. In fact when I re-did the registration command today, it said the tablepc is already registered. I can watch the conversations in the discussion panel. I can type something and it will appear in the discussion panel, but it seems like no one else can see what I said. Also my name doesn't appear on the list of attendees when the minutes come out. The only clue I have is that my user name appears in red. I suppose that might be to mark what I type. Any help will be appreciated. Have a Great Day! Pat (tablepc) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Testing F30 Workstation Beta RC 1.8 0303 RHBZ #1694782
In regard to my testing of F30 Workstation Beta RC 1.8 0330: I ran most of the standard test cases and all passed and were logged via relval. In my as deployed testing the issue I found a couple of drops ago still persists. This is the authorization pop up that can not be satisfied or dismissed. I have filled RHBZ #1694782 against Gnome Control Center. Have a Great Day! Pat (tablepc) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora 30 compose report: 20190401.n.0 changes
OLD: Fedora-30-20190330.n.3 NEW: Fedora-30-20190401.n.0 = SUMMARY = Added images:7 Dropped images: 2 Added packages: 17 Dropped packages:0 Upgraded packages: 128 Downgraded packages: 0 Size of added packages: 28.73 MiB Size of dropped packages:0 B Size of upgraded packages: 6.35 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 7.58 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Games live x86_64 Path: Labs/x86_64/iso/Fedora-Games-Live-x86_64-30-20190401.n.0.iso Image: Astronomy_KDE live i386 Path: Labs/i386/iso/Fedora-Astronomy_KDE-Live-i386-30-20190401.n.0.iso Image: Mate raw-xz armhfp Path: Spins/armhfp/images/Fedora-Mate-armhfp-30-20190401.n.0-sda.raw.xz Image: LXDE raw-xz armhfp Path: Spins/armhfp/images/Fedora-LXDE-armhfp-30-20190401.n.0-sda.raw.xz Image: SoaS raw-xz armhfp Path: Spins/armhfp/images/Fedora-SoaS-armhfp-30-20190401.n.0-sda.raw.xz Image: KDE raw-xz armhfp Path: Spins/armhfp/images/Fedora-KDE-armhfp-30-20190401.n.0-sda.raw.xz Image: Astronomy_KDE live x86_64 Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-30-20190401.n.0.iso = DROPPED IMAGES = Image: Xfce live x86_64 Path: Spins/x86_64/iso/Fedora-Xfce-Live-x86_64-30-20190330.n.3.iso Image: LXQt live x86_64 Path: Spins/x86_64/iso/Fedora-LXQt-Live-x86_64-30-20190330.n.3.iso = ADDED PACKAGES = Package: R-tidyr-0.8.3-1.fc30 Summary: Easily Tidy Data with 'spread()' and 'gather()' Functions RPMs:R-tidyr Size:2.47 MiB Package: golang-github-docopt-0.6.2-1.20190325gitee0de3b.fc30 Summary: A command-line arguments parser RPMs:golang-github-docopt-devel Size:28.98 KiB Package: golang-github-euank-kmsg-parser-2.0.1-1.fc30 Summary: A simpler parser for the /dev/kmsg format RPMs:godmesg golang-github-euank-kmsg-parser-devel Size:3.39 MiB Package: golang-github-krolaw-dhcp4-0-0.1.20190325git7cead47.fc30 Summary: DHCP4 library written in Go RPMs:golang-github-krolaw-dhcp4-devel Size:23.64 KiB Package: golang-github-opentracing-1.1.0-1.fc30 Summary: OpenTracing API for Go RPMs:golang-github-opentracing-devel Size:42.15 KiB Package: golang-github-soheilhy-cmux-0.1.4-1.fc30 Summary: Connection multiplexer for GoLang: serve different services on the same port RPMs:golang-github-soheilhy-cmux-devel Size:25.51 KiB Package: golang-uber-atomic-1.3.2-1.fc30 Summary: Wrapper types for sync/atomic which enforce atomic access RPMs:golang-uber-atomic-devel Size:13.65 KiB Package: golang-uber-multierr-1.1.0-1.fc30 Summary: Combine one or more Go errors together RPMs:golang-uber-multierr-devel Size:15.44 KiB Package: paperwork-1.2.4-2.fc30 Summary: Using scanner and OCR to grep dead trees the easy way RPMs:paperwork python3-paperwork Size:3.78 MiB Package: python-apprise-0.7.4-1.fc30 Summary: A simple wrapper to many popular notification services used today RPMs:apprise python3-apprise Size:612.57 KiB Package: python-capturer-2.4-5.fc30 Summary: Easily capture stdout/stderr of the current process and subprocesses RPMs:python-capturer-doc python3-capturer Size:213.00 KiB Package: python-coloredlogs-10.0-7.fc30 Summary: Colored terminal output for Python's logging module RPMs:python-coloredlogs-doc python3-coloredlogs Size:487.24 KiB Package: python-hdmf-1.0.1-1.fc30 Summary: A package for standardizing hierarchical object data RPMs:python-hdmf-doc python3-hdmf Size:12.04 MiB Package: python-humanfriendly-4.18-1.fc30 Summary: Human friendly output for text interfaces using Python RPMs:python-humanfriendly-doc python3-humanfriendly Size:566.66 KiB Package: python-paperwork-backend-1.2.4-1.fc30 Summary: Paperwork's backend RPMs:python3-paperwork-backend Size:132.12 KiB Package: python-py3nvml-0.2.3-2.fc30 Summary: Python 3 Bindings for the NVIDIA Management Library RPMs:python3-py3nvml python3-py3nvml-doc Size:4.75 MiB Package: python-verboselogs-1.7-4.fc30 Summary: Verbose logging level for Python's logging module RPMs:python-verboselogs-doc python3-verboselogs Size:178.71 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: ModemManager-1.10.0-1.fc30 Old package: ModemManager-1.10.0-0.3.rc1.fc30 Summary: Mobile broadband modem management service RPMs: ModemManager ModemManager-devel ModemManager-glib ModemManager-glib-devel ModemManager-vala Size: 10.10 MiB Size change: 13.71 KiB Changelog: * Wed Mar 27 2019 Richard Hughes 1.10.0-1 - Update to the release tarball. Package: R-gsl-2.1.6-1.fc30 Old package: R-gsl-2.1.5-1.fc30 Summary: Wrapper for the Gnu Scientific Library RPMs: R-gsl Size: 2.82 MiB Size change: -1.01 MiB Changelog: * Tue Mar 26 2019 Elliott Sales de Andrade - 2.1.6-1 - Update to latest version Package: R-littler-0.3.7-1.fc30 Old package: R-littler
Fedora rawhide compose report: 20190401.n.0 changes
OLD: Fedora-Rawhide-20190331.n.0 NEW: Fedora-Rawhide-20190401.n.0 = SUMMARY = Added images:5 Dropped images: 2 Added packages: 9 Dropped packages:0 Upgraded packages: 48 Downgraded packages: 1 Size of added packages: 14.84 MiB Size of dropped packages:0 B Size of upgraded packages: 1.48 GiB Size of downgraded packages: 18.79 MiB Size change of upgraded packages: 188.38 MiB Size change of downgraded packages: -2.42 KiB = ADDED IMAGES = Image: Python_Classroom vagrant-libvirt i386 Path: Labs/i386/images/Fedora-Python-Classroom-Vagrant-Rawhide-20190401.n.0.i386.vagrant-libvirt.box Image: Mate live i386 Path: Spins/i386/iso/Fedora-MATE_Compiz-Live-i386-Rawhide-20190401.n.0.iso Image: Container_Minimal_Base docker s390x Path: Container/s390x/images/Fedora-Container-Minimal-Base-Rawhide-20190401.n.0.s390x.tar.xz Image: Python_Classroom vagrant-virtualbox i386 Path: Labs/i386/images/Fedora-Python-Classroom-Vagrant-Rawhide-20190401.n.0.i386.vagrant-virtualbox.box Image: Container_Base docker s390x Path: Container/s390x/images/Fedora-Container-Base-Rawhide-20190401.n.0.s390x.tar.xz = DROPPED IMAGES = Image: Security live x86_64 Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-Rawhide-20190331.n.0.iso Image: Cinnamon live i386 Path: Spins/i386/iso/Fedora-Cinnamon-Live-i386-Rawhide-20190331.n.0.iso = ADDED PACKAGES = Package: ccls-0.20190314-1.fc31 Summary: C/C++/ObjC language server RPMs:ccls Size:3.15 MiB Package: ghc-base-compat-batteries-0.10.1-2.fc31 Summary: Base-compat with extra batteries RPMs:ghc-base-compat-batteries ghc-base-compat-batteries-devel Size:1.95 MiB Package: ghc-cabal-doctest-1.0.6-12.fc31 Summary: A Setup.hs helper for doctests running RPMs:ghc-cabal-doctest ghc-cabal-doctest-devel Size:1.22 MiB Package: ghc-haskell-src-meta-0.8.0.3-13.fc31 Summary: Parse source to template-haskell abstract syntax RPMs:ghc-haskell-src-meta ghc-haskell-src-meta-devel Size:2.80 MiB Package: ghc-th-expand-syns-0.4.4.0-13.fc31 Summary: Expands type synonyms in Template Haskell ASTs RPMs:ghc-th-expand-syns ghc-th-expand-syns-devel Size:1.12 MiB Package: ghc-th-lift-0.7.11-13.fc31 Summary: Derive Template Haskell's Lift class for datatypes RPMs:ghc-th-lift ghc-th-lift-devel Size:1.02 MiB Package: ghc-th-lift-instances-0.1.11-13.fc31 Summary: Lift instances for template-haskell for common data types RPMs:ghc-th-lift-instances ghc-th-lift-instances-devel Size:617.73 KiB Package: ghc-th-orphans-0.13.6-13.fc31 Summary: Orphan instances for TH datatypes RPMs:ghc-th-orphans ghc-th-orphans-devel Size:2.14 MiB Package: ghc-th-reify-many-0.1.8-13.fc31 Summary: Recurseively reify template haskell datatype info RPMs:ghc-th-reify-many ghc-th-reify-many-devel Size:858.27 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: Zim-0.70-1.fc31 Old package: Zim-0.70-0.2.rc1.fc30 Summary: Desktop wiki & notekeeper RPMs: Zim Size: 1.76 MiB Size change: -176 B Changelog: * Tue Feb 19 2019 Robin Lee - 0.70-0.3.rc3 - Update to 0.70-rc3 * Mon Apr 01 2019 Robin Lee - 0.70-1 - new release - Recommends appindicator to keep compatible with previous version - Enable tests Package: arm-trusted-firmware-2.1-1.fc31 Old package: arm-trusted-firmware-2.1-0.2.rc1.fc31 Summary: ARM Trusted Firmware RPMs: arm-trusted-firmware-armv8 Size: 125.75 KiB Size change: 496 B Changelog: * Sun Mar 31 2019 Peter Robinson 2.1-1 - New 2.1 GA release Package: bindfs-1.13.11-1.fc31 Old package: bindfs-1.13.10-2.fc30 Summary: Fuse filesystem to mirror a directory RPMs: bindfs Size: 270.73 KiB Size change: 1.26 KiB Changelog: * Sun Mar 31 2019 Filipe Rosset - 1.13.11-1 - update to new version 1.13.11 fixes rhbz #1694427 - ChangeLog https://bindfs.org/docs/ChangeLog.utf8.txt Package: byobu-5.127-3.fc31 Old package: byobu-5.127-2.fc30 Summary: Light-weight, configurable window manager built upon GNU screen RPMs: byobu Size: 145.57 KiB Size change: -324 B Changelog: * Wed Mar 27 2019 Miro Hron??ok - 5.127-3 - Switch to Python 3 (#1532565) Package: cacti-1.2.3-1.fc31 Old package: cacti-1.2.2-1.fc31 Summary: An rrd based graphing tool RPMs: cacti Size: 19.06 MiB Size change: 133.37 KiB Changelog: * Sun Mar 31 2019 Morten Stevens - 1.2.3-1 - Update to 1.2.3 Package: cacti-spine-1.2.3-1.fc31 Old package: cacti-spine-1.2.2-1.fc31 Summary: Threaded poller for Cacti written in C RPMs: cacti-spine Size: 439.86 KiB Size change: 1.59 KiB Changelog: * Sun Mar 31 2019 Morten Stevens - 1.2.3-1 - Update to 1.2.3 Package: conda-4.6.9-1.fc31 Old package: conda-4.6.5-1.fc30 Summary: Cross-platform, Python-agnostic binary package manager RPMs: conda python3-c
Fedora Rawhide-20190401.n.0 compose check report
Missing expected images: Atomichost raw-xz x86_64 Atomichost qcow2 x86_64 Compose FAILS proposed Rawhide gating check! 8 of 47 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could not be mapped to openQA tests: FAILED: compose.cloud.all Failed openQA tests: 28/144 (x86_64), 3/24 (i386), 1/2 (arm) ID: 375220 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller **GATING** URL: https://openqa.fedoraproject.org/tests/375220 ID: 375221 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart **GATING** URL: https://openqa.fedoraproject.org/tests/375221 ID: 375222 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/375222 ID: 375227 Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING** URL: https://openqa.fedoraproject.org/tests/375227 ID: 375228 Test: x86_64 Server-dvd-iso server_freeipa_replication_master URL: https://openqa.fedoraproject.org/tests/375228 ID: 375231 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/375231 ID: 375232 Test: x86_64 Server-dvd-iso server_freeipa_replication_client URL: https://openqa.fedoraproject.org/tests/375232 ID: 375240 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/375240 ID: 375254 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/375254 ID: 375258 Test: x86_64 Workstation-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/375258 ID: 375266 Test: x86_64 KDE-live-iso install_default_upload **GATING** URL: https://openqa.fedoraproject.org/tests/375266 ID: 375267 Test: x86_64 KDE-live-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/375267 ID: 375270 Test: x86_64 KDE-live-iso install_no_user **GATING** URL: https://openqa.fedoraproject.org/tests/375270 ID: 375280 Test: i386 KDE-live-iso install_default URL: https://openqa.fedoraproject.org/tests/375280 ID: 375281 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/375281 ID: 375283 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/375283 ID: 375284 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/375284 ID: 375285 Test: x86_64 Silverblue-dvd_ostree-iso install_no_user URL: https://openqa.fedoraproject.org/tests/375285 ID: 375297 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/375297 ID: 375318 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/375318 ID: 375332 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/375332 ID: 375336 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/375336 ID: 375337 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/375337 ID: 375338 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/375338 ID: 375348 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/375348 ID: 375351 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/375351 ID: 375357 Test: x86_64 universal install_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/375357 ID: 375361 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/375361 ID: 375362 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/375362 ID: 375363 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/375363 ID: 375378 Test: i386 universal upgrade_2_desktop_32bit URL: https://openqa.fedoraproject.org/tests/375378 ID: 375379 Test: i386 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/375379 Soft failed openQA tests: 11/144 (x86_64), 4/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 375212 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/375212 ID: 375213 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/375213 ID: 375214 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/375214 ID: 375215 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/375215 ID: 375241 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/375241 ID: 375242 Test: i386 Server-dvd-iso install_default URL: h
