Re: Automatic ABI checks for new package updates in bodhi using taskotron

Kamil Paral a écrit: > Thanks, I reported an RFE about this: > https://phab.qadevel.cloud.fedoraproject.org/T811 Thanks Kamil, Unfortunately, I still cannot log into https://phab.qadevel.cloud.fedoraproject.org/T811 using my do...@fedoraproject.org persona, so I cannot

Re: Automatic ABI checks for new package updates in bodhi using taskotron

Hello, Sorry for the late reply. Kamil Paral a écrit: >> So, let's say we initially start with packages available in >> critpath[3], then we don't have to worry whether a package provides >> any shared library or not. > > Let me try this another way. Let's assume we can

Re: Automatic ABI checks for new package updates in bodhi using taskotron

> > Speaking of lists, you and Tim were mentioning white/blacklists, also > > critpath set. So what is the ideal set of packages we should run on > > initially? All packages? Only critpath packages? Only libraries included > > in critpath? In case we should run just on libraries, any good > >

Re: Automatic ABI checks for new package updates in bodhi using taskotron

> Hello Kamil, > > Sorry for replying late. I subscribed to this list, but for a reason the > emails are still not being delivered to me. I clicked on some more buttons > in the interface right now, so we'll see. In the mean time, I am using the > web interface to reply, so please forgive the

Re: Automatic ABI checks for new package updates in bodhi using taskotron

> Thanks for the quick review. I have addressed review comments and added new > diff at https://phab.qadevel.cloud.fedoraproject.org/D817?id=2081 . Thanks, looks good. I have no further concerns regarding the task code. > I am not > sure if I updated diff in right way but this is what I ended

Re: Automatic ABI checks for new package updates in bodhi using taskotron

Hello Kamil, Sorry for replying late. I subscribed to this list, but for a reason the emails are still not being delivered to me. I clicked on some more buttons in the interface right now, so we'll see. In the mean time, I am using the web interface to reply, so please forgive the awkward

Re: Automatic ABI checks for new package updates in bodhi using taskotron

Hi Kamil, On Thu, Apr 14, 2016 at 8:40 PM, Kamil Paral wrote: > Hi Sinny, > > I have created a review here: > https://phab.qadevel.cloud.fedoraproject.org/D813 > > I used our Phabricator, because it makes it easy to comment on particular > lines. You can log in using your

Re: Automatic ABI checks for new package updates in bodhi using taskotron

Hi Sinny, I have created a review here: https://phab.qadevel.cloud.fedoraproject.org/D813 I used our Phabricator, because it makes it easy to comment on particular lines. You can log in using your FAS email [1] and reply there, or here in the mailing list, it doesn't matter. I'm pleasantly

Re: Automatic ABI checks for new package updates in bodhi using taskotron

On Wed, 13 Apr 2016 21:14:19 +0530 Sinny Kumari wrote: Thank you for getting this done, I'm excited to start it running in Taskotron. > You need to decide whether it is better to run libabigain against > every new > > Koji build, or just against every new Bodhi update. From

Re: Automatic ABI checks for new package updates in bodhi using taskotron

> Hi all, > Last year, discussion happened around "Checking the ABI of packages submitted > to the updates-testing Fedora repository" on Fedora devel ML [1]. > We felt that taskotron[2] will be the best place to run automatic ABI checks > for a new package update pushed in bodhi for testing