programmatically_include_default_files test fails on Windows due to Unix-style file paths

[Velfi]

trafficstars

Describe the bug

The programmatically_include_default_files test fails on Windows due to Unix-style file paths.

It's located in aws-config but is being moved to the aws-runtime crate soon.

Expected Behavior

test passes

Current Behavior

test fails

Reproduction Steps

on Windows,

• cd into the aws-config crate
• run cargo test --all-features programmatically_include_default_files
• The test will fail

(If it doesn't run the test, remove any #[ignore] and try again.)

Possible Solution

No response

Additional Information/Context

No response

Version

HEAD

Environment details (OS name and version, etc.)

Windows 11

Logs

No response

[Velfi]

I don't understand how this ever passed in the first place. Are we not running aws-config tests on Windows?