Uh oh!
There was an error while loading. Please reload this page.
Improve the reliability of the tests - #2620
Conversation
Tests Passed: Trying again: @dotnet-bot test this please |
KevinRansom
commented
Mar 16, 2017
Tests Passed(Except Ubuntu): Trying again: @dotnet-bot test this please |
KevinRansom
commented
Mar 16, 2017
Tests Passed: Trying again: @dotnet-bot test this please |
1 similar comment
KevinRansom
commented
Mar 16, 2017
Tests Passed: Trying again: @dotnet-bot test this please |
KevinRansom
commented
Mar 16, 2017
Flakey test failed, different test case but same code.
|
KevinRansom
commented
Mar 17, 2017
Tests Passed: With extra logging, trying again: @dotnet-bot test this please |
2 similar comments
KevinRansom
commented
Mar 17, 2017
Tests Passed: With extra logging, trying again: @dotnet-bot test this please |
KevinRansom
commented
Mar 17, 2017
Tests Passed: With extra logging, trying again: @dotnet-bot test this please |
| log "rm %s" path | ||
| let p = path |> getfullpath dir | ||
| if File.Exists(p) then File.Delete(p) | ||
| if File.Exists(p) then (log "rm %s" p) |> ignore; File.Delete(p); else (log "not found: %s p") |> ignore |
There was a problem hiding this comment.
Haven't checked the code in VS, but are the ignore required?
let's just put this on separate lines instead of ;.
I like the use of IDisposable to make it work in a scope.
There was a problem hiding this comment.
sure ... when I am convinced it is actually .... reliable :-)
KevinRansom
commented
Mar 17, 2017
Tests Passed: With extra logging, trying again: @dotnet-bot test this please |
KevinRansom
commented
Mar 17, 2017
Tests Passed (apart from Ubuntu): With extra logging, trying again: @dotnet-bot test this please |
KevinRansom
commented
Mar 18, 2017
Tests Passed (apart from FSHARPQA?): With extra logging, trying again: @dotnet-bot test this please |
* Improve the reliability of the tests * Add extra logging * Address cr
The test failure occurs when calling peverify on the built assembly. The usual readon for that is a missing or incorrect version of fsharp.core.dll. An incorrect version of fharp.core.dll can occur because of one left hanging about in the directory at test build time.
This change ensures that we :
Kevin