test_os windows failed test handling#4764
Conversation
…r all platforms`
youknowone
left a comment
There was a problem hiding this comment.
Other parts looks perfect. Thank you so much!
|
ah, removing test_os from platform independent tests allowed windows to run test_os, and it started failing |
But it shouldn't fail on windows, should it? |
|
Yes. In that case, skipping test is better than failing CI. |
|
I see the test failed, but it was run without |
Did you run |
|
here is copy of the failing messages. They look like all coming from the same reason. |
This is related to the |
|
@fanninpm do you have advices? |
|
Taking a look at what I did in #3807, you'd probably need to add (After, of course, running |
|
Just ran this command without any code changes |
Which command? It would be helpful to type it out in full. |
|
Command: |
|
I marked this PR as help-wanted. I think this PR need help from windows environment |
|
I've got a Windows partition taking up space on my hard drive, I'll hopefully get time at weekend to test out after a gazillion updates. |
|
It might be important to consider that GitHub's Windows runners are running Windows Server 2022, not Windows 10 or 11. |
|
I can try to run it in docker with 2022 image. |
|
that would be dope @derlih, if it fails we'll be pretty certain its the cause (and I'll also avoid doing updates on Windows yet again!) |
| test_importlib | ||
| test_io | ||
| test_iter | ||
| test_os |
There was a problem hiding this comment.
This is a big progress without regression. just failing on CI.
Because it is not easily fixed now, let's revert this like to skip test_os on windows, and merge it first.
And lets think about this fix later.
#3960 for test_os
In addition removed test_iter from platform dependant tests.