Using a timeout with testng breaks everything #168
Comments
ivankelly
added a commit
to ivankelly/pulsar
that referenced
this issue
Apr 4, 2018
The annotation listener adds timeouts to all tests, which changes the threading model, which breaks arquillian. I've created an issue[1] on arquillian for this, but until that is fixed, timeouts cannot be used with arquillian. [1] arquillian/arquillian-core#168
ivankelly
added a commit
to ivankelly/pulsar
that referenced
this issue
Apr 4, 2018
The annotation listener adds timeouts to all tests, which changes the threading model, which breaks arquillian. I've created an issue[1] on arquillian for this, but until that is fixed, timeouts cannot be used with arquillian. [1] arquillian/arquillian-core#168
merlimat
pushed a commit
to apache/pulsar
that referenced
this issue
Apr 5, 2018
The annotation listener adds timeouts to all tests, which changes the threading model, which breaks arquillian. I've created an issue[1] on arquillian for this, but until that is fixed, timeouts cannot be used with arquillian. [1] arquillian/arquillian-core#168
merlimat
pushed a commit
to apache/pulsar
that referenced
this issue
Apr 6, 2018
* Integration smoke test for pulsar Boots a cluster, sends and receives some messages, shuts down the cluster. If anything fails, then something is very broken. * license fix * Disable AnnotationListener for integration tests The annotation listener adds timeouts to all tests, which changes the threading model, which breaks arquillian. I've created an issue[1] on arquillian for this, but until that is fixed, timeouts cannot be used with arquillian. [1] arquillian/arquillian-core#168
|
Thanks for reporting this issue. Could you contribute a reproducer test? |
sijie
pushed a commit
to apache/pulsar-release
that referenced
this issue
Nov 12, 2020
The annotation listener adds timeouts to all tests, which changes the threading model, which breaks arquillian. I've created an issue[1] on arquillian for this, but until that is fixed, timeouts cannot be used with arquillian. [1] arquillian/arquillian-core#168
sijie
pushed a commit
to apache/pulsar-release
that referenced
this issue
Nov 12, 2020
* Integration smoke test for pulsar Boots a cluster, sends and receives some messages, shuts down the cluster. If anything fails, then something is very broken. * license fix * Disable AnnotationListener for integration tests The annotation listener adds timeouts to all tests, which changes the threading model, which breaks arquillian. I've created an issue[1] on arquillian for this, but until that is fixed, timeouts cannot be used with arquillian. [1] arquillian/arquillian-core#168
sijie
pushed a commit
to apache/pulsar-release
that referenced
this issue
Nov 12, 2020
The annotation listener adds timeouts to all tests, which changes the threading model, which breaks arquillian. I've created an issue[1] on arquillian for this, but until that is fixed, timeouts cannot be used with arquillian. [1] arquillian/arquillian-core#168
sijie
pushed a commit
to apache/pulsar-release
that referenced
this issue
Nov 12, 2020
* Integration smoke test for pulsar Boots a cluster, sends and receives some messages, shuts down the cluster. If anything fails, then something is very broken. * license fix * Disable AnnotationListener for integration tests The annotation listener adds timeouts to all tests, which changes the threading model, which breaks arquillian. I've created an issue[1] on arquillian for this, but until that is fixed, timeouts cannot be used with arquillian. [1] arquillian/arquillian-core#168
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Overview
If you add a timeout to a testng test using org.jboss.arquillian.testng.Arquillian, everything breaks.
Expected Behaviour
Adding a timeout shouldn't break stuff.
Current Behaviour
It breaks, and it breaks in a very non-obvious manner.
Steps To Reproduce
@Testto@Test(timeOut=1000)on the testArquillianClass1Additional Information
Tested with testng 6.13.1, but the problem is with arquillian. It runs
@BeforeSuitein a different thread to the test itself.@BeforeSuitesets up a thread local context object (TestRunnerAdapter), so when the test runs, it doesn't find this object, and everything goes to hell.The text was updated successfully, but these errors were encountered: