@gicmo it looks like we had some Jenkins outage at that time and the tests were not triggered... I've triggered them manually now.

@msrb @jimbair it looks like our Jenkins didn't trigger at all, do you have any idea how do we keep missing messages?

@bgoncalv I'm not sure and I agree with you after looking around a little bit that we're best suited to focus these efforts once we migrate to our new cluster/jenkins instance(s), which should hopefully be less prone to failures like this.

@gicmo if you run into another failure like this, please open an issue and let us know or ping us in #fedora-ci in freenode and we'll retrigger and see if it's something obvious. Thanks!