[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1199: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-java6/1237/ Seemed to start happenening for no obvious reason - I guess it is an underlying change in AS/arq? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1199: ------------------------------------- To replicate: git remote add tomjenkinson git://github.com/tomjenkinson/narayana.git git fetch tomjenkinson git checkout crash_rec_experiments ./scripts/hudson/narayana.sh -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1199: ------------------------------------- The only way I have found to check an old version of the AS (but still having our commits from 5_BRANCH) is as follows: 0. cd jboss-as 1. git checkout 5_BRANCH (assumes you haven't checked this out yet, if you already have this such as by having ran scripts/hudson/narayana.sh git checkout master git branch -D 5-BRANCH git checkout 5_BRANCH) 2. git pull --rebase --ff-only upstream master (to get up to date) 3. Go to: https://github.com/jbossas/jboss-as/commits/master and find a commit you want to check against, e.g one from July 3rd when build was still working: https://github.com/jbossas/jboss-as/commit/55fca1401f399591d009c211205f2e... 4. Use this in a git rebase: git rebase -i 55fca1401f399591d009c211205f2e6ef94f876b^ (you need the ^ to include that commit in the rebase) 5. delete all the commits after that commit (dd in vi) but leave our commits in at the bottom of the rebase 6. You will get a rebase issue on the first one, simply open pom.xml and remove the jbossjts part of pom.xml which came from HEAD -- grep in pom.xml for an "=" sign), then: git add pom.xml git rebase --continue 7. You should now be able to build the AS as per that commit but with our commits on top MAVEN_OPTS=-XX:MaxPermSize=256m ./build.sh "$@" clean install -DskipTests 8. cd ../ 9. export JBOSS_HOME=${WORKSPACE}/jboss-as/build/target/`ls -1 ${WORKSPACE}/jboss-as/build/target | grep jboss-as` 10. ./build.sh -f XTS/localjunit/pom.xml --projects xtstest,crash-recovery-tests -Parq "$@" clean install -Dtest=TestATCrashDuringCommit#MultiParticipantPrepareAndCommitTest After you have verified that that version works, try a later revision of AS, however you will need to delete your local branch first! This will be tedious, so to reduce the number of checks, the first thing to do is identify the day where a commit was added that broke our build, then use a binary tree search style to cut down the options on that day. Suggested commits to try: https://github.com/jbossas/jboss-as/commit/2e2f1a7dfcebebb282987d2d8e2df4... https://github.com/jbossas/jboss-as/commit/f2d65c311d67c61d953bd17c079f41... Tom -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1199: ------------------------------------- PASSED = https://github.com/jbossas/jboss-as/commit/2e2f1a7dfcebebb282987d2d8e2df4..., that narrows it down to a commit that was merged in on Jul 06. Tom -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1199: ------------------------------------- FAILED = https://github.com/jbossas/jboss-as/commit/4ff358d1b79d546281bff9a4d70f8e... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1199: ------------------------------------- PASSED = https://github.com/jbossas/jboss-as/commit/da4db1614d6e7ff1a37fbaac4ecab6... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1199: ----------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) Amos, please can you investigate why https://github.com/jbossas/jboss-as/commit/435c862b9514bfcf0a036bb2b916ac... would stop the XTS crash recovery tests from working? I noticed somethings to do with "Reload" perhaps AS7 has some behaviour that reloads the server automatically now? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1199. --------------------------------- Resolution: Done This build got past XTS CR and Txbridge: http://172.17.131.2/job/narayana-pulls/75/console -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1199: -------------------------------- Fix Version/s: 4.16.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1199: -------------------------------- Fix Version/s: 4.16.5 (was: 5.0.0.M2) -- 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

[ https://issues.jboss.org/browse/JBTM-1199?page=com.atlassian.jira.plugin.... ] Paul Robinson closed JBTM-1199. ------------------------------- -- 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