May 2013 - jbossts-issues - Jboss List Archives

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1673?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1673: --------------------------------- It looks like valgrind-3.5.0 crash {code} valgrind: m_scheduler/scheduler.c:1199 (vgPlain_scheduler): the 'impossible' happened. valgrind: VG_(scheduler), phase 3: run_innerloop detected host state invariant failure ==16048== at 0x38029D5C: report_and_quit (m_libcassert.c:145) ==16048== by 0x3802A032: vgPlain_assert_fail (m_libcassert.c:217) ==16048== by 0x38061E8B: vgPlain_scheduler (scheduler.c:1197) ==16048== by 0x3808629E: run_a_thread_NORETURN (syswrap-linux.c:91) {code} > Build failure > ------------- > > Key: JBTM-1673 > URL: https://issues.jboss.org/browse/JBTM-1673 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1492/console -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1659) BlackTie build fails when valgrind is not on

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1659?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1659: ---------------------------- Status: Closed (was: Pull Request Sent) Resolution: Duplicate Issue duplicate issue JBTM-1650 > BlackTie build fails when valgrind is not on > -------------------------------------------- > > Key: JBTM-1659 > URL: https://issues.jboss.org/browse/JBTM-1659 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux32/925/ > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1489/ -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1650) SIGPIPE as test_tprecv_sendonly tearDown() is calling tpdiscon()

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1650?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1650: ---------------------------- Summary: SIGPIPE as test_tprecv_sendonly tearDown() is calling tpdiscon() (was: SIGPIPE as xatmi test tearDown() is calling tpdiscon()) > SIGPIPE as test_tprecv_sendonly tearDown() is calling tpdiscon() > ----------------------------------------------------------------- > > Key: JBTM-1650 > URL: https://issues.jboss.org/browse/JBTM-1650 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > ==7024== > ==7024== Process terminating with default action of signal 13 (SIGPIPE) > ==7024== at 0x363040E5CD: ??? (in /lib64/libpthread-2.14.90.so) > ==7024== by 0x7044D56: apr_socket_send (in /usr/lib64/libapr-1.so.0.4.6) > ==7024== by 0x76FF688: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:287) > ==7024== by 0x76FF878: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:325) > ==7024== by 0x76FA50F: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:519) > ==7024== by 0x92B629D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==7024== by 0x92B66B8: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:182) > ==7024== by 0x92C1051: tpdiscon (XATMIc.cxx:1219) > ==7024== by 0x44416D: TestTPRecv::tearDown() (TestTPRecv.cxx:63) > ==7024== by 0x445584: CppUnit::TestCaller<TestTPRecv>::tearDown() (TestCaller.h:182) > ==7024== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==7024== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==7024== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==7024== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==7024== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==7024== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==7024== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==7024== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==7024== by 0x4E2043: main (TestRunner.cxx:27) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1650) SIGPIPE as xatmi test tearDown() is calling tpdiscon()

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1650?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1650: --------------------------------- ok, I reviewed the pulls-blacktie-windows2008/155 logs and it failed on tpsend() as the fix to setLastEvent when socket has been close happened before tpsend(). I'm trying to find a better solution. > SIGPIPE as xatmi test tearDown() is calling tpdiscon() > ------------------------------------------------------ > > Key: JBTM-1650 > URL: https://issues.jboss.org/browse/JBTM-1650 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > ==7024== > ==7024== Process terminating with default action of signal 13 (SIGPIPE) > ==7024== at 0x363040E5CD: ??? (in /lib64/libpthread-2.14.90.so) > ==7024== by 0x7044D56: apr_socket_send (in /usr/lib64/libapr-1.so.0.4.6) > ==7024== by 0x76FF688: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:287) > ==7024== by 0x76FF878: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:325) > ==7024== by 0x76FA50F: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:519) > ==7024== by 0x92B629D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==7024== by 0x92B66B8: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:182) > ==7024== by 0x92C1051: tpdiscon (XATMIc.cxx:1219) > ==7024== by 0x44416D: TestTPRecv::tearDown() (TestTPRecv.cxx:63) > ==7024== by 0x445584: CppUnit::TestCaller<TestTPRecv>::tearDown() (TestCaller.h:182) > ==7024== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==7024== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==7024== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==7024== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==7024== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==7024== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==7024== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==7024== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==7024== by 0x4E2043: main (TestRunner.cxx:27) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1659) BlackTie build fails when valgrind is not on

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1659?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1659: --------------------------------- Tom, I'm sure the two builds failed with SIGPIPE when tpdiscon(). so it looks like the same issue of JBTM-1650 > BlackTie build fails when valgrind is not on > -------------------------------------------- > > Key: JBTM-1659 > URL: https://issues.jboss.org/browse/JBTM-1659 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux32/925/ > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1489/ -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1650) SIGPIPE as xatmi test tearDown() is calling tpdiscon()

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1650?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1650: ------------------------------------- Ups, it must have rolled off the end, feel free to resolve then as it was the only example of the failure.... > SIGPIPE as xatmi test tearDown() is calling tpdiscon() > ------------------------------------------------------ > > Key: JBTM-1650 > URL: https://issues.jboss.org/browse/JBTM-1650 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > ==7024== > ==7024== Process terminating with default action of signal 13 (SIGPIPE) > ==7024== at 0x363040E5CD: ??? (in /lib64/libpthread-2.14.90.so) > ==7024== by 0x7044D56: apr_socket_send (in /usr/lib64/libapr-1.so.0.4.6) > ==7024== by 0x76FF688: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:287) > ==7024== by 0x76FF878: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:325) > ==7024== by 0x76FA50F: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:519) > ==7024== by 0x92B629D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==7024== by 0x92B66B8: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:182) > ==7024== by 0x92C1051: tpdiscon (XATMIc.cxx:1219) > ==7024== by 0x44416D: TestTPRecv::tearDown() (TestTPRecv.cxx:63) > ==7024== by 0x445584: CppUnit::TestCaller<TestTPRecv>::tearDown() (TestCaller.h:182) > ==7024== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==7024== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==7024== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==7024== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==7024== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==7024== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==7024== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==7024== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==7024== by 0x4E2043: main (TestRunner.cxx:27) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1650) SIGPIPE as xatmi test tearDown() is calling tpdiscon()

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1650?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1650: --------------------------------- btny-pulls-blacktie-linux64/151 is not available. > SIGPIPE as xatmi test tearDown() is calling tpdiscon() > ------------------------------------------------------ > > Key: JBTM-1650 > URL: https://issues.jboss.org/browse/JBTM-1650 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > ==7024== > ==7024== Process terminating with default action of signal 13 (SIGPIPE) > ==7024== at 0x363040E5CD: ??? (in /lib64/libpthread-2.14.90.so) > ==7024== by 0x7044D56: apr_socket_send (in /usr/lib64/libapr-1.so.0.4.6) > ==7024== by 0x76FF688: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:287) > ==7024== by 0x76FF878: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:325) > ==7024== by 0x76FA50F: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:519) > ==7024== by 0x92B629D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==7024== by 0x92B66B8: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:182) > ==7024== by 0x92C1051: tpdiscon (XATMIc.cxx:1219) > ==7024== by 0x44416D: TestTPRecv::tearDown() (TestTPRecv.cxx:63) > ==7024== by 0x445584: CppUnit::TestCaller<TestTPRecv>::tearDown() (TestCaller.h:182) > ==7024== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==7024== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==7024== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==7024== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==7024== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==7024== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==7024== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==7024== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==7024== by 0x4E2043: main (TestRunner.cxx:27) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1623) jboss-as is killed by Out of Memeory

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1623?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1623: -------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Tom Jenkinson (was: Amos Feng) Resolution: Done Resolved by lowering memory > jboss-as is killed by Out of Memeory > ------------------------------------ > > Key: JBTM-1623 > URL: https://issues.jboss.org/browse/JBTM-1623 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.0.0.M3 > > Attachments: consoleText.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1466 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1659) BlackTie build fails when valgrind is not on

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1659?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1659: ------------------------------------- I have added pull checking jobs for all 4 linux combos and raised the PR to check what happens with valgrind disabled > BlackTie build fails when valgrind is not on > -------------------------------------------- > > Key: JBTM-1659 > URL: https://issues.jboss.org/browse/JBTM-1659 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux32/925/ > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1489/ -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1659) BlackTie build fails when valgrind is not on

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1659?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1659: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/blacktie/pull/45 > BlackTie build fails when valgrind is not on > -------------------------------------------- > > Key: JBTM-1659 > URL: https://issues.jboss.org/browse/JBTM-1659 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux32/925/ > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1489/ -- 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, 4 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 May 2013