My PR test says error ... but where do I find the reason?

[Jan Pazdziora]

Hello,

I've filed

	https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/1

attempting to add a CI test to my package. A test Fedora CI - dist-git
test got run with result error. The test link on the PR page takes me
to

	https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...

and there I click on Console Output to get to

	https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...

where I see

	[Pipeline] echo
	The status is now "running"
	[Pipeline] echo
	Waiting for Testing Farm...
	[Pipeline] waitForWebhook
	[Pipeline] retry
	[Pipeline] {
	[Pipeline] httpRequest
	[Pipeline] }
	[Pipeline] // retry
	[Pipeline] echo
	The status is now "error"
	[Pipeline] }
	[Pipeline] // script
	[Pipeline] }

Where do I find the actual output of my test to see what went wrong in
it?

-- 
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat

[Petr Šplíchal]

On Tue, 15 Mar 2022 at 07:06, Jan Pazdziora <jpazdziora(a)redhat.com&gt; wrote:

>  Hello,
>
>  I've filed
>
>
>  https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/1
>
>  attempting to add a CI test to my package. A test Fedora CI - dist-git
>  test got run with result error. The test link on the PR page takes me
>  to
>
>
>
> https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
>
>  and there I click on Console Output to get to
>
>
>
> https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
>
>  where I see
>
>          [Pipeline] echo
>          The status is now "running"
>          [Pipeline] echo
>          Waiting for Testing Farm...
>          [Pipeline] waitForWebhook
>          [Pipeline] retry
>          [Pipeline] {
>          [Pipeline] httpRequest
>          [Pipeline] }
>          [Pipeline] // retry
>          [Pipeline] echo
>          The status is now "error"
>          [Pipeline] }
>          [Pipeline] // script
>          [Pipeline] }
>
>  Where do I find the actual output of my test to see what went wrong in
>  it?
>  
Hi!

Yes, with STI the log inspection is sometimes very hard.
Miro, Michal, is there a way to get to the detailed ansible error?

Enabling the test from the sources using tmt seems to provide a much better
output:
https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/2
https://artifacts.dev.testing-farm.io/da555e16-dd7f-4b14-b6b0-7fda4fd05313/

Also using tmt you can test/verify the setup very quickly from your laptop:
tmt run -vvv (in a local vm using testcloud/libvirt)
tmt run -vvv --all provision --how container (in a container)

psss...


>  --
>  Jan Pazdziora
>  Product Owner, Platform Security Readiness, Red Hat
>  _______________________________________________
>  CI mailing list -- ci(a)lists.fedoraproject.org
>  To unsubscribe send an email to ci-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Miroslav Vadkerti]

Actually it was an outage due to a PEBKAC:

https://pagure.io/cloud-sig/issue/372

@Jan Pazdziora <jpazdziora(a)redhat.com&gt; we try to fix issues very early,
trying [citest] is advised in case you cannot understand the error.
We do not do that automatically, sorry for that.

I restarted it, let's see how it goes,

Best regards,
/M

On Tue, Mar 15, 2022 at 9:40 AM Petr Šplíchal <psplicha(a)redhat.com&gt; wrote:

