Re: Getting notified on broken deps from updates-testing

[Fabio Valentini]

On Sun, Nov 10, 2019 at 10:24 PM Kevin Fenzi  wrote:
>
> On Sun, Nov 10, 2019 at 06:06:22PM +0100, Fabio Valentini wrote:
> > On Fri, Nov 8, 2019 at 10:24 AM Vít Ondruch  wrote:
> > >
> > > I think that the basic problem is that the "broken dependencies" emails
> > > are not sent anymore even for Rawhide. This is big loss.
> >
> > If you think that the weekly "broken dependencies" reports were
> > useful, I could set that up again.
> > After all, I already have the data, and write out reports in markdown 
> > format.
> >
> > It would be pretty easy to also generate a plain text version and then
> > just send that to the devel list on a weekly basis.
> > However, for updates-testing reports to be useful, weekly would
> > probably be not frequently enough (most updates only sit in -testing
> > for 7 days, after all).
> >
> > The code, data, and reports in easily viewable markdown format are here:
> > https://pagure.io/fedora-health-check
>
> Perhaps you might be willing to look at integrating this with the
> updates push composes and/or rawhide? We never got the old spam-o-matic
> working with more than just x86_64...
>
> https://pagure.io/releng/issue/6365
> https://pagure.io/releng/issue/7931
> (and possibly others/prs)

Yeah, that would probably be a good idea, though I'll try to get this
working reliably locally first.
Once it proves stable and useful, we can maybe reuse some of the code
and integrate it with the compose process. :)

Fabio

> kevin
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Fabio Valentini]

On Mon, Nov 11, 2019 at 5:02 AM Neal Gompa  wrote:
>
> On Sun, Nov 10, 2019 at 4:24 PM Kevin Fenzi  wrote:
> >
> > On Sun, Nov 10, 2019 at 06:06:22PM +0100, Fabio Valentini wrote:
> > > On Fri, Nov 8, 2019 at 10:24 AM Vít Ondruch  wrote:
> > > >
> > > > I think that the basic problem is that the "broken dependencies" emails
> > > > are not sent anymore even for Rawhide. This is big loss.
> > >
> > > If you think that the weekly "broken dependencies" reports were
> > > useful, I could set that up again.
> > > After all, I already have the data, and write out reports in markdown 
> > > format.
> > >
> > > It would be pretty easy to also generate a plain text version and then
> > > just send that to the devel list on a weekly basis.
> > > However, for updates-testing reports to be useful, weekly would
> > > probably be not frequently enough (most updates only sit in -testing
> > > for 7 days, after all).
> > >
> > > The code, data, and reports in easily viewable markdown format are here:
> > > https://pagure.io/fedora-health-check
> >
> > Perhaps you might be willing to look at integrating this with the
> > updates push composes and/or rawhide? We never got the old spam-o-matic
> > working with more than just x86_64...
> >
> > https://pagure.io/releng/issue/6365
> > https://pagure.io/releng/issue/7931
> > (and possibly others/prs)
> >
>
> Fabio's script also only validates on x86_64. I still don't get why
> dnf repoclosure is so broken when querying alternative
> architectures...
>
> When I wrote the DNF port to spam-o-matic, I made sure it worked, and
> it did when I wrote it. Unfortunately something in DNF broke, and I'm
> not sure exactly what or how. But there's been significant changes in
> architecture handling in the past 8 months, so maybe it'll work
> properly now?

I've adapted my script to check all architectures now (and I think it
works correctly).
I'm using --forcearch and "--arch foo" to make sure it uses the
correct repository and queries the correct arches.
So the data I'll be generating later today will include broken deps
for all arches.

Fabio

> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Fabio Valentini]

On Sun, Nov 10, 2019 at 11:57 PM Miro Hrončok  wrote:
>
> On 10. 11. 19 18:06, Fabio Valentini wrote:
> > On Fri, Nov 8, 2019 at 10:24 AM Vít Ondruch  wrote:
> >>
> >> I think that the basic problem is that the "broken dependencies" emails
> >> are not sent anymore even for Rawhide. This is big loss.
> >
> > If you think that the weekly "broken dependencies" reports were
> > useful, I could set that up again.
> > After all, I already have the data, and write out reports in markdown 
> > format.
> >
> > It would be pretty easy to also generate a plain text version and then
> > just send that to the devel list on a weekly basis.
> > However, for updates-testing reports to be useful, weekly would
> > probably be not frequently enough (most updates only sit in -testing
> > for 7 days, after all).
> >
> > The code, data, and reports in easily viewable markdown format are here:
> > https://pagure.io/fedora-health-check
> >
> > Fabio
>
> I believe, it might be useful to get and "instant" e-mail once a package I
> maintain has broken dependency but it was OK before.
>
> Aka you snapshot the data, regenerate it again, do a diff and send only new
> packages.
>
> Otherwise it would just be spam to most of the maintainers, it's just too 
> many.

Yes, that's exactly what I had in mind. Currently there's way too many
broken dependencies to notify everybody about everything.
You can already see the snapshot diffs in the git repo on pagure
(although I'm relying on the git history to store old diffs, and keep
only the latest one).

For example, here you can see yesterday's diff for fedora-31-updates-testing:
https://pagure.io/fedora-health-check/blob/6791a6d/f/changes/diff-31-testing.json

(I'd have linked the diff for rawhide, but it's too big to be useful
for human consumption.)

Fabio

> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Neal Gompa]

On Sun, Nov 10, 2019 at 4:24 PM Kevin Fenzi  wrote:
>
> On Sun, Nov 10, 2019 at 06:06:22PM +0100, Fabio Valentini wrote:
> > On Fri, Nov 8, 2019 at 10:24 AM Vít Ondruch  wrote:
> > >
> > > I think that the basic problem is that the "broken dependencies" emails
> > > are not sent anymore even for Rawhide. This is big loss.
> >
> > If you think that the weekly "broken dependencies" reports were
> > useful, I could set that up again.
> > After all, I already have the data, and write out reports in markdown 
> > format.
> >
> > It would be pretty easy to also generate a plain text version and then
> > just send that to the devel list on a weekly basis.
> > However, for updates-testing reports to be useful, weekly would
> > probably be not frequently enough (most updates only sit in -testing
> > for 7 days, after all).
> >
> > The code, data, and reports in easily viewable markdown format are here:
> > https://pagure.io/fedora-health-check
>
> Perhaps you might be willing to look at integrating this with the
> updates push composes and/or rawhide? We never got the old spam-o-matic
> working with more than just x86_64...
>
> https://pagure.io/releng/issue/6365
> https://pagure.io/releng/issue/7931
> (and possibly others/prs)
>

Fabio's script also only validates on x86_64. I still don't get why
dnf repoclosure is so broken when querying alternative
architectures...

When I wrote the DNF port to spam-o-matic, I made sure it worked, and
it did when I wrote it. Unfortunately something in DNF broke, and I'm
not sure exactly what or how. But there's been significant changes in
architecture handling in the past 8 months, so maybe it'll work
properly now?



--
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Miro Hrončok]

On 10. 11. 19 18:06, Fabio Valentini wrote:

On Fri, Nov 8, 2019 at 10:24 AM Vít Ondruch  wrote:


I think that the basic problem is that the "broken dependencies" emails
are not sent anymore even for Rawhide. This is big loss.


If you think that the weekly "broken dependencies" reports were
useful, I could set that up again.
After all, I already have the data, and write out reports in markdown format.

It would be pretty easy to also generate a plain text version and then
just send that to the devel list on a weekly basis.
However, for updates-testing reports to be useful, weekly would
probably be not frequently enough (most updates only sit in -testing
for 7 days, after all).

The code, data, and reports in easily viewable markdown format are here:
https://pagure.io/fedora-health-check

Fabio


I believe, it might be useful to get and "instant" e-mail once a package I 
maintain has broken dependency but it was OK before.


Aka you snapshot the data, regenerate it again, do a diff and send only new 
packages.


Otherwise it would just be spam to most of the maintainers, it's just too many.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Kevin Fenzi]

On Sun, Nov 10, 2019 at 06:06:22PM +0100, Fabio Valentini wrote:
> On Fri, Nov 8, 2019 at 10:24 AM Vít Ondruch  wrote:
> >
> > I think that the basic problem is that the "broken dependencies" emails
> > are not sent anymore even for Rawhide. This is big loss.
> 
> If you think that the weekly "broken dependencies" reports were
> useful, I could set that up again.
> After all, I already have the data, and write out reports in markdown format.
> 
> It would be pretty easy to also generate a plain text version and then
> just send that to the devel list on a weekly basis.
> However, for updates-testing reports to be useful, weekly would
> probably be not frequently enough (most updates only sit in -testing
> for 7 days, after all).
> 
> The code, data, and reports in easily viewable markdown format are here:
> https://pagure.io/fedora-health-check

Perhaps you might be willing to look at integrating this with the
updates push composes and/or rawhide? We never got the old spam-o-matic
working with more than just x86_64...

https://pagure.io/releng/issue/6365
https://pagure.io/releng/issue/7931
(and possibly others/prs)

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Fabio Valentini]

On Fri, Nov 8, 2019 at 10:24 AM Vít Ondruch  wrote:
>
> I think that the basic problem is that the "broken dependencies" emails
> are not sent anymore even for Rawhide. This is big loss.

If you think that the weekly "broken dependencies" reports were
useful, I could set that up again.
After all, I already have the data, and write out reports in markdown format.

It would be pretty easy to also generate a plain text version and then
just send that to the devel list on a weekly basis.
However, for updates-testing reports to be useful, weekly would
probably be not frequently enough (most updates only sit in -testing
for 7 days, after all).

The code, data, and reports in easily viewable markdown format are here:
https://pagure.io/fedora-health-check

Fabio

> Vít
>
>
> Dne 06. 11. 19 v 21:32 Miro Hrončok napsal(a):
> > Hello,
> >
> > it repeatedly happened to me that I'm notified by Koschei that dozens
> > of my packages suddenly fail to resolve build dependencies on a
> > released Fedora.
> >
> > I usually find out that the broken update was sitting in testing for 7
> > days without any feedback, only to be pushed and receive ex-post
> > feedback from me.
> >
> > Is there any good way to get notified about this sort of problems in
> > timely manner prior to the update being pushed? This is currently not
> > optimal.
> >
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Martin Kolman]

On Wed, 2019-11-06 at 17:10 -0500, Randy Barlow wrote:
> On Wed, 2019-11-06 at 21:32 +0100, Miro Hrončok wrote:
> > Is there any good way to get notified about this sort of problems in
> > timely manner prior to the update being pushed? This is currently not
> > optimal.
> 
> I'm not familiar with an existing solution to this problem, but I agree
> that it is not optimal.
> 
> I had a chat or three with Brian Stinson about some ways we could deal
> with problems like this. Today, when we CI packages (i.e., Bodhi
> gating), we typically just run the tests associated with the package
> being altered. Brian suggested that we could *also* run the tests of
> the packages that depend on the package being altered, against the
> altered package. This way if a change to something (like pyramid) would
> break a dependent package's tests (such as cornice), then the update
> for pyramid should get a failed test result on its tests tab.
Something like this would be also very very useful for the Anaconda installer &
helthy compose flow. Many failed composes and installation problems are often
not issues in Anaconda itself, but the many tools and libraries it interacts
with changing behavior and breaking the installer & compose generation.

If new build of these components triggered the Anaconda test suite, lot of this
breakage could be averted and fixed early on before actually affecting anyone.

>  The
> problem is that this does increase the load on the test system greatly,
> but perhaps we can get enough hardware to make that OK. Not sure.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Vít Ondruch]

I think that the basic problem is that the "broken dependencies" emails
are not sent anymore even for Rawhide. This is big loss.


Vít


Dne 06. 11. 19 v 21:32 Miro Hrončok napsal(a):
> Hello,
>
> it repeatedly happened to me that I'm notified by Koschei that dozens
> of my packages suddenly fail to resolve build dependencies on a
> released Fedora.
>
> I usually find out that the broken update was sitting in testing for 7
> days without any feedback, only to be pushed and receive ex-post
> feedback from me.
>
> Is there any good way to get notified about this sort of problems in
> timely manner prior to the update being pushed? This is currently not
> optimal.
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Miro Hrončok]

On 07. 11. 19 16:26, Fabio Valentini wrote:

On Thu, Nov 7, 2019 at 10:14 AM Miro Hrončok  wrote:


On 07. 11. 19 9:55, Fabio Valentini wrote:

On Thu, Nov 7, 2019, 09:25 Miro Hrončok mailto:mhron...@redhat.com>> wrote:

 On 06. 11. 19 23:10, Randy Barlow wrote:
  > On Wed, 2019-11-06 at 21:32 +0100, Miro Hrončok wrote:
  >> Is there any good way to get notified about this sort of problems in
  >> timely manner prior to the update being pushed? This is currently not
  >> optimal.
  >
  > I'm not familiar with an existing solution to this problem, but I agree
  > that it is not optimal.
  >
  > I had a chat or three with Brian Stinson about some ways we could deal
  > with problems like this. Today, when we CI packages (i.e., Bodhi
  > gating), we typically just run the tests associated with the package
  > being altered. Brian suggested that we could *also* run the tests of
  > the packages that depend on the package being altered, against the
  > altered package. This way if a change to something (like pyramid) would
  > break a dependent package's tests (such as cornice), then the update
  > for pyramid should get a failed test result on its tests tab. The
  > problem is that this does increase the load on the test system greatly,
  > but perhaps we can get enough hardware to make that OK. Not sure.


 Having this sort of CI would be awesome, however it looks like it's not on 
the
 top of the TODO list:

 RFE: Koschei-like CI (opened  8 months ago)
 https://pagure.io/fedora-ci/general/issue/45

 RFE: Check if dependent packages install (opened 8 months ago)
 https://pagure.io/fedora-ci/general/issue/46

 Support automatic execution of tests of dependent components (opened 1 
year ago)
 https://pagure.io/fedora-ci/general/issue/7


 And either way, since CI is opt-in, I would need to go and setup CI for 
all of
 dependencies (including transitive) of all my packages. I haven't really
 checked
 how big is this tree but I suppose it is enormous.


Would an automated daily report (like the broken rawhide deps report that we
used to have) help? I could hack that together for different fedora branches +
updates-testing pretty easily, and adding notifications when a broken dependency
gets added in -testing wouldn't be hard either.


I've mostl started this thread to see if I indeed need to script this.

If you could look into it, ut would be awesome.

This is very useful as starting point (rawhide example):

$ sudo dnf --repo=rawhide makecache
$ installcheck x86_64 /var/cache/dnf/rawhide*.solv*

(Igor has shown this to me at Flock.)

It would probably need some interface that let me filter my packages. And
multi-repo for released Fedora.

This is what we use for Python 2 in rawhide:

https://github.com/fedora-python/portingdb/blob/master/portingdb/check_fti.py


Oh, I didn't know installcheck existed.
I've used repoclosure to get unsatisfied dependencies for all packages
(including unsatisfied BRs).

My initial work is here:
https://pagure.io/fedora-health-check


Looks awesome. Thanks.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Fabio Valentini]

On Thu, Nov 7, 2019 at 10:14 AM Miro Hrončok  wrote:
>
> On 07. 11. 19 9:55, Fabio Valentini wrote:
> > On Thu, Nov 7, 2019, 09:25 Miro Hrončok  > > wrote:
> >
> > On 06. 11. 19 23:10, Randy Barlow wrote:
> >  > On Wed, 2019-11-06 at 21:32 +0100, Miro Hrončok wrote:
> >  >> Is there any good way to get notified about this sort of problems in
> >  >> timely manner prior to the update being pushed? This is currently 
> > not
> >  >> optimal.
> >  >
> >  > I'm not familiar with an existing solution to this problem, but I 
> > agree
> >  > that it is not optimal.
> >  >
> >  > I had a chat or three with Brian Stinson about some ways we could 
> > deal
> >  > with problems like this. Today, when we CI packages (i.e., Bodhi
> >  > gating), we typically just run the tests associated with the package
> >  > being altered. Brian suggested that we could *also* run the tests of
> >  > the packages that depend on the package being altered, against the
> >  > altered package. This way if a change to something (like pyramid) 
> > would
> >  > break a dependent package's tests (such as cornice), then the update
> >  > for pyramid should get a failed test result on its tests tab. The
> >  > problem is that this does increase the load on the test system 
> > greatly,
> >  > but perhaps we can get enough hardware to make that OK. Not sure.
> >
> >
> > Having this sort of CI would be awesome, however it looks like it's not 
> > on the
> > top of the TODO list:
> >
> > RFE: Koschei-like CI (opened  8 months ago)
> > https://pagure.io/fedora-ci/general/issue/45
> >
> > RFE: Check if dependent packages install (opened 8 months ago)
> > https://pagure.io/fedora-ci/general/issue/46
> >
> > Support automatic execution of tests of dependent components (opened 1 
> > year ago)
> > https://pagure.io/fedora-ci/general/issue/7
> >
> >
> > And either way, since CI is opt-in, I would need to go and setup CI for 
> > all of
> > dependencies (including transitive) of all my packages. I haven't really
> > checked
> > how big is this tree but I suppose it is enormous.
> >
> >
> > Would an automated daily report (like the broken rawhide deps report that we
> > used to have) help? I could hack that together for different fedora 
> > branches +
> > updates-testing pretty easily, and adding notifications when a broken 
> > dependency
> > gets added in -testing wouldn't be hard either.
>
> I've mostl started this thread to see if I indeed need to script this.
>
> If you could look into it, ut would be awesome.
>
> This is very useful as starting point (rawhide example):
>
> $ sudo dnf --repo=rawhide makecache
> $ installcheck x86_64 /var/cache/dnf/rawhide*.solv*
>
> (Igor has shown this to me at Flock.)
>
> It would probably need some interface that let me filter my packages. And
> multi-repo for released Fedora.
>
> This is what we use for Python 2 in rawhide:
>
> https://github.com/fedora-python/portingdb/blob/master/portingdb/check_fti.py

Oh, I didn't know installcheck existed.
I've used repoclosure to get unsatisfied dependencies for all packages
(including unsatisfied BRs).

My initial work is here:
https://pagure.io/fedora-health-check

I'll set up a cron job to generate and push this data daily.
Once (or if) the list of broken stuff ever gets smaller I can also set
up automated notifications ...

Fabio

> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Miro Hrončok]

On 07. 11. 19 9:55, Fabio Valentini wrote:
On Thu, Nov 7, 2019, 09:25 Miro Hrončok > wrote:


On 06. 11. 19 23:10, Randy Barlow wrote:
 > On Wed, 2019-11-06 at 21:32 +0100, Miro Hrončok wrote:
 >> Is there any good way to get notified about this sort of problems in
 >> timely manner prior to the update being pushed? This is currently not
 >> optimal.
 >
 > I'm not familiar with an existing solution to this problem, but I agree
 > that it is not optimal.
 >
 > I had a chat or three with Brian Stinson about some ways we could deal
 > with problems like this. Today, when we CI packages (i.e., Bodhi
 > gating), we typically just run the tests associated with the package
 > being altered. Brian suggested that we could *also* run the tests of
 > the packages that depend on the package being altered, against the
 > altered package. This way if a change to something (like pyramid) would
 > break a dependent package's tests (such as cornice), then the update
 > for pyramid should get a failed test result on its tests tab. The
 > problem is that this does increase the load on the test system greatly,
 > but perhaps we can get enough hardware to make that OK. Not sure.


Having this sort of CI would be awesome, however it looks like it's not on 
the
top of the TODO list:

RFE: Koschei-like CI (opened  8 months ago)
https://pagure.io/fedora-ci/general/issue/45

RFE: Check if dependent packages install (opened 8 months ago)
https://pagure.io/fedora-ci/general/issue/46

Support automatic execution of tests of dependent components (opened 1 year 
ago)
https://pagure.io/fedora-ci/general/issue/7


And either way, since CI is opt-in, I would need to go and setup CI for all 
of
dependencies (including transitive) of all my packages. I haven't really
checked
how big is this tree but I suppose it is enormous.


Would an automated daily report (like the broken rawhide deps report that we 
used to have) help? I could hack that together for different fedora branches + 
updates-testing pretty easily, and adding notifications when a broken dependency 
gets added in -testing wouldn't be hard either.


I've mostl started this thread to see if I indeed need to script this.

If you could look into it, ut would be awesome.

This is very useful as starting point (rawhide example):

$ sudo dnf --repo=rawhide makecache
$ installcheck x86_64 /var/cache/dnf/rawhide*.solv*

(Igor has shown this to me at Flock.)

It would probably need some interface that let me filter my packages. And 
multi-repo for released Fedora.


This is what we use for Python 2 in rawhide:

https://github.com/fedora-python/portingdb/blob/master/portingdb/check_fti.py

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Fabio Valentini]

On Thu, Nov 7, 2019, 09:25 Miro Hrončok  wrote:

> On 06. 11. 19 23:10, Randy Barlow wrote:
> > On Wed, 2019-11-06 at 21:32 +0100, Miro Hrončok wrote:
> >> Is there any good way to get notified about this sort of problems in
> >> timely manner prior to the update being pushed? This is currently not
> >> optimal.
> >
> > I'm not familiar with an existing solution to this problem, but I agree
> > that it is not optimal.
> >
> > I had a chat or three with Brian Stinson about some ways we could deal
> > with problems like this. Today, when we CI packages (i.e., Bodhi
> > gating), we typically just run the tests associated with the package
> > being altered. Brian suggested that we could *also* run the tests of
> > the packages that depend on the package being altered, against the
> > altered package. This way if a change to something (like pyramid) would
> > break a dependent package's tests (such as cornice), then the update
> > for pyramid should get a failed test result on its tests tab. The
> > problem is that this does increase the load on the test system greatly,
> > but perhaps we can get enough hardware to make that OK. Not sure.
>
>
> Having this sort of CI would be awesome, however it looks like it's not on
> the
> top of the TODO list:
>
> RFE: Koschei-like CI (opened  8 months ago)
> https://pagure.io/fedora-ci/general/issue/45
>
> RFE: Check if dependent packages install (opened 8 months ago)
> https://pagure.io/fedora-ci/general/issue/46
>
> Support automatic execution of tests of dependent components (opened 1
> year ago)
> https://pagure.io/fedora-ci/general/issue/7
>
>
> And either way, since CI is opt-in, I would need to go and setup CI for
> all of
> dependencies (including transitive) of all my packages. I haven't really
> checked
> how big is this tree but I suppose it is enormous.
>

Would an automated daily report (like the broken rawhide deps report that
we used to have) help? I could hack that together for different fedora
branches + updates-testing pretty easily, and adding notifications when a
broken dependency gets added in -testing wouldn't be hard either.

Fabio



> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Miro Hrončok]

On 06. 11. 19 23:10, Randy Barlow wrote:

On Wed, 2019-11-06 at 21:32 +0100, Miro Hrončok wrote:

Is there any good way to get notified about this sort of problems in
timely manner prior to the update being pushed? This is currently not
optimal.


I'm not familiar with an existing solution to this problem, but I agree
that it is not optimal.

I had a chat or three with Brian Stinson about some ways we could deal
with problems like this. Today, when we CI packages (i.e., Bodhi
gating), we typically just run the tests associated with the package
being altered. Brian suggested that we could *also* run the tests of
the packages that depend on the package being altered, against the
altered package. This way if a change to something (like pyramid) would
break a dependent package's tests (such as cornice), then the update
for pyramid should get a failed test result on its tests tab. The
problem is that this does increase the load on the test system greatly,
but perhaps we can get enough hardware to make that OK. Not sure.



Having this sort of CI would be awesome, however it looks like it's not on the 
top of the TODO list:


RFE: Koschei-like CI (opened  8 months ago)
https://pagure.io/fedora-ci/general/issue/45

RFE: Check if dependent packages install (opened 8 months ago)
https://pagure.io/fedora-ci/general/issue/46

Support automatic execution of tests of dependent components (opened 1 year ago)
https://pagure.io/fedora-ci/general/issue/7


And either way, since CI is opt-in, I would need to go and setup CI for all of 
dependencies (including transitive) of all my packages. I haven't really checked 
how big is this tree but I suppose it is enormous.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Re: Getting notified on broken deps from updates-testing

[Randy Barlow]

On Wed, 2019-11-06 at 21:32 +0100, Miro Hrončok wrote:
> Is there any good way to get notified about this sort of problems in
> timely manner prior to the update being pushed? This is currently not
> optimal.

I'm not familiar with an existing solution to this problem, but I agree
that it is not optimal.

I had a chat or three with Brian Stinson about some ways we could deal
with problems like this. Today, when we CI packages (i.e., Bodhi
gating), we typically just run the tests associated with the package
being altered. Brian suggested that we could *also* run the tests of
the packages that depend on the package being altered, against the
altered package. This way if a change to something (like pyramid) would
break a dependent package's tests (such as cornice), then the update
for pyramid should get a failed test result on its tests tab. The
problem is that this does increase the load on the test system greatly,
but perhaps we can get enough hardware to make that OK. Not sure.


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Getting notified on broken deps from updates-testing

[Miro Hrončok]

Hello,

it repeatedly happened to me that I'm notified by Koschei that dozens of my 
packages suddenly fail to resolve build dependencies on a released Fedora.


I usually find out that the broken update was sitting in testing for 7 days 
without any feedback, only to be pushed and receive ex-post feedback from me.


Is there any good way to get notified about this sort of problems in timely 
manner prior to the update being pushed? This is currently not optimal.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org