Hi Andrew,
> On Wed, 2009-07-01 at 11:43 -0400, Steve Huston wrote:
> > Hi folks,
> >
> > As part of migrating the Qpid build system to Cmake, I've
> also set up
> > a Cdash dashboard to hold build results. The dashboard gives a
good
> > overall view of the health of the builds; can keep track o
On Wed, 2009-07-01 at 11:43 -0400, Steve Huston wrote:
> Hi folks,
>
> As part of migrating the Qpid build system to Cmake, I've also set up
> a Cdash dashboard to hold build results. The dashboard gives a good
> overall view of the health of the builds; can keep track of which
> builds are workin
Hi folks,
As part of migrating the Qpid build system to Cmake, I've also set up
a Cdash dashboard to hold build results. The dashboard gives a good
overall view of the health of the builds; can keep track of which
builds are working and help show some history when they don't.
The dashboard is ava
[
https://issues.apache.org/jira/browse/QPID-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-1963.
--
Resolution: Fixed
> segfault in TopicExchange::isBound()
>
>
>
On Tue, Jun 30, 2009 at 11:52 AM, Marnie
McCormack wrote:
> Fortunately or unfortunately, It fails pretty regularly so I'm betting you
> get to raise the JIRA !
I'm re-enabling this. Yell if you see it fail please. :)
- Aidan
--
Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.
[
https://issues.apache.org/jira/browse/QPID-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated QPID-1963:
-
Attachment: TopicExchange.patch
Patch represeting the fix, now committed on trunk as r790164.
> segfault
Hi there!
Just an update, since two patches - one by aconway (789726),
the other (and equally important) by tross (789773) - I can
already make distcheck when bootstrapping using last autotools
on non-RHEL Linux distribution. Thanks for fixing that!
Not wanting to raise following much, but I ha
[
https://issues.apache.org/jira/browse/QPID-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aidan Skinner resolved QPID-1964.
-
Resolution: Fixed
Fix Version/s: (was: 0.5)
0.6
Assignee: Ai
Aidan Skinner wrote:
On Mon, Jun 29, 2009 at 8:36 PM, Bryan Kearney wrote:
Taking what Aiden suggested. Here is a first cut at ivy integration. What
this does is:
1) Require that every module have an ivy.xml file which is contains all the
dependencies.
2) Defines a depVersions.properties file
On Mon, Jun 29, 2009 at 2:30 PM, Ted Ross wrote:
> I would like to add a new m4 macro definition (AC_PROG_SWIG) to the CPP
> build directory but it has the following license text. I understand that
> GPLv2 is not compatible with the Apache license but I don't know if the
> stated exceptions make i
rsprin...@mail.etinternational.com wrote:
All,
We've been using Qpid M4 and 0.5 internally, both with C++, and have been
seeing occasional segfaults within the broker. They all seem to occur
inside TopicExchange::isBound() (the one with 3 parameters, not 2).
Looking at the access patterns in th
bin/release.sh --help does not work
---
Key: QPID-1964
URL: https://issues.apache.org/jira/browse/QPID-1964
Project: Qpid
Issue Type: Bug
Components: Build Tools
Affects Versions: M4
[
https://issues.apache.org/jira/browse/QPID-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Sarenik updated QPID-1964:
--
Attachment: 0001-Make-release.sh-help-work.patch
Patch
> bin/release.sh --help does not work
>
segfault in TopicExchange::isBound()
Key: QPID-1963
URL: https://issues.apache.org/jira/browse/QPID-1963
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.5
On Mon, Jun 29, 2009 at 8:36 PM, Bryan Kearney wrote:
> Taking what Aiden suggested. Here is a first cut at ivy integration. What
> this does is:
>
> 1) Require that every module have an ivy.xml file which is contains all the
> dependencies.
> 2) Defines a depVersions.properties file at the root p
15 matches
Mail list logo