>  On Tue, 15 Mar 2022 at 07:06, Jan Pazdziora
> <jpazdziora(a)redhat.com&gt; wrote:
>
> >
> > Hello,
> >
> > I've filed
> >
> >
> > https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/1
> >
> > attempting to add a CI test to my package. A test Fedora CI - dist-git
> > test got run with result error. The test link on the PR page takes me
> > to
> >
> >
> >
> https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
> >
> > and there I click on Console Output to get to
> >
> >
> >
> https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
> >
> > where I see
> >
> >         [Pipeline] echo
> >         The status is now "running"
> >         [Pipeline] echo
> >         Waiting for Testing Farm...
> >         [Pipeline] waitForWebhook
> >         [Pipeline] retry
> >         [Pipeline] {
> >         [Pipeline] httpRequest
> >         [Pipeline] }
> >         [Pipeline] // retry
> >         [Pipeline] echo
> >         The status is now "error"
> >         [Pipeline] }
> >         [Pipeline] // script
> >         [Pipeline] }
> >
> > Where do I find the actual output of my test to see what went wrong in
> > it?
> >
>
>  Hi!
>
>  Yes, with STI the log inspection is sometimes very hard.
>  Miro, Michal, is there a way to get to the detailed ansible error?
>
>  Enabling the test from the sources using tmt seems to provide a much
>  better output:
>  https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/2
>  https://artifacts.dev.testing-farm.io/da555e16-dd7f-4b14-b6b0-7fda4fd05313/
>
>  Also using tmt you can test/verify the setup very quickly from your laptop:
>  tmt run -vvv (in a local vm using testcloud/libvirt)
>  tmt run -vvv --all provision --how container (in a container)
>
>  psss...
>
>
> > --
> > Jan Pazdziora
> > Product Owner, Platform Security Readiness, Red Hat
> > _______________________________________________
> > CI mailing list -- ci(a)lists.fedoraproject.org
> > To unsubscribe send an email to ci-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/[e-mail]
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
> >
>  
-- 
Miroslav Vadkerti :: Senior Principal QE :: Testing Farm / Linux QE
IRC mvadkert #tft #tmt #osci :: Mobile [phone]
Remote Czech Republic :: Red Hat Czech s.r.o

[Vít Ondruch]

You are welcome to join the rant at:

https://pagure.io/fedora-ci/general/issue/311


Vít


Dne 15. 03. 22 v 7:05 Jan Pazdziora napsal(a):
>  Hello,
>
>  I've filed
>
>  	https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/1
>
>  attempting to add a CI test to my package. A test Fedora CI - dist-git
>  test got run with result error. The test link on the PR page takes me
>  to
>
>
> 	https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
>
>  and there I click on Console Output to get to
>
>
> 	https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
>
>  where I see
>
>  	[Pipeline] echo
>  	The status is now "running"
>  	[Pipeline] echo
>  	Waiting for Testing Farm...
>  	[Pipeline] waitForWebhook
>  	[Pipeline] retry
>  	[Pipeline] {
>  	[Pipeline] httpRequest
>  	[Pipeline] }
>  	[Pipeline] // retry
>  	[Pipeline] echo
>  	The status is now "error"
>  	[Pipeline] }
>  	[Pipeline] // script
>  	[Pipeline] }
>
>  Where do I find the actual output of my test to see what went wrong in
>  it?
>
>

[Miroslav Vadkerti]

On Tue, Mar 15, 2022 at 12:37 PM Vít Ondruch <vondruch(a)redhat.com&gt; wrote:

>  You are welcome to join the rant at:
>
>  https://pagure.io/fedora-ci/general/issue/311 

It will be solved, we have outlined with OSCI how to make Jenkins show what
you want


>  Vít
>
>
>  Dne 15. 03. 22 v 7:05 Jan Pazdziora napsal(a):
>  > Hello,
>  >
>  > I've filed
>  >
>  >
>  https://src.fedoraproject.org/rpms/mod_intercept_form_submit/pull-request/1
>  >
>  > attempting to add a CI test to my package. A test Fedora CI - dist-git
>  > test got run with result error. The test link on the PR page takes me
>  > to
>  >
>  >
>
> https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
>  >
>  > and there I click on Console Output to get to
>  >
>  >
>
> https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
>  >
>  > where I see
>  >
>  >       [Pipeline] echo
>  >       The status is now "running"
>  >       [Pipeline] echo
>  >       Waiting for Testing Farm...
>  >       [Pipeline] waitForWebhook
>  >       [Pipeline] retry
>  >       [Pipeline] {
>  >       [Pipeline] httpRequest
>  >       [Pipeline] }
>  >       [Pipeline] // retry
>  >       [Pipeline] echo
>  >       The status is now "error"
>  >       [Pipeline] }
>  >       [Pipeline] // script
>  >       [Pipeline] }
>  >
>  > Where do I find the actual output of my test to see what went wrong in
>  > it?
>  >
>  _______________________________________________
>  CI mailing list -- ci(a)lists.fedoraproject.org
>  To unsubscribe send an email to ci-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 
Miroslav Vadkerti :: Senior Principal QE :: Testing Farm / Linux QE
IRC mvadkert #tft #tmt #osci :: Mobile [phone]
Remote Czech Republic :: Red Hat Czech s.r.o