#8947 Rawhide builds are not pushed to stable
Closed: Fixed by cverna. Opened by ignatenkobrain.

https://bodhi.fedoraproject.org/updates/FEDORA-2020-0d23d13617

yet another time... Would be nice if you could not close tickets until the root cause is fixed so that I don't have to open a new ticket every few days.


https://bodhi.fedoraproject.org/updates/FEDORA-2020-0d23d13617

That update is in stable, it seems that it took ~12min to get there tho.

yet another time... Would be nice if you could not close tickets until the root cause is fixed so that I don't have to open a new ticket every few days.

You do have to open new tickets you can just reopen old ones :smile:

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, medium-gain, medium-trouble

@cverna now bodhi is down, so the builds are not going to stable either :(

To unblock myself I have done (since update has been signed):

koji tag-build f33 rust-path-dedot-2.0.2-1.fc33
koji untag-build f33-updates-candidate rust-path-dedot-2.0.2-1.fc33
koji untag-build f33-updates-testing-pending rust-path-dedot-2.0.2-1.fc33

I bet this will make bodhi think it is not in stable, so please change DB to think that update is in stable.

Considering: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/27U6YT73556KYW2RIFJO6J2HYMYVP22U/

please change DB to think that update is in stable.

This is not cool, you're creating work for us at a moment where we need less work. This is really not cool. Did you really need these rust packages to land on rawhide within the minute/hour? Couldn't it wait for a while for someone to wake up and try to help there?
Adding work at the moment where we certainly don't lack any is really not considerate.

Did you really need these rust packages to land on rawhide within the minute/hour?

Yes, unlike people that are getting paid to work on Fedora, these times I have very limited amount of time that I can spend on these activities. This is especially complicated when bodhi is not pushing updates few times a week and when regen-repo are either do not start at all or with few hours delay. This time, this package was blocking build of other package that was breaking some other build. Rust ecosystem (semver) requires quite some builds that are dependent on each other, so if any build is taking 10 minutes to be pushed to stable, then 5-15 minutes to kojira (hopefully) notice and regen repo, that's like 15 minutes. On average, I build 2-3 packages in a chain (sometimes much more), just waiting time is almost an hour. When some of this breaks, it can take 1-8 hours until the problem will be fixed.

I understand that all people are busy with DC move, hence I just run regen-repo myself to not bother people with kojira issues. Same I did for bodhi when it was down and just wrote that this is not issue anymore for me so that you can fix it when you have time.

Adding work at the moment where we certainly don't lack any is really not considerate.

As I said, you don't have to fix it now or probably at all (since there are builds that are staying in testing state forever). So even if you fix this after DC move - fine with me.

BTW, it seems that bodhi was able to handle the update on its own (the one where I tagged packages manually): https://bodhi.fedoraproject.org/updates/FEDORA-2020-fb0d368700

Yes, unlike people that are getting paid to work on Fedora,

This is unfair

As I said, you don't have to fix it now or probably at all

I'm confused here, I'm not seeing this said here and I figure the goal of a ticket is to ask for something to be done/fixed, is it not?

That being said, I'm glad you have the knowledge and permissions to unblock yourself and keep contributing. I'm sorry that the current situation is not ideal and I wish we could improve it, but I doubt we can dedicate cycles to it before the end of the colo move.

I'm confused here, I'm not seeing this said here and I figure the goal of a ticket is to ask for something to be done/fixed, is it not?

Yes, but at any convenient time, not something immediately.

That being said, I'm glad you have the knowledge and permissions to unblock yourself and keep contributing. I'm sorry that the current situation is not ideal and I wish we could improve it, but I doubt we can dedicate cycles to it before the end of the colo move.

:heavy_check_mark: :thumbsup:

So, can we close this one now? I think things have been processing normally for a while now?

yeah let's close

Metadata Update from @cverna:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata