Re: Strange koji failures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2016-12-22, Pavel Raiskup <praiskup@xxxxxxxxxx> wrote:
> On Thursday, December 22, 2016 9:50:12 AM CET Vít Ondruch wrote:
>> 
>> Dne 22.12.2016 v 09:27 Mikolaj Izdebski napsal(a):
>> > On 12/22/2016 05:06 AM, Christopher wrote:
>> >> The failure yesterday that I was thinking of was:
>> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=17004112
>> >>
>> >> Re-submitting it 4 minutes later passed just fine:
>> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=17004125
>> > These builds were ran on different architectures - the first one on
>> > aarch64 and the second one - x86_64. nodejs package is available only on
>> > x86_64, so failure on aarch64 was expected.
>> >
>> 
>> Honestly this is annoying misbehavior. How we can tell Koji to avoid
>> certain builders for certain noarch packages?
>
> There used to be a koji target for documentation, using that caused that
> 'x86_64' or 'i686' builders were chosen.  But it seems those are not there
> anymore.
>
>> Wouldn't be possible to build noarch packages just on primary arch builders
>> for example?
>
> Those arches are all primary .. but ExclusiveArch could help.
>
No, it does not. I have noarch perl-Alien-ROOT with ExclusiveArch and
I still receive reports about broken compose and Koschei reports build
failures when koji picks up unlisted archictecture.

-- Petr
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux