Ticket #207 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

post-koji-build watcher does not watch for new updates-candidate builds

Reported by: kparal Owned by: jlaska
Priority: major Milestone: Hot issues
Component: watchers Keywords:
Cc: Blocked By:
Blocking:

Description

I have found out that our post-koji-build watches only these tags:

dist-f10 dist-f10-updates dist-f10-updates-testing dist-f11 dist-f11-updates dist-f11-updates-testing dist-f12 dist-f12-updates dist-f12-updates-testing dist-f13 dist-f13-updates dist-f13-updates-testing dist-f14

Which is incorrect, we should be watching dist-f*-updates-candidate (and maybe dist-f14, I don't know). We don't need to watch for the rest of it.

The change happened in commit 580734d4f2aa768aefa1c0498904df2296747918. See the diff and inspect current contents of repoinfo.conf to grasp the change.

The result is that we don't currently test almost any packages except f14 ones. Do we have it already deployed on our production machine?

What we can do about it? Well, I hope someone with a deep understanding of repoinfo stuff knows what's the best approach :) It seems to me that we could define the *-updates-testing repositories in repoinfo.conf (and make sure we didn't break something else) and retrieve and select just those in watch-koji-builds.

Change History

comment:1 in reply to: ↑ description Changed 4 years ago by jlaska

Replying to kparal:

I have found out that our post-koji-build watches only these tags:

dist-f10 dist-f10-updates dist-f10-updates-testing dist-f11 dist-f11-updates dist-f11-updates-testing dist-f12 dist-f12-updates dist-f12-updates-testing dist-f13 dist-f13-updates dist-f13-updates-testing dist-f14

Which is incorrect, we should be watching dist-f*-updates-candidate (and maybe dist-f14, I don't know). We don't need to watch for the rest of it.

The change happened in commit 580734d4f2aa768aefa1c0498904df2296747918. See the diff and inspect current contents of repoinfo.conf to grasp the change.

Uh oh, that's my commit :( Great catch.

I thought we ironed this out when we revised repoinfo.conf and cleaned up the koji watcher methods. But I recall thinking that this was another hook that could use a test framework to aid in validating changes (different topic). I'm seeing fc14, fc13 and fc12 builds on autoqa-results@…. But as you point out, the hook is skipping any dist-f*-updates-candidate builds. I *wonder* if this is intentional for the hook but I could be very wrong.

Since I always have a hard time walking through the koji and bodhi hooks, where the test data changes constantly, I added some extra debugging to the hook to find a sample build. A good sample build that was skipped is fwbackups-1.43.3-0.9.rc5.fc12 (tag: dist-f12-updates-testing). This build was submitted to F12 updates-testing, and pushed on 2010-07-05 (see bodhi).

A *quick* fix is to add config sections to repoinfo.conf for [f13-updates-candidate]. While in my testing this includes the desired builds, I'm not sure that's the right fix since repoinfo is for package repositories, and there is no updates-candidate repository.

The result is that we don't currently test almost any packages except f14 ones. Do we have it already deployed on our production machine?

Yes, v0.3.5 includes this change (http://git.fedorahosted.org/git/?p=autoqa.git;a=shortlog;h=refs/tags/v0.3.5-1).

comment:2 Changed 4 years ago by kparal

  • Milestone changed from Package Update Acceptance Test Plan to Hot issues

comment:3 Changed 4 years ago by jlaska

  • Owner set to jlaska

Taking ownership. I've corrected this issue. Watch autoqa-devel for a patch.

comment:4 Changed 4 years ago by kparal

  • Status changed from new to closed
  • Resolution set to fixed

This has been pushed to master few days ago. Thanks jlaska!

Note: See TracTickets for help on using tickets.