-
Notifications
You must be signed in to change notification settings - Fork 226
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
[allure-testng] Could not write Allure test result #197
Comments
@EzioAuditoreDeFirenze it would be much easier for us if you provide a sample project to reproduce the problem |
@baev I had a very similar issue recently with allure-testng:2.6.0, it started with the following: Updating the jackson-databind, jackson-annotation and jackson-core dependencies resolved the issue for me. Consider updating those dependencies in allure-java-commons component. |
Updating jackson-core, jackson-annotation and jackson-databind to version 2.9.4 fixed the issue |
@tlytvyn how can it be solved without waiting for the bug fix? |
@MickyOwly check my reply attentively |
I added to my project: However issue is still on going when running tests in parallel after retry:
|
I opened a repository for reproduction of the issue: Just clone it and run 'mvn test'. |
Change OutputStream object to BufferedOutputStream in order to solve allure-framework/allure-java#197 . Tested and verified.
@baev can you please review allure-framework/allure2-model#16 ? |
@AutomatedOwl done, check it out |
Looks like it's fixed in 2.7.0 :) |
Still a bug at 2.8.0, Log: |
@AvrahamAtia thats maybe a different issue. Could you please provide an example project to reproduce the problem as well as providing full stack trace of the error? |
@baev It happen When I am using timeOut property of TestNG, Do you any idea why it happen only when I am using timeOut?! |
@baev |
@baev @AvrahamAtia Managed to reproduce it again with allure-testng 2.8.1 and testng 6.14.3: |
@baev @AvrahamAtia it's reproduced using Maven with JDK8. Upgrading to JDK11 seems to fix the issue. |
@AutomatedOwl @baev Should I downgrade TestNG or allure? I prefer work with JDK8 not update to JDK11.. |
from allure-framework/allure2#738
I'm submitting a ...
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
In my testcase,if run failed,it will throw AllureResultsWriteException
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Other information
io.qameta.allure.AllureResultsWriteException: Could not write Allure test result
at io.qameta.allure.FileSystemResultsWriter.write(FileSystemResultsWriter.java:43)
at io.qameta.allure.AllureLifecycle.lambda$writeTestCase$12(AllureLifecycle.java:197)
at java.util.Optional.ifPresent(Optional.java:159)
at io.qameta.allure.AllureLifecycle.writeTestCase(AllureLifecycle.java:195)
at io.qameta.allure.testng.AllureTestNg.onTestFailure(AllureTestNg.java:260)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1738)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1722)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1258)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.channels.ClosedByInterruptException
at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:216)
at java.nio.channels.Channels.writeFullyImpl(Channels.java:78)
at java.nio.channels.Channels.writeFully(Channels.java:101)
at java.nio.channels.Channels.access$000(Channels.java:61)
at java.nio.channels.Channels$1.write(Channels.java:174)
at com.fasterxml.jackson.core.json.UTF8JsonGenerator._flushBuffer(UTF8JsonGenerator.java:2085)
at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1127)
at com.fasterxml.jackson.databind.ObjectMapper._configAndWriteValue(ObjectMapper.java:3898)
at com.fasterxml.jackson.databind.ObjectMapper.writeValue(ObjectMapper.java:3164)
at io.qameta.allure.FileSystemResultsWriter.write(FileSystemResultsWriter.java:41)
... 12 more
The text was updated successfully, but these errors were encountered: