#7033 libomp: Display CI results for pull requests
Closed: Fixed 5 years ago Opened 6 years ago by tstellar.

  • Describe what you need us to do:
    Could you display the CI results for libomp pull requests in pagure?

You can use this outstanding pull request for testing:

  • When do you need this? (YYYY/MM/DD)
    Not urgent, but it would be nice to have this working.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    Same as previous question.

  • If we cannot complete your request, what is the impact?
    I will have to do more manually testing for libomp.

@pingou is this something for you? Should it be in pagure upstream rather than here?

Metadata Update from @kevin:
- Issue assigned to pingou
- Issue priority set to: Waiting on Assignee (was: Needs Review)

6 years ago

I'm going to be going through and adding CI tests to a few packages that I maintain, so if it's easier to do all these at once I would like this set up for the following packages:


The test results for PR is in the following topic: org.centos.prod.ci.pipeline.allpackages-pr.complete.

There are 3 possible value for status:
SUCCESS: Test ran successfully.
UNSTABLE: Test ran, but failed.
FAILURE: Some infrastructure issue or test.log was not created.

SUCCESS: https://apps.fedoraproject.org/datagrepper/id?id=2018-07b98b50-3330-4534-893d-00f4bfc1d496&is_raw=true&size=extra-large

UNSTABLE: https://apps.fedoraproject.org/datagrepper/id?id=2018-0ce4818e-6f3c-4b39-aa8f-2e21b1fc02a6&is_raw=true&size=extra-large

FAILURE: https://apps.fedoraproject.org/datagrepper/id?id=2018-66d2175a-774d-4a3e-982f-9382c20460cd&is_raw=true&size=extra-large

Thanks for all the info :)

@tstellar note that we won't turn this on per project, but for all in one go, so no need to provide a list :)

@bgoncalv looking at the message, may I assume that:
- it is only triggered on PR (new or updated ones)
- the rev is and will always be PR-<int> where the integer will correspond to the PR id in src.fp.o


@bgoncalv looking at the message, may I assume that:
- it is only triggered on PR (new or updated ones)

Correct. The topic is for new PR or any other action on the PR that triggers CI, like rebase or new comment with [citest] tag.

  • the rev is and will always be PR-<int> where the integer will correspond to the PR id in src.fp.o

Also correct :)

@pingou I forgot to list 2 topics that might be useful...

org.centos.prod.ci.pipeline.allpackages-pr.package.ignored - In case there is no test.
org.centos.prod.ci.pipeline.allpackages-pr.package.queued - First topic that is sent when there is test.

Good to know this OPENED ticket, it's useful feature I have been waiting for now. I have 1 PR which is filed by other colleague in some situation, I am concern about I can not receive the Fedora CI pipeline result.

I just wonder it is possible that people received pipeline result is customizable? It might be available for multiple people to receive result at same time? e.g QA contact, Package User, PR submitter. Thank You!

Ok I have everything ready to give it a try, but since it's not running in the staging bus, I'd like to be around when it first run on the prod server.

Could you ping me when you're ready to open a PR that will trigger the CI pipeline? Then we can watch how things are behaving and fix as needed :)

@pingou do you want to try it now? If so, I think I can start new test run with https://src.fedoraproject.org/rpms/udisks2/pull-request/2

@bgoncalv I'm about to head out so nope, Friday would work for me :)

@pingou okay, just ping me when we should give it a try :)

Got the basis done: https://src.fedoraproject.org/rpms/udisks2/pull-request/2

I'm not sure why we got two flags, if it was a single-time blip or if it'll happen more, so I'll keep on monitoring this a little, but I think this ticket in itself can be closed :)

Metadata Update from @pingou:
- Issue close_status updated to: Fixed

5 years ago

Log in to comment on this ticket.