Can you identify if this is intended to be a temporary fix, or a normal fix?
If it's just temporary, to test out if disabling the test is ok, then +1 to land it. However, if this is intended to be a semi-permanent fix to the problem, a couple suggestions: * Explain in whatever detail is available, what you think is causing the test failure. So when someone restores the test some day, they'll have some idea on what to check. * A link to a debian or upstream discussion/ticket about the issue would be a nice-to-have -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866881 Title: Autopkgtest regression triggered by Ruby 2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puma/+bug/1866881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
