Boost logo

Boost Testing :

Subject: Re: [Boost-testing] macOS and Android test runners
From: Dmitry Moskalchuk (dm_at_[hidden])
Date: 2017-01-10 09:07:30

Hi Florent,

Thank you for pointing me to this. We (CrystaX) were not running aarch64
Android tests just because there was no stable aarch64 Android emulators
for long time and we were able run Boost tests only on real Android
devices. We were doing that occasionally but that was not really regular
testing solution, so we weren't able to fulfill Boost team requirements
for aarch64 architecture. Fortunately, things are improved with time and
now we have Android emulator for aarch64 stable enough so we can include
aarch64 to the list of target architectures for Boost testing. It's on
my task list actually, so I'm going to add it soon.

And, as always, primary way to contact us is - this link is specified in all our
runners information page on Boost regression results web site. Just
click on runner name (for example,
CrystaX-apilevel-19-armeabi-v7a-hard-gnu-libstdc++) and scroll to the
bottom of information section. Right before repositories listing you
will see two links, one of them is "Contact us". Feel free to send us
requests or questions, we'd be happy to help. And, of course, you can
ask here, in this mailing list - I monitor it and respond more-or-less

Dmitry Moskalchuk
On 10/01/2017 14:42, Florent Castelli wrote:
> Hello,
> While experimenting with Boost 1.63, I noticed some crashes on macOS
> with the Boost Context and Fiber libraries, and failure to compile
> Boost Context on Android Aarch64 with Clang.
> I was wondering why those crashes were not noticed by anyone, and thus
> I found the regression page and noticed the macOS runners are using
> Xcode7, which probably doesn't fit the requirements marked for the
> tests that would fail.
> So how could I contact Sandia, the owner of the machines, to kindly
> ask them to consider upgrading (or installing side-by-side) to the
> latest Xcode 8.2 to match what most people probably use and find more
> regressions?
> Also, Android devices now come in the aarch64 (arm64) flavor and I
> didn't see any coverage for it, it could have caught the problem
> before the release.
> Same issue as before, how can I contact the owner of the CrystaX
> Android test runners and ask them to add another runner for that one?
> Final note, both issues I faced where reported to Boost Context and
> fixed in their developer branch. All tests pass for me now!
> Regards,
> Florent
> _______________________________________________
> Boost-Testing mailing list
> Boost-Testing_at_[hidden]

Boost-testing list run by mbergal at