-
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
ConcurrentModificationException #1168
Comments
The problem is that the for (ITestResult r : confResults) {
if (! seen.containsKey(r.getMethod())) {
result += r.getEndMillis() - r.getStartMillis();
seen.put(r.getMethod(), r);
}
confResults.removeAll(seen.values());
} |
Good catch. Would you be willing to send a PR? Cédric On Fri, Sep 23, 2016 at 3:51 PM, Ben Manes [email protected] wrote:
|
ConcurrentModificationException during iteration (fixes #1168)
when will we expect the issue fixed release? as I am also getting the same issue. |
hi @shabana-parveen |
Thanks @missedone |
Still seeing the error with 6.9.13.8 and u102:
POM:
|
I don't see my fix in |
Exactly. This issue is still present in the version |
Yes, I can also see the same |
This issue appears to be closed but I, like others, are still seeing the issue. Just making sure that folks area aware this is still a problem, including with the 6.9.13.8 release. |
The fix should be available in the next release. |
Downgrade testng, because of: testng-team/testng#1168.
When shall we release next version. See the problem on 6.9.13.8 with Eclipse. Thanks! |
Hi there. Any ETA on a release vehicle that contains this fix? I'm stuck on this release due to a fix that I need in 6.9.13.x :) |
@kodayashi - The latest version of TestNG viz., 6.10 is already available in bintray. You can just add the following and you should be able to consume it <repositories>
<repository>
<id>bintray-cbeust-maven</id>
<name>bintray</name>
<url>http://dl.bintray.com/cbeust/maven</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>6.10</version>
</dependency>
</dependencies> |
Is 6.10 stable? Production ready? |
Not sure what you mean by "Production ready" ? A released product is meant to be stable consumable no ? |
I'm asking if this is a Beta you're suggesting |
No this is not a beta. This is a released version of TestNG. |
Cool, thanks. Is there a timeline for when it will be in Eclipse's repositories? |
@cbeust should be able to answer that. I know he mentioned he is going to be pushing the changes to Maven Central as well. |
Lol, so is it a Beta after all? Someone enlighten me |
TestNG 6.10 is released. |
Sweet, thanks everyone! |
Neat. Good work folks |
…NG to the version 6.10. It seems to be working: the java.util.ConcurrentModificationException when performing 'mvn test' is no more.
TestNG Eclipse Plugin 6.10.0.201612030230 is released. |
When will 6.10.x be available from the Maven Central? |
The 6.10.x release that will contain the fix for this issue has still not been posted yet. When can we expect this to be available? |
@sbabcoc |
I upgraded to TestNG 6.10.0.201612030230, and this issue still exists. |
@sbabcoc , Eclipse Plugin simply respects the testng jar version of your project, so could you check the testng version on your project classpath? make sure that's up to date. |
still i hit the same problem with testng 6.10. can you please share the workaround on this? |
@anand853 Could you share your stacktrace? I bet the issue is not the same but a similar one. |
@juherr ,please find the logs testng.xml configuration: name="Suite" parallel="methods" Maven Error logs: test73(test.com.t.test.com.t.AppBraavaTermsTest) Time elapsed: 0 sec <<< FAILURE! test77(test.com.t.test.com.t.AppBraavaTermsTest) Time elapsed: 0.169 sec <<< FAILURE! test76(test.com.t.test.com.t.AppBraavaTermsTest) Time elapsed: 0.17 sec <<< FAILURE! test66(test.com.t.test.com.t.AppBraavaTermsTest) Time elapsed: 0.17 sec <<< FAILURE! Results : Failed tests: Tests run: 331, Failures: 5, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ |
@anand853 - This is not a problem from TestNG. Looks like you are facing this problem from extent reports, to be specific this method. I would suggest that you please file a bug here |
@krmahadevan , |
@anand853 - There are no work arounds for this. Extent Reports needs to fix itself so that it doesn't try to modify and iterate a List at the same time without any sort of synchronization mechanism that wraps access to the list. That would ensure that you don't see this exception from extent reports. Not much can be done, apart from fixing the problematic code. |
For reference: anshooarora/extentreports-java#769 |
version : 6.10 error Results : Failed tests: Tests run: 260, Failures: 1, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ |
It looks the exception comes from the test itself and not TestNG |
Hi all, I am using testng-version 7.1.0, getting concurrentModificationException in following line. Error: Note: i use DataProvider, Multithreading. |
@anandhapriyak Your issue comes from com.aventstack.extentreports. You should open an issue there https://github.com/extent-framework/extentreports-java |
Jeez, talk about necro 😅 |
When running a test class using
6.9.13.8
the tests pass, but the following error is printed. This does not occur in6.9.12
. (Running via Eclipse)The text was updated successfully, but these errors were encountered: