#9041 Need: Fedora 32 aarch64 vm for testing
Closed: Fixed 3 years ago by nb. Opened 3 years ago by spot.

Chromium is throwing an internal compiler error, but only on Fedora 32 aarch64. To be able to file the bug, I need to reproduce this in a VM and send the preprocessed source output to the gcc maintainers.

There is not currently a F32 aarch64 test machine listed here: https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers

It would be very helpful if one could be spun up. There is no ETA, however, I need to get this bug fixed in either chromium or Fedora 32's gcc before I can push this chromium security update.


We will not have a test system in Fedora land until July due to the move. Would a VM spun up in AWS cover this and what are the memory/cpu etc needed?

@mobrien can you do this one? or I can...

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: aws, groomed, low-trouble, medium-gain

3 years ago

A VM in AWS would be sufficient. 40GB ram 140GB disk would be nice, but since I'm not trying to do a full chromium build here, I could make due with less RAM.

Metadata Update from @nb:
- Issue assigned to nb

3 years ago

VM created. 62GB ram, 150GB disk. 16 CPUs.

ssh fedora@54.221.162.9
I have your fedora SSH key in authorized_keys

I didn't add it to DNS since it's a temporary thing.

Please let me know when you are done so I can remove the instance.

Actually, please hold. What cloud.fedoraproject.org said was a F32 AMI was F31. I found the correct AMI and am building an instance as F32 for you. Will have the new IP shortly.

Use fedora@54.175.145.248

It's a Fedora 32 instance with 64GB ram, 150GB disk, 16 CPUs.

Please let me know when you are done so I can remove the instance.

Jakub has a patch for gcc that should resolve the issue, but I'd like to confirm it works before removing the instance.

I'm done with it for now, you can remove it. Thank you.

I've terminated it. Please let us know if you need one again in the future.

Metadata Update from @nb:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata