-
Notifications
You must be signed in to change notification settings - Fork 793
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing tests on master #915
Comments
I'll fix test failures, thx @latkin |
Here's the full list of failures in "fsharpqa" based on a run last night on my machine. I'm concerned about the failures in GenericComparison in particular though regardless we have to get back to the point where we are running clean, and stay there.
|
After #937 the current failures will be like this: fail014 TypeProviders\RuntimeDesignTimeAssembly\LoadingLogic # (NFYY) |
I commented on this in #944 (the gist being that we should probably restore the tail calls. Agree?) |
These are the failing tests on my machine for the "FSHARP" suite:
|
All failing tests should now be fixed in #944 |
I'm still seeing failing tests when running tests using the VS tets runner from VisualFSharp.sln:
I'm not sure why/if these appear to be passing outside VS. Some of the issues seem to do with timing of output. Will look into it and keep this thread open. |
We're also seeing FSHARP suite failures on AppVeyor, however the AppVeyor build itself is not failing when that suite has errors....
|
@dsyme some like core/member/basic are disabled in appveyor becuase of |
Ref #813 (comment) |
I think https://github.com/Microsoft/visualfsharp/pulls/948 should address all test failures. We're getting close to having all tests passing. core\printing will still fail on non-US culture |
Status of CI after merging #948
|
i'll fix that now, pr wip in #949 (i'll make suite fail, and fix error) |
@enricosada it's fixed in #950 , but good to double check with #949 |
@dsyme i think the problem is another, i'll try to fix it with my pr call RunTests.cmd %BUILD_CONFIG_LOWER% fsharp %TEST_TAGS%
@if ERRORLEVEL 1 type testresults\fsharp_failures.log && echo Error: 'RunTests.cmd %BUILD_CONFIG_LOWER% fsharp %TEST_TAGS%' failed && goto :failure with |
btw @dsyme amazing job fixing all failures, and the code cleanup in fsharp nunit 👍 |
ok, thanks |
@enricosada I've fixed the |
@dsyme ok, closed mine |
@enricosada A couple of comments on the test runner code for the FSHARP quite
|
btw @dsyme i think you can ask @KevinRansom to make you collaborator in appveyor, so you can cancel/stop useless builds. |
Thanks @enricosada , have asked |
We have a GREEN on master https://ci.appveyor.com/project/KevinRansom/visualfsharp-radou/build/0.0.1.1511 that includes running all FSHARP and FSHARPQA tests (apart from the relatively few "Expensive" ones) Am closing this!!!! |
I see the following failures on master:
fsc usage baseline files have not been updated with new response file flag
Various warning numbers don't match actual warning numbers.
The text was updated successfully, but these errors were encountered: