On Thu, 2019-11-14 at 10:34 -0800, Kevin Fenzi wrote:
On Thu, Nov 14, 2019 at 08:13:52AM -0800, Adam Williamson wrote:
On Wed, 2019-11-13 at 14:32 -0800, Kevin Fenzi wrote:
autocloud*: f27, but should die when f29 goes eol (it's only used to test atomic-host).
No, it isn't. It also tests the regular cloud images:
Sigh. :(
https://apps.fedoraproject.org/autocloud/jobs/
the tests with family 'Base' are tests of non-Atomic images. The regular Cloud base images are still release-blocking until whenever we decide to switch over to CoreOS. At some point this testing was meant
Well, or decide to just make the Cloud base image not blocking.
to move to Taskotron, then there was some talking of moving it to Fedora CI, but I don't know if anyone has actually done any work on either of those things. AFAIK we have no other system currently for doing automated testing on the Cloud base images.
We could probably run the tests in openQA without too much trouble if desired (though I can't guarantee it as I haven't looked into it in any detail), but we should probably do *something* here.
yeah, keeping autocloud is really not an option. It's running on a eol OS.
We have no upstream developers anymore.
It takes up 2 large hardware boxes we can't use for anything else that are idle most of the time.
So, yes, we should come up with something here. ;(
welp, if no-one else has a plan, I can take a look at migrating the tests it runs into openQA maybe next week. (That might also mean we'd pay more attention to the results - the autocloud tests haven't passed on Rawhide for like two months, but I didn't know that until I looked this morning...)
I still don't know what automated testing CoreOS has in place either...that might be useful to know...