[Kernel-packages] [Bug 1851663] Re: Consistent autopkgtest failures on ppc64el/s390x
** No longer affects: makedumpfile (Ubuntu Disco) ** Also affects: makedumpfile (Ubuntu Groovy) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: Consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851663] Re: Consistent autopkgtest failures on ppc64el/s390x
** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-xenial ** Changed in: makedumpfile (Ubuntu Disco) Status: Confirmed => Won't Fix ** Changed in: makedumpfile (Ubuntu Disco) Importance: Medium => Undecided ** Changed in: makedumpfile (Ubuntu Disco) Assignee: Thadeu Lima de Souza Cascardo (cascardo) => (unassigned) ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: makedumpfile (Ubuntu Xenial) Status: New => Confirmed ** Changed in: makedumpfile (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: Consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Disco: Won't Fix Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851663] Re: Consistent autopkgtest failures on ppc64el/s390x
** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-bionic ** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: Consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Disco: Confirmed Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851663] Re: Consistent autopkgtest failures on ppc64el/s390x
** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-disco ** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: Consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Disco: Confirmed Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851663] Re: Consistent autopkgtest failures on ppc64el/s390x
Cascardo, assigned to you given our conversations and since you're the maintainer. Feel free to reassign (to me even) if you like, and change the tags and states accordingly. Thanks, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: Consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Disco: Confirmed Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
