-
Notifications
You must be signed in to change notification settings - Fork 94
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
Throws STDOUT warning on AppVeyor and WIndows 10 64 #110
Comments
@replaysMike sorry for the delay getting back to you. This should not affect the coverage posting. Can you confirm this is just a error message? |
Due to no answering since some time ago, I'm closing this issue. |
The error keeping throwing in AppVeyor with Windows. Yes, it is just an error message that can be interpreted by some filters as error in build process. Some example (error starts at line 318): Here's a snippet:
|
I'm reopening the issue. Thank you for reporting. |
@guibranco a possible workaround is to tweak the logging level and disable E.g. write a file <configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<withJansi>false</withJansi>
<encoder>
<pattern>%date %-16level %-10.-10logger %message %n</pattern>
</encoder>
</appender>
<logger name="application" level="ERROR"/>
<root level="WARN">
<appender-ref ref="STDOUT"/>
</root>
</configuration> And run the reporter passing the new configuration: java -jar ./codacy-test-reporter.jar report -Dlogback.configurationFile=logback.xml -l CSharp -t %CODACY_PROJECT_TOKEN% -r "%CD%\Tests\%SOLUTION_NAME%.Tests\coverage.cobertura.xml" I'm sorry but I don't have access to a windows machine to test, can you check and report the result? |
@andreaTP I'll try soon, and then I'll let you know if this works! |
@andreaTP I put the file in a "Build" directory in the repository and I'm passing it as a reference in the build, it's generating an error and breaking the build process...
This is how my build section is in the appveyor.yml: build_script:
- dotnet build %SOLUTION_NAME%.sln
- dotnet test .\Tests\%SOLUTION_NAME%.Tests\%SOLUTION_NAME%.Tests.csproj /p:CollectCoverage=true /p:CoverletOutputFormat="opencover"
- codecov -f %CD%\Tests\%SOLUTION_NAME%.Tests\coverage.opencover.xml
- dotnet test .\Tests\%SOLUTION_NAME%.Tests\%SOLUTION_NAME%.Tests.csproj /p:CollectCoverage=true /p:CoverletOutputFormat="cobertura"
- java -jar ./codacy-test-reporter.jar report -Dlogback.configurationFile="%CD%\Build\logback.xml" -l CSharp -t %CODACY_PROJECT_TOKEN% -r "%CD%\Tests\%SOLUTION_NAME%.Tests\coverage.cobertura.xml" |
It works if I switch the arguments order, passing the -D... right after the -jar option Example: build_script:
- dotnet build %SOLUTION_NAME%.sln
- dotnet test .\Tests\%SOLUTION_NAME%.Tests\%SOLUTION_NAME%.Tests.csproj /p:CollectCoverage=true /p:CoverletOutputFormat="opencover"
- codecov -f %CD%\Tests\%SOLUTION_NAME%.Tests\coverage.opencover.xml
- dotnet test .\Tests\%SOLUTION_NAME%.Tests\%SOLUTION_NAME%.Tests.csproj /p:CollectCoverage=true /p:CoverletOutputFormat="cobertura"
- java -jar -Dlogback.configurationFile="%CD%\Build\logback.xml" ./codacy-test-reporter.jar report -l CSharp -t %CODACY_PROJECT_TOKEN% -r "%CD%\Tests\%SOLUTION_NAME%.Tests\coverage.cobertura.xml" |
@guibranco my bad for the arguments order, sorry for the trouble! |
Yes! Now it's working like a charm 👍👏 Thanks! |
Hi @guibranco, |
It worked with 7.6.8 log: https://ci.appveyor.com/project/guibranco/viacep/builds/32012715 |
Thank you very much for testing it! |
Scala Version (2.10.x / etc)
Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)
Windows 10 x64
JDK (Oracle 1.8.0_72, OpenJDK 1.8.x, Azul Zing)
java version "1.8.0_191"
Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)
Library Dependencies
If this is an issue that involves integration with another system, include the exact version and OS of the other system, including any intermediate drivers or APIs i.e. if you connect to a PostgreSQL database, include both the version / OS of PostgreSQL and the JDBC driver version used to connect to the database.
Expected Behavior
java -jar codacy-coverage-reporter-4.0.5-assembly.jar final --project-token "TOKEN" --commit-uuid "COMMITID"
Actual Behavior
Exception thrown when generating report:
java -jar codacy-coverage-reporter-4.0.5-assembly.jar final --project-token "TOKEN" --commit-uuid "COMMITID"
Reproducible Test Case
On Windows 10 x64:
java -jar codacy-coverage-reporter-4.0.5-assembly.jar final --project-token "TOKEN" --commit-uuid "COMMITID"
The text was updated successfully, but these errors were encountered: