[JBoss JIRA] (JBTM-1016) Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code
8:41 a.m.
Paul Robinson created JBTM-1016:
-----------------------------------
Summary: Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI.
--
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
10:52 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1016:
-------------------------------------
Can it be integrated into the maven build at all?
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI.
--
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
5:22 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1016:
-------------------------------------
Not sure, I'll investigate.
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI.
--
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
4:08 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson reassigned JBTM-1016:
-----------------------------------
Assignee: Amos Feng (was: Paul Robinson)
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI.
--
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
4:08 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1016:
-------------------------------------
Needs to be integrated into the poms, even by an ant run call
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI.
--
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
5:38 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1016:
-------------------------------------
Can we make it fail the build if it detects the failure, before raising the pull req it
might be necessary to resolve some of the discovered errors.
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI.
--
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
6:13 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1016:
--------------------------------
Description:
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors?
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
was:
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI.
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors?
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
6:13 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1016:
--------------------------------
Comment: was deleted
(was: Can we make it fail the build if it detects the failure, before raising the pull req
it might be necessary to resolve some of the discovered errors.)
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors?
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
6:13 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1016:
--------------------------------
Comment: was deleted
(was: Can it be integrated into the maven build at all?)
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors?
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
6:13 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1016:
--------------------------------
Comment: was deleted
(was: Needs to be integrated into the poms, even by an ant run call)
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors?
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
6:13 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1016:
--------------------------------
Comment: was deleted
(was: Not sure, I'll investigate.)
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors?
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
6:15 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1016:
--------------------------------
Description:
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
was:
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors?
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
6:24 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Paul Robinson updated JBTM-1016:
--------------------------------
Component/s: XTS
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
12:25 p.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1016:
-------------------------------------
I think this applies to more than just XTS component
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
5:38 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1016:
-------------------------------------
Correct.
Amos, you need to search for all the Byteman scripts and make sure they are covered by
this.
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
11:01 p.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Amos Feng commented on JBTM-1016:
---------------------------------
I think we could do this check in scripts/hudson/narayana.sh and it needs export
BYTEMAN_HOME which install byteman on CI. also if
https://issues.jboss.org/browse/BYTEMAN-190 done, we could integrate it in maven build.
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
11:01 p.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Amos Feng edited comment on JBTM-1016 at 3/30/12 12:00 AM:
-----------------------------------------------------------
I think we could do this check in scripts/hudson/narayana.sh and it needs export
BYTEMAN_HOME which install byteman on CI. also if BYTEMAN-190 done, we could integrate it
in maven build.
was (Author: zhfeng):
I think we could do this check in scripts/hudson/narayana.sh and it needs export
BYTEMAN_HOME which install byteman on CI. also if
https://issues.jboss.org/browse/BYTEMAN-190 done, we could integrate it in maven build.
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
12:51 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1016:
-------------------------------------
I suggest we add a dependency on BYTEMAN-190 for this task. Amos, if you agree, can you
add the dependency please?
More Actions -> Link -> Depends on
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
2:32 a.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Paul Robinson updated JBTM-1016:
--------------------------------
Fix Version/s: 5.0.1.Final
(was: 5.0.0.M2)
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.1.Final
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
9:01 p.m.
[
https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin....
]
Amos Feng commented on JBTM-1016:
---------------------------------
we will defer it till when BYTEMAN-190 is resolved
Run bmcheck.sh regularly to spot inconsistencies between byteman
scripts and the code
-------------------------------------------------------------------------------------
Key: JBTM-1016
URL: https://issues.jboss.org/browse/JBTM-1016
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 5.0.1.Final
I've found many bugs in the XTS crash recovery tests that where due to changes being
made to the XTS code without updating the byteman scripts. The problem is that these
inconsistencies often go unnoticed when the tests run, until you notice a failure in the
test.
Can we run bmcheck as part of the maven build and make the build fail if it detects
errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
NOTE: Before raising the pull req it will be necessary to resolve any the discovered
errors.
--
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
4620
days inactive
4703
days old
jbossts-issues@lists.jboss.org
19 comments
3 participants
participants (3)
-
Amos Feng (JIRA) -
Paul Robinson (JIRA)
-
Tom Jenkinson (JIRA)