April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1645: ------------------------------------- Take this example: !XTS !QA_JTA The XTS and QA_JTA jobs will still run, but they will detect the presence of that string in the PR description and then do nothing. The problem is that to the casual observer, it would look like these tests passed in CI, when actually they where skipped. Not a major problem as it only applies to PR jobs, and we don't pay too much attention to the history of those. > Allow pull requests to configure some parameters in scripts/hudson/narayana.sh > ------------------------------------------------------------------------------ > > Key: JBTM-1645 > URL: https://issues.jboss.org/browse/JBTM-1645 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the pull description has something like this: > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests] > We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1565) Allow callback server to open on a random port and override from the system property

by Crispin Boylan (JIRA)

[ https://issues.jboss.org/browse/JBTM-1565?page=com.atlassian.jira.plugin.... ] Crispin Boylan edited comment on JBTM-1565 at 4/25/13 9:31 AM: --------------------------------------------------------------- if you dont already intend this, it would be nice to extend this so that if no -p is specified on a machine-ref arguments line and socketserver is 0 then they also assign themselves a random port. was (Author: crisb): if you dont already indent this, it would be nice to extend this so that if no -p is specified on a machine-ref arguments line and socketserver is 0 then they also assign themselves a random port. > Allow callback server to open on a random port and override from the system property > ------------------------------------------------------------------------------------ > > Key: JBTM-1565 > URL: https://issues.jboss.org/browse/JBTM-1565 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: BlackTie > Affects Versions: 5.0.0.M2 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M3 > > > currently the client can only use the port defined for <SOCKETSERVER> in the btconfig.xml and multi clients can not run together. > we need to allow callback server to open the random port when <SOCKETSERVER PORT="0"> or a range <SOCKETSERVER "12340-12350"> and they could be overridden by socketserver_port and socketserver_host environment variables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1645: ------------------------------------- Lets go with that > Allow pull requests to configure some parameters in scripts/hudson/narayana.sh > ------------------------------------------------------------------------------ > > Key: JBTM-1645 > URL: https://issues.jboss.org/browse/JBTM-1645 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the pull description has something like this: > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests] > We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1653) narayana Jenkins job is allowing lastSuccessfulbuild to expire

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1653?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1653: ------------------------------------- I've also got this job to try reproduce the expiry issue: http://172.17.131.2/job/paul-test-multi/ If this deletes the last succesfulbuild tomorrow, then we have reproduced the bug. In which cae I can easily report it to the Jenkins team. > narayana Jenkins job is allowing lastSuccessfulbuild to expire > -------------------------------------------------------------- > > Key: JBTM-1653 > URL: https://issues.jboss.org/browse/JBTM-1653 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.5, 5.0.0.M3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > the narayana multi-config job is supposed to save at least one successful build, but it is allowing it to expire. It seems like a bug, but I can't find a reference to it on Google. > The problem is that all jobs that use these artefacts will now fail as they can no longer find them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1653) narayana Jenkins job is allowing lastSuccessfulbuild to expire

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1653?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1653: ------------------------------------- Looks like saving a fixed number of builds does what we want. Changed the multi-jobs to save 5 jobs, rather than expire after 3d. Lets see how we get on. > narayana Jenkins job is allowing lastSuccessfulbuild to expire > -------------------------------------------------------------- > > Key: JBTM-1653 > URL: https://issues.jboss.org/browse/JBTM-1653 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.5, 5.0.0.M3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > the narayana multi-config job is supposed to save at least one successful build, but it is allowing it to expire. It seems like a bug, but I can't find a reference to it on Google. > The problem is that all jobs that use these artefacts will now fail as they can no longer find them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1654) Multi jobs are not archiving the lastSuccessfullArtifacts

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1654: ----------------------------------- Summary: Multi jobs are not archiving the lastSuccessfullArtifacts Key: JBTM-1654 URL: https://issues.jboss.org/browse/JBTM-1654 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Paul Robinson Priority: Critical Fix For: 4.17.5, 5.0.0.M3 Downstream projects (e.g. quickstarts, blacktie) are affected. Is it possible that the Archive Artifacts are no longer the correct path now there is a matrix in play? Perhaps we can scp the files to albany at the end of the build? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1654) Multi jobs are not archiving the lastSuccessfullArtifacts

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1654?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1654. --------------------------------- Resolution: Duplicate Issue JBTM-1653 > Multi jobs are not archiving the lastSuccessfullArtifacts > --------------------------------------------------------- > > Key: JBTM-1654 > URL: https://issues.jboss.org/browse/JBTM-1654 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 4.17.5, 5.0.0.M3 > > > Downstream projects (e.g. quickstarts, blacktie) are affected. Is it possible that the Archive Artifacts are no longer the correct path now there is a matrix in play? > Perhaps we can scp the files to albany at the end of the build? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1653) narayana Jenkins job is allowing lastSuccessfulbuild to expire

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1653?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1653: ------------------------------------- As a work-around I've set the expiry to 10d. We need to keep an eye on this to make sure we don't fill up the slave disks. In particular, Haverstraw is pretty tight on space. > narayana Jenkins job is allowing lastSuccessfulbuild to expire > -------------------------------------------------------------- > > Key: JBTM-1653 > URL: https://issues.jboss.org/browse/JBTM-1653 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.5, 5.0.0.M3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > the narayana multi-config job is supposed to save at least one successful build, but it is allowing it to expire. It seems like a bug, but I can't find a reference to it on Google. > The problem is that all jobs that use these artefacts will now fail as they can no longer find them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1653) narayana Jenkins job is allowing lastSuccessfulbuild to expire

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1653: ----------------------------------- Summary: narayana Jenkins job is allowing lastSuccessfulbuild to expire Key: JBTM-1653 URL: https://issues.jboss.org/browse/JBTM-1653 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.17.5, 5.0.0.M3 the narayana multi-config job is supposed to save at least one successful build, but it is allowing it to expire. It seems like a bug, but I can't find a reference to it on Google. The problem is that all jobs that use these artefacts will now fail as they can no longer find them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1601) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1601?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1601: -------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb > -------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1601 > URL: https://issues.jboss.org/browse/JBTM-1601 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.3, 5.0.0.M2 > Reporter: Ondřej Chaloupka > Assignee: Michael Musgrove > > I'm hitting an issue on qa tests for windows machines. I'm currently testing EAP 6.1.0.ER3. > Testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 is failing when it's run on windows machines. It does not matter which JDK is used. It fails on 4.17 branch and master as well. > This happens for jacorb. > The fails consistently occur on 5 tests from the testcase - that are from CrashRecovery02_2_Test26 till CrashRecovery02_2_Test30. > All of them throw assertion: > {quote} > junit.framework.AssertionFailedError: task client1 printed Failed. > {quote} > These details apply to test CrashRecovery02_2_Test27: > The client implementation is org.jboss.jbossts.qa.CrashRecovery02.Client02a and the fail comes from line 114 (branch 4.17). > {code} > correct = correct && (resourceTrace1 == ResourceTrace.ResourceTraceCommit); > {code} > Where the value of resourceTrace1 is {{ResourceTraceNone}}. > I didn't get with investigation further so far. > Steps for reproducing could be handy (using narayana.sh script first): > 1. export NARAYANA_BUILD=0 > export NARAYANA_TESTS=0 > export CP_NARAYANA_AS=0 > export AS_BUILD=0 > export XTS_AS_TESTS=0 > export TXF_TESTS=0 > export XTS_TESTS=0 > export txbridge=0 > export QA_TESTS=1 > export SUN_ORB=0 > export QA_TARGET=test > export QA_PROFILE="-Dtest=crashrecovery02_2" > export WORKSPACE=$PWD > 2. run naryana.sh - there was problem with paths for me so the command looks like this at the end > {quote} > sh scripts/hudson/narayana.sh -Demma.jar.location=c:\\tmp\\ochaloup\\ext -Demma.enabled=false -Dorson.jar.location=\\tmp\\ochaloup\\ext > {quote} > You can check whole stacktrace from job on jenkins: > - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT... > - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT... > Do you think that you could check this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2013