-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Linux / OSX Build has a lot of failures #7477
Comments
Originally posted by @Aaronontheweb in #7468 (comment) |
Eh, I don't think this is that big of an issue - you can just look at the Test Results pane in AzDo and see the attachment for specific unit test failures. These logs all stem from Roslyn trying to analyze the solution to determine which parts of the code are affected by the Git diff. I agree it'd be better if we squelched them but it's not the end of the world. |
Agree it might not be a critical issue, but as a new contributor to the project I find it baffling and distracting from the actual source of error |
feel free to close this as not planned if there is no issue here |
Totally fair! If you want to submit a PR to Incrementalist that's also OSS and available here: https://github.com/petabridge/Incrementalist I really need to make that tool easier to use to boot... |
Marked this as a "Developer Experience" issue and as "up for grabs" - which means we'd love to have someone in the community take a stab at it |
Perhaps it would make sense to migrate to fresher FAKE release (similar to how it was done here akkadotnet/Akka.Persistence.Sql#361), but then later FAKE was completely dropped from the project |
Looks like this issue with the MSBuild output is solved in newer versions of the Roslyn tooling, which we'll introduce when we install Incrementalist 1.0 into Akka.NET |
PR validation pipeline on Linux / OSX writes a few thousand lines of error logs such as one below making it impractical for actual build failure investigation.
Examples of failing builds:
abd10495
4db39055
The text was updated successfully, but these errors were encountered: