-
Notifications
You must be signed in to change notification settings - Fork 774
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
[Error] While setting up dev env #5890
Comments
Looking at the screenshots, it looks like you might have multiple issues. I see one exception in your screenshot:
You would have to review if that endpoint is already in use on your machine. |
It looks like you're working with multiple repos at once. Let me stress that you should focus on one repo at a time until you can resolve all the issues. Try this:
This will either pass or fail. If this fails you should have a distinct list of issues to investigate. |
@TimothyMothra sorry about the confusion in above comment. Note: Before installing the required version of .NET SDK which is 9.0.100-rc.1.24452.12 I installed a .NET SDK 8.0.403. But since the required version was .NET SDK 9.0.100-rc.1.24452.12 so I deleted the old one from system. Now the dotnet test is still giving same errors. I'm going to copy some of the failed test logs:
|
@TimothyMothra do I need to install these dependencies explicitly individually to set up dev env? OpenTelemetry Although it's not mention in CONTRIBUTING.md to install these dependencies in order to contribute to the project? Note: As a beginner I apologize for asking silly questions. I'm a newbie trying to contribute to Otel.dotnet. Thank you. |
Please keep the .NET 8.0 and see if it helps. (Looks like the contributing doc may need an update to call this out) |
Hi @Annosha,
|
@TimothyMothra the build was successful with zero errors or warnings. |
@cijothomas yes indeed I kept the .NET 8.0 eventually and that did solve some of errors. But the latest errors for |
@rajkumar-rangaraj Do you have any suggestions or feedback on this issue? |
Here is the full log of build and |
@TimothyMothra the opentelemetry-java also fails test on windows env. I had it confirmed from a maintainer and another contributor. The build for otel-java is successful too. Has anyone tried setting up otel-dotnet on windows env? |
I use Windows. And our CI builds run on Windows. I reviewed the text log.
I don't see any indication in the log what's causing these tests to abort. The HttpListenerException is the same one I described earlier. Several of our tests set up a local web server to simulate transmitting or receiving data. My best guess is that one of these tests are failing to shut down its test server and that blocks any other test from setting up its own test server, causing that test to fail. Next Steps@Annosha, the good news is that the overall majority of your tests appear to be running successfully. You should consider yourself unblocked if you're ready to work on any contributions. To clear this specific error, the easiest thing you can do would be to restart your machine. |
Package
OpenTelemetry
Package Version
$(TargetFrameworksForLibrariesExtended) OpenTelemetry .NET SDK core-Runtime Version
Microsoft.AspNetCore.App 9.0.0-rc.1.24452.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 9.0.0-rc.1.24431.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 9.0.0-rc.1.24452.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Description
I was setting up dev env on my local machine and followed the instructions in CONTRIBUTING.md.
After cloning and running
dotnet test
on top level. I get following errors.Note: I've changed touched the code yet.
What am I missing?
Steps to Reproduce
Followed instructions here I forked and cloned the repo with required version of sdk
"version": "9.0.100-rc.1.24452.12"
and ran:
dotnet test
Expected Result
Since I haven't made changes in the code the tests must pass without errors.
Actual Result
Additional Context
No response
The text was updated successfully, but these errors were encountered: