[JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2419?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-2419:
-----------------------------------
Assignee: (was: Michael Musgrove)
> Consider reducing the number of JMH perf test forks on PRs
> ----------------------------------------------------------
>
> Key: JBTM-2419
> URL: https://issues.jboss.org/browse/JBTM-2419
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
>
> We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/m...] state:
> bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches.
> Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions:
> - reduce the number of forks;
> - run a subset of performance tests on each PR and then run them all once a week or so on the main build
> My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (JBTM-1906) Improve CI timeout handling
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1906?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-1906:
-----------------------------------
Assignee: (was: Gytis Trikleris)
> Improve CI timeout handling
> ---------------------------
>
> Key: JBTM-1906
> URL: https://issues.jboss.org/browse/JBTM-1906
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Reporter: Tom Jenkinson
> Priority: Minor
>
> We do not timeout the CI runs so that someone can have the opportunity to kill -3 the Java processes when they notice that the run has hung. It is therefore possible for the rogue processes to clog up CI. Also, if we were to move to alternative CI arrangements it may be necessary to set a timeout and in that case we would not have the opportunity to be alerted of the hang.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (JBTM-2473) Document qa/ build suite
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2473?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-2473:
-----------------------------------
Assignee: (was: Tom Jenkinson)
> Document qa/ build suite
> ------------------------
>
> Key: JBTM-2473
> URL: https://issues.jboss.org/browse/JBTM-2473
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Reporter: Tom Jenkinson
> Attachments: QA Notes (5.1).ppt
>
>
> There is a wealth of testing in the qa/ testsuite but it is not accessible to understand what is being tested by it.
> * How do we evaluate the impact of running less of the suite
> * Is it possible to run the suite with other object stores easily?
> * What is the quantified value of running the whole suite
> * Can we run with different ORBs
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (JBTM-1802) Consider moving Arquillian profiles to root pom.xml
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1802?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-1802:
-----------------------------------
Assignee: (was: Amos Feng)
> Consider moving Arquillian profiles to root pom.xml
> ---------------------------------------------------
>
> Key: JBTM-1802
> URL: https://issues.jboss.org/browse/JBTM-1802
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Build System, Testing
> Reporter: Paul Robinson
> Priority: Minor
>
> We have three Arquillian profiles (for managed, remote and ipv6-managed) present in the pom of nearly every test that uses Arquillian. I suspect they can all be identical and thus placed int he root pom.xml. This should simplify maintenance and will ensure any fixes to this config are made throughout.
> The problem is that we may have legitimate reasons for this config to differ for some tests. Maybe we could use overrides in these cases.
> Assigning to Tom for his input.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (JBTM-809) Provide instructions for using ironjacamar as well as transactional driver
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson reassigned JBTM-809:
----------------------------------
Assignee: (was: Tom Jenkinson)
> Provide instructions for using ironjacamar as well as transactional driver
> --------------------------------------------------------------------------
>
> Key: JBTM-809
> URL: https://issues.jboss.org/browse/JBTM-809
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Resource Manager
> Reporter: Tom Jenkinson
>
> Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server.
> There are several bugs open against transactional driver that will be resolved by completing this work.
> The general approach would be along the lines of:
> Startup
> ======
> Embedded embedded = EmbeddedFactory.create();
> embedded.startup();
> embedded.deploy(new File("my-rar.rar").toURI().toURL());
> embedded.deploy(new File("my-ds.xml").toURI().toURL());
> In use
> =====
> InitialContext initialContext = new InitialContext();
> UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction");
> DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS");
> Shutdown
> =======
> embedded.undeploy(new File("my-ds.xml").toURI().toURL());
> embedded.undeploy(new File("my-rar.rar").toURI().toURL());
> embedded.shutdown(); // does not work - some threads don't stop
> Problems?
> =========
> JCA transitive dependencies?
> Accessing ds files from war?
> Accessing rar from war?
> May have to provide these both upfront.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months