[jira] [Commented] (PROTON-214) Test proton_tests.messenger.MessengerTest.testSendBogus failed

[ https://issues.apache.org/jira/browse/PROTON-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570300#comment-13570300 ] Gordon Sim commented on PROTON-214: --- I actually think there is a race in the test logic,

[jira] [Updated] (PROTON-214) Test proton_tests.messenger.MessengerTest.testSendBogus failed

[ https://issues.apache.org/jira/browse/PROTON-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-214: -- Priority: Minor (was: Major) Test proton_tests.messenger.MessengerTest.testSendBogus failed

[jira] [Commented] (PROTON-214) Test proton_tests.messenger.MessengerTest.testSendBogus failed

[ https://issues.apache.org/jira/browse/PROTON-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570301#comment-13570301 ] Gordon Sim commented on PROTON-214: --- Downgraded the severity as I think this is

[jira] [Resolved] (PROTON-192) Implement Proton-JNI binding for proton-c

[ https://issues.apache.org/jira/browse/PROTON-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey resolved PROTON-192. -- Resolution: Fixed Fix Version/s: 0.4 merged to trunk Implement

[jira] [Closed] (PROTON-207) Modify release.sh to create single release artefact from top-level proton directory

[ https://issues.apache.org/jira/browse/PROTON-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey closed PROTON-207. Resolution: Duplicate Modify release.sh to create single release artefact from top-level

Re: Thoughts on proton performance and interoperability testing

I assume that such tests would be done peer-to-peer for right now. That would also give us a baseline for brokerless so that we can also compare various brokers from such a baseline. In such a test we should be able to configure, as we do today with qpid perf test, the number of subscribers

Re: Thoughts on proton performance and interoperability testing

On Mon, Feb 4, 2013 at 11:36 AM, Ken Giusti kgiu...@redhat.com wrote: I like what I'm hearing - here are some objectives based on what has been proposed so far: 1) Messenger-based scale and soak tests. These would be 'black-box' type tests that would mimic simple deployment scenarios,

Re: Additional components for language bindings?

We could use lables to denote which binding(s). The advantage here is that if multiple bindings expose the same bug, all we need to do is to add an additional label to the same JIRA. We currently use labels in the JMS client to denote sub categories (Ex addressing, exception-handling). The same

Re: Thoughts on proton performance and interoperability testing

Personally I feel like #3 is really a bit of a different animal from the others. It's a functional test rather than a performance test, and I'm not sure how possible/desirable it is to cover both with the same test code. Agreed - it isn't a perf/soak test. But it is on my mental glaring

proposal for docs to aid Proton adoption

I am working on some documentation, examples, c. to encourage easy adoption of Proton. I expect every one of you has had the experience of trying to use a new software package and not getting decent help doing so. I would like to do what I can to help delight any software person who decides to

Re: [jira] [Created] (PROTON-213) Reconcile C99 and C++ inconsistencies within proton

Dear Mr.Cliff Jansen, when do you plan to finish this work? -- View this message in context: http://qpid.2158936.n2.nabble.com/jira-Created-PROTON-213-Reconcile-C99-and-C-inconsistencies-within-proton-tp7587772p7588003.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.