Skip to content
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

Closed
latkin opened this issue Jan 29, 2016 · 24 comments
Closed

Failing tests on master #915

latkin opened this issue Jan 29, 2016 · 24 comments
Labels
Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. Regression

Comments

@latkin
Copy link
Contributor

latkin commented Jan 29, 2016

I see the following failures on master:

fsc usage baseline files have not been updated with new response file flag

+++ CompilerOptions\fsc\help (NetFx40 -?) +++
PRECMD: [fsc >help40.txt -?     2>&1]
Microsoft (R) F# Compiler version (private)
Copyright (c) Microsoft Corporation. All Rights Reserved.
POSTCMD: [fsiAnyCPU --nologo --quiet --exec comparer.fsx help40.txt help40.437.1033.bsl]
Fail to execute the POSTCMD. FAIL
+++ CompilerOptions\fsc\help (NetFx40 --help) +++
PRECMD: [fsc >help40.txt --help 2>&1]
Microsoft (R) F# Compiler version (private)
Copyright (c) Microsoft Corporation. All Rights Reserved.
POSTCMD: [fsiAnyCPU --nologo --quiet --exec comparer.fsx help40.txt help40.437.1033.bsl]
Fail to execute the POSTCMD. FAIL
+++ CompilerOptions\fsc\help (NetFx40 /?) +++
PRECMD: [fsc >help40.txt /? 2>&1]
Microsoft (R) F# Compiler version (private)
Copyright (c) Microsoft Corporation. All Rights Reserved.
POSTCMD: [fsiAnyCPU --nologo --quiet --exec comparer.fsx help40.txt help40.437.1033.bsl]
Fail to execute the POSTCMD. FAIL

Various warning numbers don't match actual warning numbers.

+++ CompilerOptions\fsc\responsefile (E_responsefile_not_found.fs error if response file does not exists) +++
Microsoft (R) F# Compiler version (private)
Copyright (c) Microsoft Corporation. All Rights Reserved.
(0,0): error FS3194: Response file '@not_exists' not found in 'C:\src\latkinfsharp\tests\fsharpqa\Source\CompilerOptions\fsc\responsefile\not_exists'

*** The following necessary lines were never matched:
*** error FS3192:.+
+++ CompilerOptions\fsc\responsefile (E_responsefile_path_invalid.fs error if response file name is empty or invalid) +++
Microsoft (R) F# Compiler version (private)
Copyright (c) Microsoft Corporation. All Rights Reserved.
(0,0): error FS3195: Response file name '@' is empty, contains invalid characters, has a drive specification without an absolute path, or is too long

*** The following necessary lines were never matched:
*** error FS3193:.+
@enricosada
Copy link
Contributor

I'll fix test failures, thx @latkin

@dsyme
Copy link
Contributor

dsyme commented Feb 7, 2016

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.

fail001     CompilerOptions\fsc\help    #  (NetFx40 -?)
fail002     CompilerOptions\fsc\help    #  (NetFx40 --help)
fail003     CompilerOptions\fsc\help    #  (NetFx40 /?)
fail004     CompilerOptions\fsc\responsefile    #  (E_responsefile_not_found.fs error if response file does not exists)
fail005     CompilerOptions\fsc\responsefile    #  (E_responsefile_path_invalid.fs error if response file name is empty or invalid)
fail006     Conformance\DeclarationElements\CustomAttributes\AttributeUsage #  (X_AssemblyVersion01.fs)
fail007     Conformance\DeclarationElements\CustomAttributes\AttributeUsage #  (X_AssemblyVersion02.fs)
fail008     Conformance\DeclarationElements\MemberDefinitions\MethodsAndProperties  #  (E_DuplicateProperty01.fs)
fail009     Conformance\DeclarationElements\MemberDefinitions\MethodsAndProperties  #  (E_AbstractProperties03.fs)
fail010     Conformance\DeclarationElements\MemberDefinitions\MethodsAndProperties  #  (E_AbstractAndConcereteProp.fs)
fail011     Conformance\ObjectOrientedTypeDefinitions\ClassTypes\MemberDeclarations #  (E_PropertySetterUnit01.fs)
fail012     Conformance\ObjectOrientedTypeDefinitions\ClassTypes\MemberDeclarations #  (E_PropertyInvalidGetterSetter01.fs)
fail013     Conformance\ObjectOrientedTypeDefinitions\ClassTypes\MemberDeclarations #  (E_PropertySameNameDiffArity.fs)
fail014     TypeProviders\RuntimeDesignTimeAssembly\LoadingLogic    #  (NFYY)
fail015     TypeProviders\RuntimeDesignTimeAssembly\LoadingLogic    #  (NFYN)
fail016     Optimizations\GenericComparison #  (Compare07.fs - NetFx40)
fail017     Optimizations\GenericComparison #  (Compare10.fs - NetFx40)
fail018     Optimizations\GenericComparison #  (Equals06.fs - NetFx40)
fail019     Optimizations\GenericComparison #  (Equals09.fs - NetFx40)
fail020     Optimizations\GenericComparison #  (Hash09.fs - NetFx40)
fail021     Optimizations\GenericComparison #  (Hash12.fs - NetFx40)

