-
Notifications
You must be signed in to change notification settings - Fork 78
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
Adding logging causes exception and failure #451
Comments
Found another:
Can see this in our CI run here: https://github.com/CommunityToolkit/Labs-Windows/actions/runs/4077929697/jobs/7027560709#step:8:1138 Logs from our CI as well: |
Interestingly, on a linux environment on Codespaces things seem to work, so these may be issues with the loggers on Windows only? (Saw them locally and in our CI, so Win10 and Server 2022.) Logs from linux environment in codespaces attached here. |
SlnGen is faking a project started event so that the binary log shows SUCCESS vs FAILURE. It would appear that the |
See this with 11.2.3 and 11.2.6 still. |
Looks like the issue is coming up with ReusableLogger/TextWriter as well: https://github.com/CommunityToolkit/Tooling-Windows-Submodule/actions/runs/11509384515/job/32039385206#step:12:3084
|
Added the following logging parameters:
Without them, slngen worked, but with them, it causes this error:
(realized I had commas above as was confused by #450; so that may have been part of the issue for this one, but had another stack below)
The text was updated successfully, but these errors were encountered: