Unit test failures when running the build locally

[Numpsy]

Hi

I'm not sure if this is down to my environment or is an actual issue (I'm running on Windows and I see the CI is running on Ubuntu), but when I run the build script locally I get this unit test failure:

I got this when trying to do a local build for #277 and it prevented the later tests from running, making it harder to test.

Any ideas?

Thanks

[sergey-tihon]

I wanna believe that Copilot fixed it correctly #281

[Numpsy]

Thanks, I'll give it another try at the weekend.

On a related note, just to check - the test in question is looking for a schema file in __SOURCE_DIRECTORY__ + "/../Schemas/v2/petstore.json" but it doesn't look like that file actually exists - the petstore.json file looks to actually be under /../SwaggerProvider.ProviderTests/Schemas/v2/petstore.json - is that intentional?
The test seems to be trying to ignore 'file not found' type errors, but it didn't seem to be hitting that code path

[Numpsy]

I'm still seeing an issue locally on Windows, but wonder if there could be a behavioural difference between Windows/Linux when the schema file is missing?
When I debug it, it gets to

SwaggerProvider/src/SwaggerProvider.DesignTime/Utils.fs

Line 202 in ed3414f

let isLocalFile = not checkUri.IsAbsoluteUri

and IsAbsoluteUri is true, and then it hits the error case at

SwaggerProvider/src/SwaggerProvider.DesignTime/Utils.fs

Line 319 in ed3414f

failwithf

I haven't been able to debug it on Linux yet, but maybe the path there (/home/... etc) would be considered a not-absolute URI and fail with

SwaggerProvider/src/SwaggerProvider.DesignTime/Utils.fs

Line 206 in ed3414f

return failwithf "Schema file not found: %s" resolvedPath

instead?