#731 cloud: remove s390x from image builds
Closed 3 years ago by mohanboddu. Opened 4 years ago by dustymabe.
dustymabe/pungi-fedora dusty-s390x  into  f30

file modified
+1 -1
@@ -220,7 +220,7 @@ 

                      'kickstart': 'fedora-cloud-base.ks',

                      'distro': 'Fedora-22',

                      'disk_size': 4,

-                     'arches': ['aarch64', 'ppc64le', 's390x', 'x86_64'],

+                     'arches': ['aarch64', 'ppc64le', 'x86_64'],

                      'repo': [

                          'https://kojipkgs.fedoraproject.org/compose/updates/f30-updates/compose/Everything/$arch/os/'

                          'https://kojipkgs.fedoraproject.org/compose/30/latest-Fedora-30/compose/Everything/$arch/os/' 

It consistently fails so let's remove it so we don't get notifications
all the time.

OK, hopefully we can enable that again after @kevin is back and he finishes the infra migration under KVM. Because it's still just the infra that doesn't cooperate sometimes, I can't see anything wrong with the distro.

Also can't we just make another config and job for s390x?

OK, hopefully we can enable that again after @kevin is back and he finishes the infra migration under KVM. Because it's still just the infra that doesn't cooperate sometimes, I can't see anything wrong with the distro.

+1 - I'm perfectly fine with re-enabling it, but continuously watching it fail gives me anxiety

Also can't we just make another config and job for s390x?

just so it can fail in the same way? i'd prefer to keep the config integrated like it is. It's no biggie to re-enable when we think we've fixed it.

From what I can see the s390x failures aren't consistent, they are spread across all releases, 1/2 fails, 1/2 succeeds. And not always it's s390x what makes the compose fail.

Let's wait for the new infra and see what change it will make.

@dustymabe Can you make it failable rather than removing it totally?

Making it failable will still try to compose it but if the s390x image fails, it wont fail the entire compose.

From what I can see the s390x failures aren't consistent, they are spread across all releases, 1/2 fails, 1/2 succeeds. And not always it's s390x what makes the compose fail.

well for the specific compose I'm disabling s390x for in this PR (f30 cloud) it fails pretty consistently.

Let's wait for the new infra and see what change it will make.

I'd rather add it back once the new infra is in place.

@mohanboddu:
@dustymabe Can you make it failable rather than removing it totally?
Making it failable will still try to compose it but if the s390x image fails, it wont fail the entire compose.

We'll still get a notification because it will be FINISHED_INCOMPLETE so that doesn't help.

I think this is moot now right, it's been compiling fine for a while, can we just close this?

Closing this PR as its not required anymore

Pull-Request has been closed by mohanboddu

3 years ago
Metadata