corvus-dotnet / corvus-dotnet/Corvus.Testing

Warnings with empty stderror

Open
#303 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
13
Forks
11
PR merge metrics
No merged PRs in 30d

Description

I keep receiving warnings with empty stderror messages after the test have run:

```
warn: Corvus.Testing.AzureFunctions.FunctionsController[0]
StdErr for process /usr/local/lib/node_modules/azure-functions-core-tools/bin/func host start --port 7075 --csharp, working directory /home/..../bin/Debug/net6.0:

info: Corvus.Testing.AzureFunctions.FunctionsController[0]
StdOut for process /usr/local/lib/node_modules/azure-functions-core-tools/bin/func host start --port 7075 --csharp, working directory /home/..../bin/Debug/net6.0: Output cleared at 26-01-2022 13:31:22

warn: Corvus.Testing.AzureFunctions.FunctionsController[0]
StdErr for process /usr/local/lib/node_modules/azure-functions-core-tools/bin/func host start --port 7075 --csharp, working directory /home/....../bin/Debug/net6.0: Output cleared at 26-01-2022 13:31:22

```

I am using version 1.5.0-253-unix-support.5.

Am I doing something wrong?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in FunctionsController, focusing on the process stderr and stdout logging shown for `func host start --port 7075 --csharp`. Reproduce with version 1.5.0-253-unix-support.5 and check whether empty output is logged as a warning. Done means empty stderr no longer produces misleading warnings while meaningful process output remains visible.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.