[ 
https://issues.apache.org/jira/browse/THRIFT-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jens Geyer updated THRIFT-5140:
-------------------------------
    Description: 
The netstd tests have been added to cross test etc just recently as the netstd 
bindings are the successor to both old netcore and csharp bindings. The Travis 
logs indicate that there is something fundamentally wrong with these test when 
executed on the CI machines. This needs to be investigated and fixed.

One example of many messages being logged:
{code}
*************************** client message ***************************
Sun Mar 15 11:08:09 2020
Executing: dotnet run --no-build --project=Client/Client.csproj client 
--protocol=binary --transport=framed --port=41989
Directory: /thrift/src/test/netstd
config:delay: 5
config:timeout: 10
===============================================================================
System.ComponentModel.Win32Exception (2): No such file or directory
   at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] 
argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, 
Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, 
UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean 
usesTerminal, Boolean throwOnNoExec)
   at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at Microsoft.DotNet.Cli.Utils.Command.Execute()
   at Microsoft.DotNet.Tools.Run.RunCommand.Execute()
   at Microsoft.DotNet.Tools.Run.RunCommand.Run(String[] args)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry 
telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)
===============================================================================
Return code: 1 (negative values indicate kill by signal)
Test execution took 1.9 seconds.
Sun Mar 15 11:08:11 2020

{code}

  was:The netstd tests have been added to cross test etc just recently as the 
netstd bindings are the successor to both old netcore and csharp bindings. The 
Travis logs indicate that there is something fundamentally wrong with these 
test when executed on the CI machines. This needs to be investigated and fixed.


> Netstd cross tests largely broken on Travis CI
> ----------------------------------------------
>
>                 Key: THRIFT-5140
>                 URL: https://issues.apache.org/jira/browse/THRIFT-5140
>             Project: Thrift
>          Issue Type: Bug
>          Components: netstd - Library
>            Reporter: Jens Geyer
>            Priority: Major
>
> The netstd tests have been added to cross test etc just recently as the 
> netstd bindings are the successor to both old netcore and csharp bindings. 
> The Travis logs indicate that there is something fundamentally wrong with 
> these test when executed on the CI machines. This needs to be investigated 
> and fixed.
> One example of many messages being logged:
> {code}
> *************************** client message ***************************
> Sun Mar 15 11:08:09 2020
> Executing: dotnet run --no-build --project=Client/Client.csproj client 
> --protocol=binary --transport=framed --port=41989
> Directory: /thrift/src/test/netstd
> config:delay: 5
> config:timeout: 10
> ===============================================================================
> System.ComponentModel.Win32Exception (2): No such file or directory
>    at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] 
> argv, String[] envp, String cwd, Boolean redirectStdin, Boolean 
> redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 
> userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, 
> Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
>    at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
>    at System.Diagnostics.Process.Start()
>    at Microsoft.DotNet.Cli.Utils.Command.Execute()
>    at Microsoft.DotNet.Tools.Run.RunCommand.Execute()
>    at Microsoft.DotNet.Tools.Run.RunCommand.Run(String[] args)
>    at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry 
> telemetryClient)
>    at Microsoft.DotNet.Cli.Program.Main(String[] args)
> ===============================================================================
> Return code: 1 (negative values indicate kill by signal)
> Test execution took 1.9 seconds.
> Sun Mar 15 11:08:11 2020
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to