Comment 2 for bug 1866881

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