@churchyard Well, this depends on if we have that hardware around for testing in Fedora. Do we?

Is testing internally in RH and uploading the results out of the question? We have resources there ....

Is testing internally in RH and uploading the results out of the question?

This time it is. We need this to be usable by anyone, not just Red Hat employees, in order to remove the part from %check.

I wonder how the CI is one of the things that everybody in Fedora is talking about (well, after modularity) and the are no resources in this. What can I do to help with this problem? As a Fedora contributor? As a Red Hat employee?

cc @dperpeet @bookwar do we have some ideas here?

This time it is. We need this to be usable by anyone, not just Red Hat employees, in order to remove the part form %check.

Testing internally and providing the results upstream != it's unusable for community, but I agree it would get hard once people would like to debug on such a machine ...

I am putting here low priority, as we have more serious issues on Fedora CI to fix first. We will get back to this later.

@mvadkert Can you provide an update here?

Do we have estimations for the timeline for multiarch support via TFT backend?

@bookwar afaict we are able to support ARM only as other artchitecture, do we have some other HW we could use in Fedora?

We plan to add support for functional tests next month, I believe we can enable testing on arm in the same time.

By arm do you mean aarch64 or armhfp or both?

@pbrobinson hmm, no idea about specifics .. this is their ARM product page ... https://aws.amazon.com/ec2/graviton/

I would think it is aarch64, I will try to provision an instance ...

So graviton is aarch64 but can run both. Although for armhfp it's likely easier to do it in a container, there's issues with the Fedora armhfp containers ATM but I'm hoping to have them fixed in the next few weeks.

@pbrobinson ah right, armhfp is 32bit :)

# uname -a
Linux ip-172-31-22-249.us-east-2.compute.internal 5.6.6-300.fc32.aarch64 #1 SMP Tue Apr 21 13:25:53 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
# cat /proc/cpuinfo 
processor   : 0
BogoMIPS    : 166.66
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

So 64bit works, not sure if we can also run 32bit arm, checking ...

@pbrobinson there are no armhfp images on AWS, so I cannot even test. Do you think it should work on their 64b arm processors? I can try to upload an armhfp image then ...

@pbrobinson sorry missed your comments ;)

So graviton is aarch64 but can run both. Although for armhfp it's likely easier to do it in a container, there's issues with the Fedora armhfp containers ATM but I'm hoping to have them fixed in the next few weeks.

I see, for consistency, of we want to also test 32bit arm, it would be better to have armhfp fedora images uploaded to AWS, testing via containers is not very suitable when testing the OS itself.