My only concern with this is the unfinished nature of the UBSAN work. Here
are some things left to do:
1. Make UBSAN builds work with FE and JDBC tests. These aren't UBSAN
unclean -- they plain don't work.
2. Make e2e, custom cluster, and BE tests UBSAN clean. This is in progress.
3. Make e2e
On Mon, Nov 12, 2018 at 1:21 PM Jim Apple wrote:
> I don't think I understand the "one stone" part - are you suggesting that
> we do UBSAN testing within a centos6 container?
>
Exactly. If we're doing multiple builds, we may as well be mutating other
variables to get coverage from them. (Here,
I don't think I understand the "one stone" part - are you suggesting that
we do UBSAN testing within a centos6 container?
On Mon, Nov 12, 2018 at 1:01 PM Philip Zeyliger wrote:
> Seems useful to me.
>
> If you're interested, we could kill multiple birds with one stone.
> Specifically, I'm also
I think about 7 working days will be enough to wrap up the doc work for 3.1:
- TOPN query option
- SHUTDOWN command
- TIMEZONE changes
- Minor release-related work
On Mon, Nov 12, 2018 at 9:17 AM, Zoltan Borok-Nagy
wrote:
> Hey Folks,
>
> It's been a week since we last talked about the 3.1.0
Seems useful to me.
If you're interested, we could kill multiple birds with one stone.
Specifically, I'm also interested in centos6/rh6 pre-merge testing. There
are a variety of ways to do so, including running with test-with-docker
stuff. I recognize it's more work, but happy to help if you want
