refs #12836 - added Python tests showing inline suppressions not working with unusedFunction check and -j2

[firewave]

No description provided.

[firewave]

This was extracted from #5647.

[chrchr-github]

If this highlights a bug, shouldn't we add a TODO somewhere?

[firewave]

If this highlights a bug, shouldn't we add a TODO somewhere?

This is no single location to highlight this. It's a fundamental problem. The referenced PR partially fixes this but that is not mergable and still quite messy.

I am trying to establish a basic test coverage so I can start fixing this. There are also still potentially more bugs related to this.

[chrchr-github]

What I meant was, is it obvious that this is an undesirable test result? Elsewhere we have e.g. TODO_ASSERT. But I'm not familiar with those Python tests.

[firewave]

What I meant was, is it obvious that this is an undesirable test result? Elsewhere we have e.g. TODO_ASSERT. But I'm not familiar with those Python tests.

That is reflected by @pytest.mark.xfail(). That indicates that this test is expected to fail for now (reported as XFAIL). If the test should ever succeed that will be reported as XPASS. Since it set the strict option this will cause the Python test will fail with an error.