fix(pwt): compatibility in CWD with wrong casing#16636
Conversation
51fbb9f to
bb062f7
Compare
bb062f7 to
ee6d28f
Compare
| retries: 0, | ||
| reporter: process.env.CI ? [ | ||
| ['dot'], | ||
| ['list'], |
There was a problem hiding this comment.
we only have a small number of long running tests, so list is better there.
ee6d28f to
77884e2
Compare
1fe567f to
c080a45
Compare
|
I'm still fuzzy on what it going on here. |
|
Abstract problem:
this ends up that the state inside is different, since these are different instances.
e.g. to it, so 1): setCurrentlyLoadingFileSuite 2): currentlyLoadingFileSuite |
…ith wrong casing (microsoft#16636)"
Fixes #16347
Fixes #9193
This bug only affects PowerShell 5.X and 6.X experience, when using PowerShell 7.X its not possible anymore to enter a directory with incorrect casing. PowerShell/PowerShell#9250 was fixing it upstream - this patch workarounds it and normalizes paths before requiring them.