@StanFromIreland do we still want to log this, though? Or perhaps have a mechanism for skipping checks / checking against different sets of files in certain envs?

Or perhaps have a mechanism for skipping checks / checking against different sets of files in certain envs?

As I noted in the issue, this will greatly complicate the test (and increase the maintenance burden, who knows what envs people use), for something that is not particularly important. As such, I think skipping is fine, logging them too, however, sounds good.

"Simple prints" will get lost in the noise of the output, and be false-positives in the OPs case.

I don't think

print(f"Warning: LIBRARY_FUZZER_PATHS might contain an invalid entry:{p!r}")

will do any good.
So I think this is fine to go. It was the previous behaviour, anyway. I just thought it is a low hanging fruit to crop when the else was removed in#145232 and we had spurious failures ...