Please, don't do pytest || : construct. Rather file a stupid upstream ticket like “test foo fails” and then add it to -k not (foo or bar) construct (with reference to the bug report in the comment), but don't eliminate results of tests altogether. Then at least other tests will provide some protection against regressions, and upstream might help with investigating the problems.

Sorry, what I meant to write is:

Please, don't do pytest || : construct. Rather file a stupid upstream ticket like “test foo fails” and then add it to -k not (foo or bar) construct (with reference to the bug report in the comment), but don't eliminate results of tests altogether. Then at least other tests will provide some protection against regressions, and upstream might help with investigating the problems.

I didn't change that pytest command, but I'll try to fix investigate the test fails.