llvm dev - Feb 2020 - MLIR changes not sent to any mailing lists?

On Thu, Feb 6, 2020 at 11:24 AM Hans Wennborg <hans at chromium.org>
wrote:
>
> On Thu, Jan 30, 2020 at 4:04 PM Hans Wennborg <hans at chromium.org>
wrote:
> >
> > On Thu, Jan 30, 2020 at 9:50 AM Tom Stellard <tstellar at
redhat.com> wrote:
> > >
> > > On 01/30/2020 05:25 AM, Hans Wennborg via llvm-dev wrote:
> > > > For example, 7984b47401f7f36475619abf2ff02de3b5ff0481 does
not seem to
> > > > have made it to any mailing lists.
> > > >
> > > > This makes things harder for me as release manager, as those
changes
> > > > are essentially landing under the radar.
> > > >
> > > > Can we please make sure all commits that get pushed upstream
are sent
> > > > to a -commits list?
> > > >
> > > > Who is the right person to ask about this?
> > > >
> > >
> > > I'm looking into this.
> > >
> > > If you want to guarantee that you get every email.  I suggest you
> > > subscribe to
https://lists.llvm.org/cgi-bin/mailman/listinfo/all-commits
> > > which gets all the commit emails directly from github.
> >
> > I actually tried subscribing to that but it didn't work; maybe my
> > subscription request got stuck in moderation?
> >
> > It's also sub-optimal because it would duplicate all the emails
> > already getting sent to the regular -commits lists, but I'd rather
> > have too much email than too little.
>
> Here's another one that passed under my radar:
> 31fd112eb4a90600e0f340f19053e5715e92ec4c
>
> Any progress on getting these sent to llvm-commits or some other list?
Here's a non-MLIR commit that also wasn't sent to any list:
b3576f60ebc8f660afad8120a72473be47517573

>
> Here's a non-MLIR commit that also wasn't sent to any list:
> b3576f60ebc8f660afad8120a72473be47517573
>
I don't think that this is the same issue as the mlir commits.  This
particular one is likely due to the issue of non-ascii characters the
commit summary (author/comitter name in this case) causing some sort of
failure somewhere in the email pipeline, resulting in emails not turning up
on the list:
http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html
http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html
http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html
My guess is that somewhere on some server involved in sending the emails
there's a series of error messages hiding in a logfile about invalid ascii
characters from some software that isn't utf-8 aware.  I don't know who
owns that process though.

-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/61f2e59f/attachment.html>

On 02/06/2020 02:48 PM, Greg Bedwell wrote:
>     Here's a non-MLIR commit that also wasn't sent to any list:
>     b3576f60ebc8f660afad8120a72473be47517573
> 
> 
> I don't think that this is the same issue as the mlir commits.  This
particular one is likely due to the issue of non-ascii characters the commit
summary (author/comitter name in this case) causing some sort of failure
somewhere in the email pipeline, resulting in emails not turning up on the list:
> http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html 
> http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html 
> http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html 
> My guess is that somewhere on some server involved in sending the emails
there's a series of error messages hiding in a logfile about invalid ascii
characters from some software that isn't utf-8 aware.  I don't know who
owns that process though.
> 
You are correct, this second email is the same non-ascii issue.  I
think we have a fix now and hopefully we'll be able to deploy it soon.

-Tom
> -Greg
>