You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Yusaku Sako <yu...@hortonworks.com> on 2014/10/14 18:16:56 UTC
Let's pay special attention to post-commit Jenkins UT failure reports
Hi all,
Unit tests on branch-1.7.0 have been failing since 10/11 until it was fixed
recently via https://issues.apache.org/jira/browse/AMBARI-7774.
Branch 1.7.0 Jenkins jobs:
https://builds.apache.org/job/Ambari-branch-1.7.0/
Note that builds #63 through #86 all reported UT failures consecutively.
This is a situation that we really need to avoid on trunk or any branch,
but especially for a release branch.
There is the patch verification job (aka "Hadoop QA"), but there are also
post-commit jobs that report to the JIRA whether a UT failure occurred or
not.
What seems to be happening is that the patch verification job works against
trunk and report OK, but when patches are committed to branch-1.7.0, the
post-commit UT job is catching UT failures specifically for the branch and
reporting back to the JIRAs that potentially caused the failure.
However, it seems that these reports are largely being ignored.
If you are the contributor/committer for a JIRA that has a post-commit
failure report, please take appropriate action.
Also, I'd like to propose incorporating some sort of post-commit UT failure
report handling into our Dev Process. Thoughts?
Yusaku
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Let's pay special attention to post-commit Jenkins UT failure reports
Posted by Yusaku Sako <yu...@hortonworks.com>.
The post-commit hook reports back to all the JIRAs that were newly
incorporated in the build; builds are done on commits that happened within
the last 15 minutes, so multiple JIRAs can be associated with a single
build.
The Failure report shows the status (SUCCESS or FAILURE), which tests
failed, and a link to the associated build job. The build job shows all
the JIRAs/commits involved in the build.
Yusaku
On Tue, Oct 14, 2014 at 9:36 AM, Erin Boyd <eb...@redhat.com> wrote:
> I think this is a great idea.
> Does the process report back to the JIRA somehow the failure in the build?
> Is there an automated means by reporting which JIRAs are causing the
> failures?
> Erin
>
>
> ----- Original Message -----
> From: "Yusaku Sako" <yu...@hortonworks.com>
> To: dev@ambari.apache.org
> Sent: Tuesday, October 14, 2014 10:16:56 AM
> Subject: Let's pay special attention to post-commit Jenkins UT failure
> reports
>
> Hi all,
>
> Unit tests on branch-1.7.0 have been failing since 10/11 until it was fixed
> recently via https://issues.apache.org/jira/browse/AMBARI-7774.
>
> Branch 1.7.0 Jenkins jobs:
> https://builds.apache.org/job/Ambari-branch-1.7.0/
>
> Note that builds #63 through #86 all reported UT failures consecutively.
> This is a situation that we really need to avoid on trunk or any branch,
> but especially for a release branch.
>
> There is the patch verification job (aka "Hadoop QA"), but there are also
> post-commit jobs that report to the JIRA whether a UT failure occurred or
> not.
> What seems to be happening is that the patch verification job works against
> trunk and report OK, but when patches are committed to branch-1.7.0, the
> post-commit UT job is catching UT failures specifically for the branch and
> reporting back to the JIRAs that potentially caused the failure.
> However, it seems that these reports are largely being ignored.
> If you are the contributor/committer for a JIRA that has a post-commit
> failure report, please take appropriate action.
>
> Also, I'd like to propose incorporating some sort of post-commit UT failure
> report handling into our Dev Process. Thoughts?
>
> Yusaku
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Let's pay special attention to post-commit Jenkins UT failure
reports
Posted by Erin Boyd <eb...@redhat.com>.
I think this is a great idea.
Does the process report back to the JIRA somehow the failure in the build?
Is there an automated means by reporting which JIRAs are causing the failures?
Erin
----- Original Message -----
From: "Yusaku Sako" <yu...@hortonworks.com>
To: dev@ambari.apache.org
Sent: Tuesday, October 14, 2014 10:16:56 AM
Subject: Let's pay special attention to post-commit Jenkins UT failure reports
Hi all,
Unit tests on branch-1.7.0 have been failing since 10/11 until it was fixed
recently via https://issues.apache.org/jira/browse/AMBARI-7774.
Branch 1.7.0 Jenkins jobs:
https://builds.apache.org/job/Ambari-branch-1.7.0/
Note that builds #63 through #86 all reported UT failures consecutively.
This is a situation that we really need to avoid on trunk or any branch,
but especially for a release branch.
There is the patch verification job (aka "Hadoop QA"), but there are also
post-commit jobs that report to the JIRA whether a UT failure occurred or
not.
What seems to be happening is that the patch verification job works against
trunk and report OK, but when patches are committed to branch-1.7.0, the
post-commit UT job is catching UT failures specifically for the branch and
reporting back to the JIRAs that potentially caused the failure.
However, it seems that these reports are largely being ignored.
If you are the contributor/committer for a JIRA that has a post-commit
failure report, please take appropriate action.
Also, I'd like to propose incorporating some sort of post-commit UT failure
report handling into our Dev Process. Thoughts?
Yusaku
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.