{"push_id":795432184,"size":1,"distinct_size":1,"ref":"refs/heads/FixPalTests","head":"f58399b744ba4c104789c8b25d470eeaefa95219","before":"be3a949cbd1e3032fc703f08ab159731768065c7","commits":[{"sha":"f58399b744ba4c104789c8b25d470eeaefa95219","author":{"email":"79c8506aa7c4f256d586135507aa979186135502@microsoft.com","name":"Koundinya Veluri"},"message":"Fix some frequently failing PAL tests\n\nSome PAL tests are frequently failing in the CI. The specified output folder is currently used as the working folder for all PAL tests. The CI machine happened to have the output folder on a mount mounted as fuseblk instead of ext4. We don't know why this is happening. For the moment, I'm fixing the test runner to work around this issue.\n\nChanges:\n- Use /tmp/PalTestOutput/0 as the output folder by default\n- If a specific folder is specified for the output, use a unique folder starting with /tmp/PalTestOutput/1 for output files, and copy them to the specified folder at the end. A unique folder is used to support parallel runs on the same machine in this mode.\n- Run each test in its own folder. Many PAL tests don't clean up after themselves, and create/use the same file/folder names in the current folder.\n- Add a few more checks to some tests to hopefully provide more information upon the next failure\n- Fix GetFileAttributes tests, which were crashing upon some failures due to mismatched number of placeholders and arguments to vprintf\n\nFixes #1561","distinct":true,"url":"https://api.github.com/repos/kouvel/coreclr/commits/f58399b744ba4c104789c8b25d470eeaefa95219"}]}