Hey all,

If you see a failure in CI that looks like the one in: filenamehttps://dev.azure.com/u-boot/u-boot/_build/results?buildId=7436&view=log... Which is: "FAT: illegal filename (.)" being printed instead of "Unable to write", just hit the re-run job until it passes. I guess Azure changed something under the hood that's causing something to go wrong somewhere else as it's neither consistently failing nor is the test itself failing (we continue to not write an illegal file).