[Tests] no-restricted-paths: skip failing tests on windows

[AdriAt360]

following #2466 (comment)

Context

One test is failing on windows, and multiple attempts to fix it have failed, without understanding why it's still failing

Changes

Skip this test, waiting for a bright idea

[AdriAt360]

awesome, the test is broken here too, I can close

[ljharb]

Please don’t open throwaway PRs like this tho; a PR ref is a permanent mark on a repo that can’t ever be removed.

[AdriAt360]

@ljharb got it 👍🏽
what's the preferred way of investigations needing to run the pipelines with unrelated changes to an existing PR?

[ljharb]

Ask me to push a branch, or set up appveyor on your own fork.

[AdriAt360]

@ljharb it seems I can't reopen here after force pushing a new commit, are you able to with your admin rights by any chance?

[AdriAt360]

@ljharb note that I commented out the test on #2466 anyways, so we can just merge the other PR if it's ok for you, as it would be simpler
your call

[ljharb]

No, if the branch was deleted the PR can never be reopened - it would have had to be reopened first.

Commenting out the test isn’t the proper way to skip it, and we have to land that skipping separately, before #2466.

[AdriAt360]

@ljharb in practice, there was no existing failing test, it was only uncovered code

• here I only added a failing test to double-check that the existing code was also faulty
• so even without changing this code, there is no CI issue currently

Commenting out the test isn’t the proper way to skip it

what would be the correct way? I couldn't find any clue in the code
by the way, feel free to answer on #2466 directly as I commented out a test there to skip it