t; > Historically I think it has been a little flakey. Though I haven't
> > > personally had it fail locally.
> > >
> > > Unless someone with more of a clue about these bits indicates
> > > otherwise, I think we will be proceeding. I'll leave th
id-proton/c/tests/fdlimit.py", line 77,
in test_fd_limit_broker
6: self.assertNotEqual(sender.poll(), 0)
6: AssertionError: 0 == 0
6:
6: --
6: Ran 1 test in 2.162s
6:
6: FAILED (failures=1)
Test #6: c-fdlimit-tests ..***Failed2
Has anyone else been testing with python 3.10? I see that we specify python
3.6+ as per:
-- Found Python: /usr/bin/python3.10 (found suitable version "3.10.0", minimum
required is "3.6") found components: Interpreter Development Development.Module
Development.Embed
but on Fedora 34 with python
-0
tl;dr - c-fdlimit-test failed on Fedora 34 with both gcc and clang, likely
due to default ulimit settings. As this can easily be configured around its
not great but not a blocker either.
Tested on Fedora 34
- Lenovo T450s, GCC 9.3.1, 2c4t
-- ctest full pass consistently, default build options
+1
Built and tested on macOS 10.14.6 with
-DBUILD_RUBY=OFF
AppleClang 10.0.1.10010046
go version go1.15.2 darwin/amd64
python 3.7.9
ctest -VV all passed 3 times (no c-threadercizer configured atm)
ran examples broker, *receive and *send for c, cpp, and go without issue.
On Tue, Nov 17, 2020 at
for the vote
> tally itself to go another way should folks actually test it and/or
> want to vote negatively. Which is why the vote has remained open,
> longer than needed, to give folks more opportunity to provide such
> feedback (and/or changes that warrant an RC2).
>
> Robbie
>
>
0
To follow up on Chuck's testing I had originally observed the threaderciser
issue on macOS 10.14 in my first round of testing a few days ago when I ran
4 sets of tests and all had only 1 failure - c_threaderciser.
In retesting this morning on the same platform with the same build with no
reboots
p'
[1]. May or may not be related to PROTON-1636 - 'Fairly Consistent (but
intermittent) hangs in ruby-example-test/ruby-test-container using Travis
CI' [2]
Roddie Kieley
---
[1] - https://issues.apache.org/jira/browse/PROTON-2213
[2] - https://issues.apache.org/jira/browse/PROTON-1
+1
macOS 10.14.6
* built without ruby and with go
* ran ctest -VV 100% successfully
* ran c broker receive and send examples
* ran cpp broker helloworld simple_recv simple_send
* ran go example_test
macOS 10.11.6
* built without ruby and without go
* ran ctest -VV 100% successfully
* ran c broker
+1
Fedora 29
- checkout 0.29.0-rc1
- cmake ../qpid-proton
- ctest -VV
- 100% tests passed
- ran all c examples
- ran send/receive cpp examples
OSX 10.11.6 XCode 7.3.1
- checkout 0.29.0-rc1
- cmake -DCMAKE_OSX_DEPLOYMENT_TARGET=10.11 -DBUILD_RUBY=NO -DBUILD_GO=NO
-DRUNTIME_CHECK= ../qpid-proton
-
+1
Cloned the repo from gitbox, checked out 0.27.1-rc1
Fedora 29
- Built using via cmake ../qpid-proton
- Ran tests via ctest -VV; all tests ran passed
OSX 10.11.6 w/Xcode 7.3.1
- As previously built using
ccmake -DCMAKE_OSX_DEPLOYMENT_TARGET=10.11 -DBUILD_RUBY=NO ../qpid-proton
as per travis setu
+1
I checked out the 0.27.0-rc1 tag on a Fedora 29 box
- default cmake ../qpid-proton && cmake --build . && ctest -VV
- no failures
- ran all c examples
- ran all cpp examples w/exception of service_bus
I checked out the 0.27.0-rc1 tag on a 10.11.6 OSX box with Xcode 7.3.1
- cmake -DCMAKE_OSX_DEP
:02 PM Rob Godfrey wrote:
> Welcome Roddie - good to have you here!
>
> -- Rob
>
> On Tue, 27 Nov 2018 at 17:18, Oleksandr Rudyy wrote:
>
> > Welcome, Roddie!
> > On Tue, 27 Nov 2018 at 14:38, Robbie Gemmell
> > wrote:
> > >
> > > Th
+1 (advisory)
On OSX 10.11.6:
- Updated MacPorts Portfile to pull 0.24.0-rc1 tag; built and installed
-- built and ran installed c examples
-- built and ran installed cpp examples
- cloned the Apache Github qpid-proton repository, checked out the tag
0.24.0-rc1
-- Generated and built via Makefiles
+1 (advisory)
On OSX 10.11.6:
- Updated MacPorts Portfile to pull 0.22.0-rc1 tag; built and installed
-- built and ran installed c examples
-- built and ran installed cpp examples
- Cloned the Apache Github qpid-proton repository, checked out the tag
0.22.0-rc1
-- Generated and built via Makefiles
+1 (advisory)
- checked out the tag 0.21.0-rc1
- Built on OSX 10.11.6 w/Xcode 7.3.1 command line tools without ruby or
valgrind
-- Tested with go-test failure related to open PROTON-1695 and potentially
closed PROTON-1655
- Built and Installed using updated Portfile for MacPorts net/qpid-proton
--
com/_/python/
> `
>
> On Thu, Jan 25, 2018 at 7:01 PM Roddie Kieley wrote:
>
> > Hi, while I have not run into your specific problem I had previously run
> > into some issues when utilizing the cyrus sasl implementation on OSX
> which
> > I documented via PROTON-16
Hi, while I have not run into your specific problem I had previously run
into some issues when utilizing the cyrus sasl implementation on OSX which
I documented via PROTON-1695 - '[OSX] Cyrus SASL plugins do not load
leading to missing mechanisms' [1]. It appears that you are utilizing the
sasl pla
While I haven't built on debian/ubuntu in a while you'd want the cyrus
libraries and extra plugins installed which should be something like this:
# apt-get install libsasl2 sasl2-bin libsasl2-modules
Which looks like is the case based on the dpkg command. On some operating
systems the 'sasl2-b
Hi. If I recall correctly you'd also need to allow insecure mechanisms via
the connection_options [1]:
"
/// Force the enabling of SASL mechanisms that disclose cleartext
/// passwords over the connection. By default, such mechanisms
/// are disabled.
PN_CPP_EXTERN connection_options&
Hi Venkat, there are indeed issues on Mac OS X with the mutex
initialization and
destruction as you indicate. A pull request with the required fixes,
including the
update below is located here [1] which was generated from the work on
PROTON-522 and commented upon at [2].
While the changes have not
> On 01/10/17 04:06, Roddie Kieley wrote:
>
>> Looks like the MacPorts install of cyrus-sasl doesn't have plain,
>> discovered
>> this after noting that all the sasl related tests in python failed as
>> well.
>>
>> saslauthd 2.1.26
>> authent
Looks like the MacPorts install of cyrus-sasl doesn't have plain, discovered
this after noting that all the sasl related tests in python failed as well.
saslauthd 2.1.26
authentication mechanisms: getpwent kerberos5 pam rimap
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2
Hi folks. I'm doing some work on PROTON-522 to ensure proton-c works well
on OSX and I'm seeing failures in the TestAuthPlain go-test. With
PN_TRACE_FRM=1 and PN_TRACE_EVT=1 I'm seeing the following:
11: === RUN TestAuthPlain
11: [0x4706330]:ConnectionInit
11: [0x4706330]:ConnectionLocalOpen
11:
Forgot one important part, before running cmake as mentioned with
-DCMAKE_TOOLCHAIN_FILE you'll want to use the included python setup.py
script in the bin directory as per:
[rkieley@i5t450s qpid-proton]$ python bin/setup.py emscripten
script_dir is /home/rkieley/LocalProjects/usx/research/qpid-pr
Hi folks. Recently I had a need for an emscripten build of proton-c and the
existing implementation was a little dusty, so I made a small update for my
needs over at github [1]. In particular it was based on some MIT licensed
work by Andre Weissflog also at github here [2] and here [3], but updated
26 matches
Mail list logo
