According to this job http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16147 it seems that we're running checks on EPEL tags. I assume that is some kind of mistake, because IIRC we don't want to complicate things with EPEL just yet.
I guess the problem is in trigger - it reacts to fedmsg notifications which it should ignore. Please find the problem and disable EPEL scheduling.
This ticket had assigned some Differential requests: D226
More affected jobs, with different outputs: http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16328/ http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16459 http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16604 http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16628 http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16638 http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16644 http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16703 http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16743 http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16761 http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/16935 ...
This might be related to why we suddenly see EPEL tags: https://github.com/fedora-infra/bodhi/pull/87/files
It seems the name is no longer "ELx", but also "EPELx".
See more: https://lists.fedoraproject.org/pipermail/infrastructure/2014-August/014720.html
This might be related to why we suddenly see EPEL tags: https://github.com/fedora-infra/bodhi/pull/87/files It seems the name is no longer "ELx", but also "EPELx". See more: https://lists.fedoraproject.org/pipermail/infrastructure/2014-August/014720.html
Yeah, but that's a bodhi change and shouldn't be related to the issue as far as I know. I have a patch ready (regression...) and will send it for review shortly.