May 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2405) QA suite test failure: CrashRecovery05_1 Test04

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2405: ------------------------------------- Summary: QA suite test failure: CrashRecovery05_1 Test04 Key: JBTM-2405 URL: https://issues.jboss.org/browse/JBTM-2405 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Minor Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFIL... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2395: ------------------------------------- It was fixed by this bit: https://github.com/jbosstm/narayana/blob/143e65b55de87d9ac18f7e2e1f0be2fb... I think what could be going on is the -Pcommunity profile isn't being set in that build? > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2395: ------------------------------------- The strange thing is I think I fixed those. This one (the first one) in particular was fixed: [ERROR] Exit code: 1 - /home/hudson/workspace/btny-pulls-quickstart/narayana/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfGraph.java:716: error: package org.jfree.beans does not exist > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2395: ---------------------------------------- There are more javadoc errors - I am working my through them (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-quickstart/92/console) > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2404?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2404: ------------------------------------- Yeah, sorry it was my mistake I have been trying to remove the app server tests from being ran (so the job can stay on JDK7) but when I tried to put RTS_AS_TESTS=0 those tests are still ran. I managed to disable the OSGi tests but can't get the RTS ones suppressed :( Thanks for looking into it mike. > narayana-codeCoverage CI job is not producing any output > -------------------------------------------------------- > > Key: JBTM-2404 > URL: https://issues.jboss.org/browse/JBTM-2404 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/conso... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2404?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2404: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/845 > narayana-codeCoverage CI job is not producing any output > -------------------------------------------------------- > > Key: JBTM-2404 > URL: https://issues.jboss.org/browse/JBTM-2404 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/conso... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2404?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2404: ---------------------------------------- The failure is because we only run PROFILE=MAIN on the code coverage job. So I can fix it by any combination of the following: 1. skip the run the QA jacoco report (ie remove the line ant -f run-tests.xml jacoco-report from the job config) 2. conditionally run the QA jacoco report task based on the presence of QA execution data 3. update the CI job to run a profile that includes QA testing My plan is to fix it using option 3 > narayana-codeCoverage CI job is not producing any output > -------------------------------------------------------- > > Key: JBTM-2404 > URL: https://issues.jboss.org/browse/JBTM-2404 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/conso... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2369: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2404: -------------------------------------- Summary: narayana-codeCoverage CI job is not producing any output Key: JBTM-2404 URL: https://issues.jboss.org/browse/JBTM-2404 Project: JBoss Transaction Manager Issue Type: Bug Components: Configuration Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/conso... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2393?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2393: --------------------------------------- [~tomjenkinson], do we have analytics id etc.? > Add google analytics to the docs and narayana.io > ------------------------------------------------ > > Key: JBTM-2393 > URL: https://issues.jboss.org/browse/JBTM-2393 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > For the docs, see an example here: > https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-... > <transformerParameters> > <html.googleAnalyticsId>UA-XXXXXXX-X</html.googleAnalyticsId> > <html.googleTagManagerId>GTM-NJWS5L</html.googleTagManagerId> > <html.googleTagManagerChannel>MyProject</html.googleTagManagerChannel> > </transformerParameters> > We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2015