@dsyme
Copy link
Contributor

dsyme commented Feb 7, 2016

After #937 the current failures will be like this:

fail014 TypeProviders\RuntimeDesignTimeAssembly\LoadingLogic # (NFYY)
fail015 TypeProviders\RuntimeDesignTimeAssembly\LoadingLogic # (NFYN)
fail016 Optimizations\GenericComparison # (Compare07.fs - NetFx40)
fail017 Optimizations\GenericComparison # (Compare10.fs - NetFx40)
fail018 Optimizations\GenericComparison # (Equals06.fs - NetFx40)
fail019 Optimizations\GenericComparison # (Equals09.fs - NetFx40)
fail020 Optimizations\GenericComparison # (Hash09.fs - NetFx40)
fail021 Optimizations\GenericComparison # (Hash12.fs - NetFx40)

@dsyme dsyme changed the title Response file tests fail Failing tests on master Feb 7, 2016
@dsyme dsyme added Regression Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. labels Feb 7, 2016
@manofstick
Copy link
Contributor

I commented on this in #944 (the gist being that we should probably restore the tail calls. Agree?)

@dsyme
Copy link
Contributor

dsyme commented Feb 7, 2016

These are the failing tests on my machine for the "FSHARP" suite:

Errors and Failures

1) Failed : FSharp-Tests-Core+Printing.printing("","z.output.test.default.txt","
z.output.test.default.bsl")
2) Failed : FSharp-Tests-Core+Printing.printing("--use:preludePrintSize1000.fsx"
,"z.output.test.1000.txt","z.output.test.1000.bsl")
3) Failed : FSharp-Tests-Core+Printing.printing("--use:preludePrintSize200.fsx",
"z.output.test.200.txt","z.output.test.200.bsl")
4) Failed : FSharp-Tests-Core+Printing.printing("--use:preludeShowDeclarationVal
uesFal...","z.output.test.off.txt","z.output.test.off.bsl")
5) Failed : FSharp-Tests-Typecheck+Sigs.sigs

@dsyme
Copy link
Contributor

dsyme commented Feb 8, 2016

All failing tests should now be fixed in #944

@dsyme
Copy link
Contributor

dsyme commented Feb 8, 2016

I'm still seeing failing tests when running tests using the VS tets runner from VisualFSharp.sln:

  • core\members\basics
  • core\load-script
  • negTests("neg1a")
  • negTests("neg1_a")
  • negTests("ProviderAttribute_EmptyConsume")
  • negTests("providerAttributeErrorConsume")
  • printing tests

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.

@dsyme
Copy link
Contributor

dsyme commented Feb 8, 2016

We're also seeing FSHARP suite failures on AppVeyor, however the AppVeyor build itself is not failing when that suite has errors....

