infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <>
Subject [jira] [Commented] (INFRA-9221) New issues@hive mailing list not getting JIRA commit messages
Date Fri, 02 Oct 2015 16:52:27 GMT


Mark Thomas commented on INFRA-9221:

I've been looking through the outgoing mail logs. There is a lot of noise from users with
invalid e-mail addresses. I have changed the e-mail address for these users to dev-null@a.o
and disabled the user. That should significantly reduce the noise and make it easier to see
if there is a pattern to the other failures.

I've also been lookign through the logs and I don't see anything that jumps out in terms of
a pattern. It looks like some form of intermittent network issue. The errors reported are
that the Jira host can't find mail.a.o or it connects but then times out reading the response
from mail.a.o.

> New issues@hive mailing list not getting JIRA commit messages
> -------------------------------------------------------------
>                 Key: INFRA-9221
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Lefty Leverenz
>            Priority: Critical
> The mailing list that was created by INFRA-9156 is missing some
commit comments and status changes for Hive JIRA issues.
> Example:  HIVE-9083 had a QA comment on March 2nd, followed by Ashutosh Chauhan's comment
"Committed to trunk. Thanks, Mithun!" and then a status change from Patch Available to Resolved
(Version 1.2.0, Resolution Fixed), followed by some changes to Affects Version/s.  But the
email list and archives only got the QA comment and Affects Version/s changes, skipping over
two messages.  See archives page
> Many other Hive JIRA issues missed commit messages, such as HIVE-9509, HIVE-9731, HIVE-9803,
and HIVE-9738.  But not all issues have this problem:  see HIVE-9785 and HIVE-9837 for examples
that do have their commit messages in the mailing list and archives.  (Fwiw, those commits
went to the CBO and LLAP branches, not trunk.)

This message was sent by Atlassian JIRA

View raw message