I am newbie to TFS and got legacy project. Application is ASP.NET Core MVC, it uses .NET Core 6.0.
I wanted to run unit test in TFS. This is settings that I've found recently:
But tests are not run. It says:
2023-02-10T08:11:39.2659415Z ##[section]Starting: VsTest - testAssemblies
2023-02-10T08:11:39.2733935Z ==============================================================================
2023-02-10T08:11:39.2757377Z Task : Visual Studio Test
2023-02-10T08:11:39.2779733Z Description : Run unit and functional tests (Selenium, Appium, Coded UI test, etc.) using the Visual Studio Test runner. Test frameworks that have a Visual Studio test adapter such as xUnit, NUnit, Chutzpah, etc. can also be run. Tests can be distributed on multiple agents using this task (version 2).
2023-02-10T08:11:39.2798473Z Version : 2.3.28
2023-02-10T08:11:39.2804727Z Author : Microsoft Corporation
2023-02-10T08:11:39.2815189Z Help : [More Information](https://go.microsoft.com/fwlink/?LinkId=835764)
2023-02-10T08:11:39.2846404Z ==============================================================================
2023-02-10T08:11:40.1471485Z Run the tests locally using vstest.console.exe
2023-02-10T08:11:40.1487886Z ========================================================
2023-02-10T08:11:40.1509812Z Test selector : Test assemblies
2023-02-10T08:11:40.1524013Z Test assemblies : **\*test*.dll,!**\*Foo.Bar.TestLibrary.dll,!**\*testhost.dll,!**\*TestAdapter.dll,!**\obj\**
2023-02-10T08:11:40.1538632Z Test filter criteria : null
2023-02-10T08:11:40.1549192Z Search folder : D:\TfsAgents\dotNetDefault\_work\2\s
2023-02-10T08:11:40.1557662Z Run settings file : D:\TfsAgents\dotNetDefault\_work\2\s
2023-02-10T08:11:40.1565805Z Run in parallel : true
2023-02-10T08:11:40.1570553Z Run in isolation : false
2023-02-10T08:11:40.1592991Z Path to custom adapters : null
2023-02-10T08:11:40.1598283Z Other console options : null
2023-02-10T08:11:40.1603518Z Code coverage enabled : true
2023-02-10T08:11:40.1612353Z Rerun failed tests: false
2023-02-10T08:11:40.1619914Z VisualStudio version selected for test execution : latest
2023-02-10T08:11:40.5178061Z ========================================================
2023-02-10T08:12:33.9180802Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9191874Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9204400Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9214640Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9224315Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9238856Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9250308Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9259790Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9275781Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9296315Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9317966Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9337844Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9358059Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9373710Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9383130Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9392781Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9402054Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9411443Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9420659Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9431366Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9442896Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9454959Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9468304Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9478978Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9490804Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9502277Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9514008Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9526112Z (node:19236) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-02-10T08:12:33.9555091Z ##[warning]No test assemblies found matching the pattern: **\*test*.dll,!**\*Foo.Bar.TestLibrary.dll,!**\*testhost.dll,!**\*TestAdapter.dll,!**\obj\**.
2023-02-10T08:12:33.9926468Z ##[section]Finishing: VsTest - testAssemblies
Or shorter version is:
No test assemblies found matching the pattern:
**\*test*.dll,!**\*Foo.Bar.TestLibrary.dll,
!**\*testhost.dll,!**\*TestAdapter.dll,!**\obj\**
I've read this topic and added an extra wildcard:
**\*\*test*.dll
!**\*\*Foo.Bar.TestLibrary.dll
Even I've added two extra spaces. However, the error message is still the same.
**\*\*\*test*.dll
!**\*\*\*Foo.Bar.TestLibrary.dll
This is version of TFS:
Microsoft Visual Studio Team Foundation Server
Version 16.131.28601.4
© Microsoft Corporation. All rights reserved.
Related
So i started writing xunit test in net 6.0 with visual studio 2022 community preview.
Everything was working fine on the first PC.
But then when i set the dev environment on another PC (both windows 10) and i try running tests i get this :
========== Starting test run ==========
Testhost process exited with error: . Please check the diagnostic logs for more information.
Testhost process exited with error: . Please check the diagnostic logs for more information.
========== Test run aborted: 0 Tests (0 Passed, 0 Failed, 0 Skipped) run in < 1 ms ==========
With no more information. Where can i find those "diagnostic logs" i don't find info about it on the web.
I tried running tests manually in command terminal with "dotnet test" but i get this :
**dotnet test
Determining projects to restore...
All projects are up-to-date for restore.
kis-project-information-core -> D:\Users\Thomas MEDARD\Documents\Apollo\Kis\Booth\Libraries\kis-project-information\sources\binaries\net6.0\kis-project-information-core.dll
kis-project-information-unit-tests -> D:\Users\Thomas MEDARD\Documents\Apollo\Kis\Booth\Libraries\kis-project-information\sources\binaries\net6.0\kis-project-information-unit-tests.dll
Test run for D:\Users\Thomas MEDARD\Documents\Apollo\Kis\Booth\Libraries\kis-project-information\sources\binaries\net6.0\kis-project-information-unit-tests.dll (.NETCoreApp,Version=v6.0)
Microsoft (R) Test Execution Command Line Tool Version 17.0.0
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
Testhost process exited with error: . Please check the diagnostic logs for more information.
Test Run Aborted.**
I ran dotnet test -verbosity:diagnostic --diag:log.txt to see details and here is what i get
log.txt
log.host.21-11-30_10-19-44_26197_5.txt
So i see my test is detected but something is going wrong when running it
Ok so i found what is happening.
After reinstalling i thought everything worked but actually i found the same problem again.
What i realized is that i was in admin mode on my terminal. When i run the same command from non admin terminal, i get the problem explained.
So my problem is accessing to dotnet. I guess it has something to do with having my source code stored in a different drive from dotnet.
It's still weird that i can build without problem but testing need elevated privileges.
I have been deploying my C# MVC application for years now, as early as yesterday, successfully. Today however I started getting this error:
Step 6/6 : RUN npm install firebase-admin
---> Running in 6af72a3f9eaf
[91m/bin/sh: 1: npm: not found
The command '/bin/sh -c npm install firebase-admin' returned a non-zero code: 127
ERROR
ERROR: build step 0 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 127
[0m
--------------------------------------------------------------------------------
ERROR: (gcloud.app.deploy) Cloud build failed. Check logs at https://console.cloud.google.com/cloud-build/builds/ea90f766-e252-4b9b-b707-746acf8ad686?project=186443889098 Failure status: UNKNOWN: Error Response: [2] Build failed; check build logs for details
Failed to deploy project [Project Name] to App Engine Flex.
The logs say this:
Step 6/6 : RUN npm install firebase-admin
---> Running in 6af72a3f9eaf
/bin/sh: 1: npm: not found
The command '/bin/sh -c npm install firebase-admin' returned a non-zero code: 127
ERROR
ERROR: build step 0 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 127
Has anyone seen this error or know whats casing it?
The problem was the node.js version was wrong. It was trying to use the wrong node version when publishing vs what was defined in the code.
trying to get the sonar scanner running from the command line at the moment with just msbuild.exe solution.sln /rebuild it's currently failing on the post-processing step and i can't seem to get beyond that
my java path is set in: C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe. I tried updating my path to a location that didn't have any spaces in it but no luck.
I also tried using dotnet sonar scanner and msbuild sonar scanner. both with the same result
These are the steps i'm executing:
dotnet-sonarscanner begin /k:"key" /d:sonar.host.url="https://my_company_sonarqube.com" /d:sonar.login="token" /d:sonar.verbose=true
MSBuild.exe solution.sln /t:Rebuild /p:Platform="Any CPU"
dotnet-sonarscanner end /d:sonar.login="token"
Everything seems to work fine until i get to the post-processing step:
Executing file C:\Users\userid\.dotnet\tools\.store\dotnet-sonarscanner\4.7.1\dotnet-sonarscanner\4.7.1\tools\netcoreapp2.1\any\sonar-scanner-4.1.0.1829\bin\sonar-scanner.bat
Args: -Dsonar.scanAllFiles=true -Dproject.settings=C:\Users\userid\Documents\project_path\.sonarqube\out\sonar-project.properties --embedded --debug <sensitive data removed>
Working directory: C:\Users\userid\Documents\project_path
Timeout (ms):-1
Process id: 38116
Error: Could not find or load main class
Process returned exit code 1
The SonarQube Scanner did not complete successfully
19:53:44.155 Post-processing failed. Exit code: 1
Using the following JDK
java -version
java version "1.8.0_221"
Java(TM) SE Runtime Environment (build 1.8.0_221-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.221-b11, mixed mode)
ok so i'm not sure why i was getting the main class error. I re-ran everything using the sonarscanner batch script and then with a stripped down java call from the batch script and it seems like my problem was not having my ssl certificates for the sonarqube server.
Starting over and setting SONAR_SCANNER_OPTS seemed to do the trick.
set SONAR_SCANNER_OPTS = "-Djavax.net.ssl.trustStore="C:\path\to\trustStore"
For all .NET Framework and .NET Core projects in our TFS server 2018 the sonar scan does not finish scan after updatet to version 3.1.0.
We have the following build configuration in TFS server 2018, for a .NET Framework project:
Build configuration
The build breaks on the complete analyse step with the following error:
2018-01-16T09:28:19.5905262Z ##[error]No analysable projects were
found. SonarQube analysis will not be performed. Check the build
summary report for details. 2018-01-16T09:28:19.5905262Z Generation of
the sonar-properties file failed. Unable to complete SonarQube
analysis. 2018-01-16T09:28:19.5905262Z 10:28:19.543 Creating a
summary markdown file... 2018-01-16T09:28:19.5905262Z
[error]10:28:19.543 Post-processing failed. Exit code: 1 2018-01-16T09:28:19.5905262Z ##[error]System.Exception: Unexpected
exit code received from batch file: 1 2018-01-16T09:28:19.5905262Z
[debug]Processed: ##vso[task.logissue type=error;]System.Exception: Unexpected exit code received from batch file: 1
2018-01-16T09:28:19.5905262Z at
Microsoft.TeamFoundation.DistributedTask.Task.Internal.InvokeBatchScriptCmdlet.ProcessRecord()
2018-01-16T09:28:19.5905262Z at
System.Management.Automation.CommandProcessor.ProcessRecord()
2018-01-16T09:28:19.5905262Z ##[debug]The build was not triggered by a
Pull Request, not processing code analysis comments
2018-01-16T09:28:19.5905262Z ##[debug]Invoke - Get-TaskVariable cmdlet
2018-01-16T09:28:19.5905262Z ##[debug]Variable read:
MSBuild.SonarQube.Internal.IncludeFullReport = true
2018-01-16T09:28:19.6061603Z ##[debug]Invoke - Get-TaskVariable cmdlet
2018-01-16T09:28:19.6061603Z ##[debug]Variable read:
MSBuild.SonarQube.Internal.ServerVersion =
2018-01-16T09:28:19.6217771Z ##[debug]Calling InvokeGetRestMethod
"/api/server/version" 2018-01-16T09:28:19.6374047Z ##[debug]Invoke -
Get-TaskVariable cmdlet 2018-01-16T09:28:19.6374047Z ##[debug]Variable
read: MSBuild.SonarQube.HostUrl = https://sonar.MyOrganisation.nl/
2018-01-16T09:28:19.6530505Z ##[debug]Invoke - Get-TaskVariable cmdlet
2018-01-16T09:28:19.6530505Z ##[debug]Variable read:
MSBuild.SonarQube.ServerUsername = ********
2018-01-16T09:28:19.6530505Z ##[debug]Invoke - Get-TaskVariable cmdlet
2018-01-16T09:28:19.6530505Z ##[debug]Variable read:
MSBuild.SonarQube.ServerPassword = 2018-01-16T09:28:19.6842912Z
[debug]GET https://sonar.MyOrganisation.nl/api/server/version with 0-byte payload 2018-01-16T09:28:19.7155095Z ##[debug]received 11-byte
response of content type text/plain; charset=UTF-8
2018-01-16T09:28:19.7323972Z ##[debug]Processed:
vso[task.setvariable variable=MSBuild.SonarQube.Internal.ServerVersion;]6.7.1.35068
2018-01-16T09:28:19.7323972Z 2018-01-16T09:28:19.7323972Z
2018-01-16T09:28:19.7323972Z ##[debug]The SonarQube server version is
6.7.1.35068 2018-01-16T09:28:19.7467772Z Waiting on the SonarQube server to finish processing in order to determine the quality gate
status. 2018-01-16T09:28:19.7467772Z 2018-01-16T09:28:19.7467772Z
2018-01-16T09:28:19.7467772Z ##[debug]Invoke - Get-TaskVariable cmdlet
2018-01-16T09:28:19.7467772Z ##[debug]Variable read:
Agent.BuildDirectory = d:/_work\3 2018-01-16T09:28:19.7624290Z
[debug]Could not find the task details file at d:/_work\3.sonarqube\out.sonar\report-task.txt
2018-01-16T09:28:19.7936587Z
[error]System.Management.Automation.RuntimeException: Cannot determine if the analysis has finished. Possible cause: your SonarQube
server version is lower than 5.3 - for more details see
https://go.microsoft.com/fwlink/?LinkId=722407 --->
System.Management.Automation.RuntimeException: Cannot determine if the
analysis has finished. Possible cause: your SonarQube server version
is lower than 5.3 - for more details see
https://go.microsoft.com/fwlink/?LinkId=722407
2018-01-16T09:28:19.7936587Z ##[debug]Processed: ##vso[task.logissue
type=error;]System.Management.Automation.RuntimeException: Cannot
determine if the analysis has finished. Possible cause: your SonarQube
server version is lower than 5.3 - for more details see
https://go.microsoft.com/fwlink/?LinkId=722407 --->
System.Management.Automation.RuntimeException: Cannot determine if the
analysis has finished. Possible cause: your SonarQube server version
is lower than 5.3 - for more details see
https://go.microsoft.com/fwlink/?LinkId=722407
2018-01-16T09:28:19.7936587Z --- End of inner exception stack trace
--- 2018-01-16T09:28:19.7936587Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable
input) 2018-01-16T09:28:19.7936587Z at
System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace
rs, Boolean performSyncInvoke) 2018-01-16T09:28:19.7936587Z at
System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace
rsToUse, Boolean isSync) 2018-01-16T09:28:19.7936587Z at
System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection1
input, PSDataCollection1 output, PSInvocationSettings settings)
2018-01-16T09:28:19.7936587Z at
System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection1
input, PSDataCollection1 output, PSInvocationSettings settings)
2018-01-16T09:28:19.7936587Z at
Microsoft.TeamFoundation.DistributedTask.Handlers.LegacyVSTSPowerShellHost.VSTSPowerShellHost.Main(String[]
args) 2018-01-16T09:28:19.8092817Z
[error]LegacyVSTSPowerShellHost.exe completed with return code: -1. 2018-01-16T09:28:19.8092817Z ##[section]Finishing: Complete the
SonarQube analysis
I have checked the build log in debug mode, but i can't see anything wrong.
Temp location with the full log with debug mode:
https://onedrive.live.com/?authkey=%21ADdDbeYD4oxJ9NA&id=5A1F84872B7BA3C1%21952&cid=5A1F84872B7BA3C1
Note that i have replaced my organisation name with: myorganiation and the project name with MyProject in the log.
It is working! I have configured a build agent on my laptop and then the analyze works. After comparing logs a long time i have found it. And this topic helpt me stackoverflow.com/questions/23696251/…. It was de working path for the build agent. We had it configured like this: "workFolder": "d:/_work" but the correct path must be: "workFolder": "d:\\_work"
After reviewing lots of posts and blogs I still can´t figure this out.
This my current stack
Sonar: 6.3.0.19869
Sonar Code Analyzer for C#: 5.10.1 (build 1411)
Jenkins: 2.46.1
Jenkins sonarqube scanner: 2.6.1
TFS branches:
- Dev
- Main
Sonarqube projects (deactivated rules S104, S105)
- Dev
- Main
When I run DEV Branch Jenkins Job, the upload to sonar DEV project is successful
When I run DEV Branch Jenkins Job, the upload to sonar Main project is successful
When I run Main Branch Jenkins Job, the upload to sonar Main project FAILS
DEV - DEV = OK
DEV - MAIN = OK
MAIN - MAIN = ERROR
Both file sets generated by sonarQube scanner are about 100Mb (Dev 111MB / Main 106MB)
ERROR: Error during SonarQube Scanner execution
java.lang.IllegalArgumentException: Start pointer [line=4541, lineOffset=49] should be before end pointer [line=4541, lineOffset=49]
at org.sonar.api.internal.google.common.base.Preconditions.checkArgument(Preconditions.java:145)
at org.sonar.api.batch.fs.internal.DefaultInputFile.newRangeValidPointers(DefaultInputFile.java:265)
at org.sonar.api.batch.fs.internal.DefaultInputFile.newRange(DefaultInputFile.java:203)
at org.sonarsource.dotnet.shared.plugins.SensorContextUtils.toTextRange(SensorContextUtils.java:41)
at org.sonarsource.dotnet.shared.plugins.protobuf.SymbolRefsImporter.consumeFor(SymbolRefsImporter.java:47)
at org.sonarsource.dotnet.shared.plugins.protobuf.SymbolRefsImporter.consumeFor(SymbolRefsImporter.java:33)
at org.sonarsource.dotnet.shared.plugins.protobuf.ProtobufImporter.consume(ProtobufImporter.java:50)
at org.sonarsource.dotnet.shared.plugins.protobuf.RawProtobufImporter.accept(RawProtobufImporter.java:44)
at org.sonarsource.dotnet.shared.plugins.AbstractSensor.parseProtobuf(AbstractSensor.java:90)
at org.sonarsource.dotnet.shared.plugins.AbstractSensor.importResults(AbstractSensor.java:83)
at org.sonar.plugins.csharp.CSharpSensor.executeInternal(CSharpSensor.java:119)
at org.sonar.plugins.csharp.CSharpSensor.execute(CSharpSensor.java:79)
at org.sonar.scanner.sensor.SensorWrapper.analyse(SensorWrapper.java:53)
at org.sonar.scanner.phases.SensorsExecutor.executeSensor(SensorsExecutor.java:57)
at org.sonar.scanner.phases.SensorsExecutor.execute(SensorsExecutor.java:49)
at org.sonar.scanner.phases.AbstractPhaseExecutor.execute(AbstractPhaseExecutor.java:74)
at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:175)
at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:143)
at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:128)
at org.sonar.scanner.scan.ProjectScanContainer.scan(ProjectScanContainer.java:262)
at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:257)
at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:247)
at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:143)
at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:128)
at org.sonar.scanner.task.ScanTask.execute(ScanTask.java:47)
at org.sonar.scanner.task.TaskContainer.doAfterStart(TaskContainer.java:86)
at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:143)
at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:128)
at org.sonar.scanner.bootstrap.GlobalContainer.executeTask(GlobalContainer.java:118)
at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:117)
at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:60)
at com.sun.proxy.$Proxy0.execute(Unknown Source)
at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(EmbeddedScanner.java:233)
at org.sonarsource.scanner.api.EmbeddedScanner.runAnalysis(EmbeddedScanner.java:151)
at org.sonarsource.scanner.cli.Main.runAnalysis(Main.java:123)
at org.sonarsource.scanner.cli.Main.execute(Main.java:77)
at org.sonarsource.scanner.cli.Main.main(Main.java:61)
What I can think of is that is something wrong with the MAIN code base, but can't figure it out
Any ideas?
We recently received a bug report with the same error: Tuple literals make the analysis fail, I suppose it could be caused by other C# 7 constructs as well. Unfortunately we don't have a fix or workaround yet (except not using some C# 7 features for the time being).
I cannot promise a fix for the next version of SonarC# because we did not investigated the problem yet, but we will do our best to resolve the problem as soon as possible.