{"push_id":795017626,"size":1,"distinct_size":1,"ref":"refs/heads/FixPalTests","head":"285d5cd22d326c53f5d704b9eab53e35f9f9eeb5","before":"9d6bcc43f95657bf206e8ed6942ae2d818060b1a","commits":[{"sha":"285d5cd22d326c53f5d704b9eab53e35f9f9eeb5","author":{"email":"79c8506aa7c4f256d586135507aa979186135502@microsoft.com","name":"Koundinya Veluri"},"message":"Try a fix for some frequently failing PAL tests\n\nSome PAL tests are frequently failing in the CI. I noticed that the CI runs PAL tests specifying an output folder that is on a mounted share. The specified output folder is used as the working directory for all PAL tests. Perhaps it has something to do with that, but not sure yet.\n\nTrying a few changes to way in which PAL are run, to see if the issue goes away:\n- Use the default /tmp/PalTestOutput as the output directory\n- Run each test in its own folder. Many PAL tests don't clean up after themselves, and create/use the same file/directory names in the current directory.\n- Copy the output folder to the specified output folder at the end\n\nFix #1561","distinct":true,"url":"https://api.github.com/repos/kouvel/coreclr/commits/285d5cd22d326c53f5d704b9eab53e35f9f9eeb5"}]}