You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Paolo Patierno <pp...@live.com> on 2017/06/12 08:20:38 UTC
Test fail reason on doc fix
Hi all,
I opened this JIRA with a related PR few days ago :
https://github.com/apache/kafka/pull/3269
https://issues.apache.org/jira/browse/KAFKA-5410
It's just a fix on a documentation file but in the PR I see a Test FAILed (JDK 7 and Scala 2.11) with no more information about that.
Because it sounds strange to me, because I didn't change any Java/Scala code, what is the way to go to check the failure reason ?
Thanks,
Paolo.
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/>
Re: Test fail reason on doc fix
Posted by Paolo Patierno <pp...@live.com>.
And after two "Retest this please" .. it worked :-)
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/>
________________________________
From: Paolo Patierno <pp...@live.com>
Sent: Monday, June 12, 2017 12:41 PM
To: Michal Borowiecki; dev@kafka.apache.org
Subject: Re: Test fail reason on doc fix
Thanks Michal ... I have done in this way but now the test which failed is now passed. The other test which was successful is now aborted (https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5149/).
I'll retry with a new "Retest this please" ;)
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/>
________________________________
From: Michal Borowiecki <mi...@openbet.com>
Sent: Monday, June 12, 2017 9:26 AM
To: dev@kafka.apache.org; Paolo Patierno
Subject: Re: Test fail reason on doc fix
Some tests are intermittently failing, it may go away when you retest. You can trigger a retest by putting a comment "Retest this please" on your PR.
Hope that helps,
Michał
On 12/06/17 10:19, Paolo Patierno wrote:
Hi Tom,
this is the problem I noticed for this reason asked here. Btw I don't understand the reason for a failure on a simple doc fix (inside the HTML file) :-)
Thanks,
Paolo
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno><http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno><http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/><http://paolopatierno.wordpress.com/>
________________________________
From: Tom Bentley <t....@gmail.com>
Sent: Monday, June 12, 2017 9:17 AM
To: dev@kafka.apache.org<ma...@kafka.apache.org>
Subject: Re: Test fail reason on doc fix
Hi Paolo,
Usually you can just follow the links added by asfbot on the PR, but these
are currently giving 404 (and not just for your failures, so maybe an ASF
infrastructure problem?)
Cheers,
Tom
On 12 June 2017 at 09:20, Paolo Patierno <pp...@live.com> wrote:
Hi all,
I opened this JIRA with a related PR few days ago :
https://github.com/apache/kafka/pull/3269
https://issues.apache.org/jira/browse/KAFKA-5410
It's just a fix on a documentation file but in the PR I see a Test FAILed
(JDK 7 and Scala 2.11) with no more information about that.
Because it sounds strange to me, because I didn't change any Java/Scala
code, what is the way to go to check the failure reason ?
Thanks,
Paolo.
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno><http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno><http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/><http://paolopatierno.wordpress.com/>
--
[cid:part1.357E5BC3.818C28FB@openbet.com]<http://www.openbet.com/> Michal Borowiecki
Senior Software Engineer L4
[cid:part3.5DFFD143.24010FAF@openbet.com] T: +44 208 742 1600
+44 203 249 8448
[cid:part3.5DFFD143.24010FAF@openbet.com] E: michal.borowiecki@openbet.com<ma...@openbet.com>
[cid:part3.5DFFD143.24010FAF@openbet.com] W: www.openbet.com<http://www.openbet.com/>
[cid:part3.5DFFD143.24010FAF@openbet.com] OpenBet Ltd
Chiswick Park Building 9
566 Chiswick High Rd
London
W4 5XT
UK
[cid:part8.DE3B2AAA.26ACE50A@openbet.com]<https://www.openbet.com/email_promo>
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@openbet.com<ma...@openbet.com> and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by OpenBet for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. OpenBet Ltd. Registered Office: Chiswick Park Building 9, 566 Chiswick High Road, London, W4 5XT, United Kingdom. A company registered in England and Wales. Registered no. 3134634. VAT no. GB927523612
Re: Test fail reason on doc fix
Posted by Paolo Patierno <pp...@live.com>.
Thanks Michal ... I have done in this way but now the test which failed is now passed. The other test which was successful is now aborted (https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5149/).
I'll retry with a new "Retest this please" ;)
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/>
________________________________
From: Michal Borowiecki <mi...@openbet.com>
Sent: Monday, June 12, 2017 9:26 AM
To: dev@kafka.apache.org; Paolo Patierno
Subject: Re: Test fail reason on doc fix
Some tests are intermittently failing, it may go away when you retest. You can trigger a retest by putting a comment "Retest this please" on your PR.
Hope that helps,
Michał
On 12/06/17 10:19, Paolo Patierno wrote:
Hi Tom,
this is the problem I noticed for this reason asked here. Btw I don't understand the reason for a failure on a simple doc fix (inside the HTML file) :-)
Thanks,
Paolo
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno><http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno><http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/><http://paolopatierno.wordpress.com/>
________________________________
From: Tom Bentley <t....@gmail.com>
Sent: Monday, June 12, 2017 9:17 AM
To: dev@kafka.apache.org<ma...@kafka.apache.org>
Subject: Re: Test fail reason on doc fix
Hi Paolo,
Usually you can just follow the links added by asfbot on the PR, but these
are currently giving 404 (and not just for your failures, so maybe an ASF
infrastructure problem?)
Cheers,
Tom
On 12 June 2017 at 09:20, Paolo Patierno <pp...@live.com> wrote:
Hi all,
I opened this JIRA with a related PR few days ago :
https://github.com/apache/kafka/pull/3269
https://issues.apache.org/jira/browse/KAFKA-5410
It's just a fix on a documentation file but in the PR I see a Test FAILed
(JDK 7 and Scala 2.11) with no more information about that.
Because it sounds strange to me, because I didn't change any Java/Scala
code, what is the way to go to check the failure reason ?
Thanks,
Paolo.
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno><http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno><http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/><http://paolopatierno.wordpress.com/>
--
[cid:part1.357E5BC3.818C28FB@openbet.com]<http://www.openbet.com/> Michal Borowiecki
Senior Software Engineer L4
[cid:part3.5DFFD143.24010FAF@openbet.com] T: +44 208 742 1600
+44 203 249 8448
[cid:part3.5DFFD143.24010FAF@openbet.com] E: michal.borowiecki@openbet.com<ma...@openbet.com>
[cid:part3.5DFFD143.24010FAF@openbet.com] W: www.openbet.com<http://www.openbet.com/>
[cid:part3.5DFFD143.24010FAF@openbet.com] OpenBet Ltd
Chiswick Park Building 9
566 Chiswick High Rd
London
W4 5XT
UK
[cid:part8.DE3B2AAA.26ACE50A@openbet.com]<https://www.openbet.com/email_promo>
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@openbet.com<ma...@openbet.com> and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by OpenBet for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. OpenBet Ltd. Registered Office: Chiswick Park Building 9, 566 Chiswick High Road, London, W4 5XT, United Kingdom. A company registered in England and Wales. Registered no. 3134634. VAT no. GB927523612
Re: Test fail reason on doc fix
Posted by Michal Borowiecki <mi...@openbet.com>.
Some tests are intermittently failing, it may go away when you retest.
You can trigger a retest by putting a comment "Retest this please" on
your PR.
Hope that helps,
Michał
On 12/06/17 10:19, Paolo Patierno wrote:
> Hi Tom,
>
>
> this is the problem I noticed for this reason asked here. Btw I don't understand the reason for a failure on a simple doc fix (inside the HTML file) :-)
>
>
> Thanks,
>
> Paolo
>
>
> Paolo Patierno
> Senior Software Engineer (IoT) @ Red Hat
> Microsoft MVP on Windows Embedded & IoT
> Microsoft Azure Advisor
>
> Twitter : @ppatierno<http://twitter.com/ppatierno>
> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
> Blog : DevExperience<http://paolopatierno.wordpress.com/>
>
>
> ________________________________
> From: Tom Bentley <t....@gmail.com>
> Sent: Monday, June 12, 2017 9:17 AM
> To: dev@kafka.apache.org
> Subject: Re: Test fail reason on doc fix
>
> Hi Paolo,
>
> Usually you can just follow the links added by asfbot on the PR, but these
> are currently giving 404 (and not just for your failures, so maybe an ASF
> infrastructure problem?)
>
> Cheers,
>
> Tom
>
> On 12 June 2017 at 09:20, Paolo Patierno <pp...@live.com> wrote:
>
>> Hi all,
>>
>>
>> I opened this JIRA with a related PR few days ago :
>>
>>
>> https://github.com/apache/kafka/pull/3269
>> https://issues.apache.org/jira/browse/KAFKA-5410
>>
>>
>> It's just a fix on a documentation file but in the PR I see a Test FAILed
>> (JDK 7 and Scala 2.11) with no more information about that.
>>
>> Because it sounds strange to me, because I didn't change any Java/Scala
>> code, what is the way to go to check the failure reason ?
>>
>>
>> Thanks,
>>
>> Paolo.
>>
>>
>> Paolo Patierno
>> Senior Software Engineer (IoT) @ Red Hat
>> Microsoft MVP on Windows Embedded & IoT
>> Microsoft Azure Advisor
>>
>> Twitter : @ppatierno<http://twitter.com/ppatierno>
>> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
>> Blog : DevExperience<http://paolopatierno.wordpress.com/>
>>
--
Signature
<http://www.openbet.com/> Michal Borowiecki
Senior Software Engineer L4
T: +44 208 742 1600
+44 203 249 8448
E: michal.borowiecki@openbet.com
W: www.openbet.com <http://www.openbet.com/>
OpenBet Ltd
Chiswick Park Building 9
566 Chiswick High Rd
London
W4 5XT
UK
<https://www.openbet.com/email_promo>
This message is confidential and intended only for the addressee. If you
have received this message in error, please immediately notify the
postmaster@openbet.com <ma...@openbet.com> and delete it
from your system as well as any copies. The content of e-mails as well
as traffic data may be monitored by OpenBet for employment and security
purposes. To protect the environment please do not print this e-mail
unless necessary. OpenBet Ltd. Registered Office: Chiswick Park Building
9, 566 Chiswick High Road, London, W4 5XT, United Kingdom. A company
registered in England and Wales. Registered no. 3134634. VAT no.
GB927523612
Re: Test fail reason on doc fix
Posted by Paolo Patierno <pp...@live.com>.
Hi Tom,
this is the problem I noticed for this reason asked here. Btw I don't understand the reason for a failure on a simple doc fix (inside the HTML file) :-)
Thanks,
Paolo
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
Twitter : @ppatierno<http://twitter.com/ppatierno>
Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
Blog : DevExperience<http://paolopatierno.wordpress.com/>
________________________________
From: Tom Bentley <t....@gmail.com>
Sent: Monday, June 12, 2017 9:17 AM
To: dev@kafka.apache.org
Subject: Re: Test fail reason on doc fix
Hi Paolo,
Usually you can just follow the links added by asfbot on the PR, but these
are currently giving 404 (and not just for your failures, so maybe an ASF
infrastructure problem?)
Cheers,
Tom
On 12 June 2017 at 09:20, Paolo Patierno <pp...@live.com> wrote:
> Hi all,
>
>
> I opened this JIRA with a related PR few days ago :
>
>
> https://github.com/apache/kafka/pull/3269
> https://issues.apache.org/jira/browse/KAFKA-5410
>
>
> It's just a fix on a documentation file but in the PR I see a Test FAILed
> (JDK 7 and Scala 2.11) with no more information about that.
>
> Because it sounds strange to me, because I didn't change any Java/Scala
> code, what is the way to go to check the failure reason ?
>
>
> Thanks,
>
> Paolo.
>
>
> Paolo Patierno
> Senior Software Engineer (IoT) @ Red Hat
> Microsoft MVP on Windows Embedded & IoT
> Microsoft Azure Advisor
>
> Twitter : @ppatierno<http://twitter.com/ppatierno>
> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
> Blog : DevExperience<http://paolopatierno.wordpress.com/>
>
Re: Test fail reason on doc fix
Posted by Tom Bentley <t....@gmail.com>.
Hi Paolo,
Usually you can just follow the links added by asfbot on the PR, but these
are currently giving 404 (and not just for your failures, so maybe an ASF
infrastructure problem?)
Cheers,
Tom
On 12 June 2017 at 09:20, Paolo Patierno <pp...@live.com> wrote:
> Hi all,
>
>
> I opened this JIRA with a related PR few days ago :
>
>
> https://github.com/apache/kafka/pull/3269
> https://issues.apache.org/jira/browse/KAFKA-5410
>
>
> It's just a fix on a documentation file but in the PR I see a Test FAILed
> (JDK 7 and Scala 2.11) with no more information about that.
>
> Because it sounds strange to me, because I didn't change any Java/Scala
> code, what is the way to go to check the failure reason ?
>
>
> Thanks,
>
> Paolo.
>
>
> Paolo Patierno
> Senior Software Engineer (IoT) @ Red Hat
> Microsoft MVP on Windows Embedded & IoT
> Microsoft Azure Advisor
>
> Twitter : @ppatierno<http://twitter.com/ppatierno>
> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
> Blog : DevExperience<http://paolopatierno.wordpress.com/>
>