[00:33:34] 1) Failed : FSharp-Tests-Core+Interop.interop
[00:33:34] 2) Failed : FSharp-Tests-Core+Printing.printing("--use:preludePrintSize200.fsx","z.output.test.200.txt","z.output.test.200.bsl")
[00:33:34] 3) Failed : FSharp-Tests-Core+Printing.printing("--use:preludeShowDeclarationValuesFal...","z.output.test.off.txt","z.output.test.off.bsl")
[00:33:34] 4) Failed : FSharp-Tests-Core+Verify.verify
[00:33:34] 5) Failed : FSharp-Tests-Typecheck+Sigs.sigs
[00:33:34] 6) Failed : FSharp-Tests-TypeProviders+Builtin+EdmxFile.EdmxFile(FSC_BASIC)
[00:33:34] 7) Failed : FSharp-Tests-TypeProviders+Builtin+EdmxFile.EdmxFile(FSC_O3)
[00:33:34] 8) Failed : FSharp-Tests-TypeProviders+Builtin+EdmxFile.EdmxFile(FSC_OPT_MINUS_DEBUG)
[00:33:34] 9) Failed : FSharp-Tests-TypeProviders+Builtin+EdmxFile.EdmxFile(FSC_OPT_PLUS_DEBUG)
[00:33:34] 10) Failed : FSharp-Tests-TypeProviders+Builtin+EdmxFile.EdmxFile(FRENCH)
[00:33:34] 11) Failed : FSharp-Tests-TypeProviders+Builtin+EdmxFile.EdmxFile(SPANISH)
[00:33:34] 12) Failed : FSharp-Tests-TypeProviders+Builtin+EdmxFile.EdmxFile(AS_DLL)
[00:33:34] 13) Failed : FSharp-Tests-TypeProviders+Builtin+SqlDataConnection.sqlDataConnection(FSC_BASIC)
[00:33:34] 14) Failed : FSharp-Tests-TypeProviders+Builtin+SqlDataConnection.sqlDataConnection(FSC_O3)
[00:33:34] 15) Failed : FSharp-Tests-TypeProviders+Builtin+SqlDataConnection.sqlDataConnection(FSC_OPT_MINUS_DEBUG)
[00:33:34] 16) Failed : FSharp-Tests-TypeProviders+Builtin+SqlDataConnection.sqlDataConnection(FSC_OPT_PLUS_DEBUG)
[00:33:34] 17) Failed : FSharp-Tests-TypeProviders+Builtin+SqlDataConnection.sqlDataConnection(FRENCH)
[00:33:34] 18) Failed : FSharp-Tests-TypeProviders+Builtin+SqlDataConnection.sqlDataConnection(SPANISH)
[00:33:34] 19) Failed : FSharp-Tests-TypeProviders+Builtin+SqlDataConnection.sqlDataConnection(AS_DLL)
[00:33:34] 20) Failed : FSharp-Tests-TypeProviders+Builtin+ODataService.oDataService(FSC_BASIC)
[00:33:34] 21) Failed : FSharp-Tests-TypeProviders+Builtin+ODataService.oDataService(FSC_O3)
[00:33:34] 22) Failed : FSharp-Tests-TypeProviders+Builtin+ODataService.oDataService(FSC_OPT_MINUS_DEBUG)
[00:33:34] 23) Failed : FSharp-Tests-TypeProviders+Builtin+ODataService.oDataService(FSC_OPT_PLUS_DEBUG)
[00:33:34] 24) Failed : FSharp-Tests-TypeProviders+Builtin+ODataService.oDataService(FRENCH)
[00:33:34] 25) Failed : FSharp-Tests-TypeProviders+Builtin+ODataService.oDataService(SPANISH)
[00:33:34] 26) Failed : FSharp-Tests-TypeProviders+Builtin+ODataService.oDataService(AS_DLL)
[00:33:34] 27) Failed : FSharp-Tests-TypeProviders+Builtin+WsdlService.wsdlService(FSC_BASIC)
[00:33:34] 28) Failed : FSharp-Tests-TypeProviders+Builtin+WsdlService.wsdlService(FSC_O3)
[00:33:34] ERRORLEVEL 1 ERRORLEVEL 1
[00:33:34] 29) Failed : FSharp-Tests-TypeProviders+Builtin+WsdlService.wsdlService(FSC_OPT_MINUS_DEBUG)
[00:33:34] 30) Failed : FSharp-Tests-TypeProviders+Builtin+WsdlService.wsdlService(FSC_OPT_PLUS_DEBUG)
[00:33:34] 31) Failed : FSharp-Tests-TypeProviders+Builtin+WsdlService.wsdlService(FRENCH)
[00:33:34] 32) Failed : FSharp-Tests-TypeProviders+Builtin+WsdlService.wsdlService(SPANISH)
[00:33:34] 33) Failed : FSharp-Tests-TypeProviders+Builtin+WsdlService.wsdlService(AS_DLL)

@enricosada
Copy link
Contributor

@dsyme some like core/member/basic are disabled in appveyor becuase of NO_CI in https://github.com/Microsoft/visualfsharp/blob/master/tests/test.lst

@enricosada
Copy link
Contributor

Ref #813 (comment)

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2016

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

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2016

Status of CI after merging #948

  • FSHARP and FSHARPQA are both enanbled
  • One remaining FSHARP suite failure. 1) Failed : FSharp-Tests-Typecheck+Sigs.sigs
  • Failures in FSHARP are still not triggering an overall failure of the build, nor uploading results correctly
  • The VisualFSharp.Unittests suite is not yet enabled
  • Overall appveyor build+test times are at around 55 minutes. (2x27min)
  • VisualFSharp.Unittests has these failures based on a "release" local run on my machine.
  1. Error : Tests.LanguageService.General.UsingMSBuild.PublicSurfaceArea.DotNetRe
    flection
  2. Error : Tests.LanguageService.General.UsingProjectSystem.PublicSurfaceArea.Do
    tNetReflection
  3. Error : Tests.ProjectSystem.Miscellaneous.Miscellaneous.CreateServices
  4. Error : Tests.ProjectSystem.References.PathReferences.Existing
  5. Error : Tests.ProjectSystem.References.ReferenceResolution.Bug650591.Automati
    onReference.Add.FullPath
  6. Failed : Tests.ProjectSystem.UpToDate.ItemInputs

@enricosada
Copy link
Contributor

Failures in FSHARP are still not triggering an overall failure of the build, nor uploading results correctly

i'll fix that now, pr wip in #949 (i'll make suite fail, and fix error)

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2016

@enricosada it's fixed in #950 , but good to double check with #949

@enricosada
Copy link
Contributor

@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 type testresults\fsharp_failures.log if fsharp_failures.log doesnt exists, there is no goto :failure. the fsharp nunit runner write FSharpNunit_Output.log

@enricosada
Copy link
Contributor

btw @dsyme amazing job fixing all failures, and the code cleanup in fsharp nunit 👍

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2016

ok, thanks

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2016

@enricosada I've fixed the fsharp_failures.log problem in #950

@enricosada
Copy link
Contributor

@dsyme ok, closed mine

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2016

@enricosada A couple of comments on the test runner code for the FSHARP quite

  • Awesome job on the 1:1 translation. It's made it feasible to track down these bugs. I can't believe how you persevered with that: it really is a huge contribution especially in the long term
  • Now that the translation is done and stable (apart from enabling it for CoreCLR) we should aim to simplify the code. For example I spent an hour staring at some "pipe to FSI sed.fsx script" code trying to work out what was going on, and in the end replaced it with a File.ReadAllLines+String.Replace+File.WriteAllLines in 3 minutes :) So we can likely look for similar places where we are needlessly shelling out or where we have inherited complexity we no longer need.
  • It would be good to split the "sigs" test into multiple individual tests.

@enricosada
Copy link
Contributor

btw @dsyme i think you can ask @KevinRansom to make you collaborator in appveyor, so you can cancel/stop useless builds.
I use stop build a lot in my personal appveyor

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2016

Thanks @enricosada , have asked

@dsyme
Copy link
Contributor

dsyme commented Feb 9, 2016

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)

capture

Am closing this!!!!

@dsyme dsyme closed this as completed Feb 9, 2016
@forki
Copy link
Contributor

forki commented Feb 9, 2016

Kudos!

yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. Regression
Projects
None yet
Development

No branches or pull requests

5 participants