On Wed, 2017-02-22 at 17:45 +0100, GERHARD GOETZHABER wrote:
> Is it really that heavy work to make proper install scripts? ("Can't
> find install class")
Yes. Yes it is. An operating system installer is a fundamentally
complex thing, and Fedora's is required to have a rather large number
of additional complex features. Note that anaconda itself did not
change at all yesterday. It's most likely that the breakage was caused
by a change in the behaviour of a library anaconda uses, or a change in
the behaviour of another package which relates to how the install
classes are provided. I saw this failure last night but didn't have
time to debug it yet; note we *do* have automated testing of all
Rawhide composes, so this kind of failure is usually caught quite
quickly. You'll see the 'Fedora Rawhide-20170221.n.1' and 'Fedora
Rawhide-20170222.n.0' 'compose check reports' lists 60/85 failures,
compared to the 20170220.n.2 report which listed 11/85 failures; that's
due to this bug. You can also see that
https://www.happyassassin.net/nightlies.html lists all the 0222.n.0
images in red and links to failures caused by this bug.
BTW, it's good to have feedback, but it's quite impolite to the people
who work on the tools to ask questions in this kind of way, implying
that they're incompetent or stupid. Please don't do it in future. Also,
when what you've found is clearly a bug, a bug report is usually much
more use than a post to this mailing list: most maintainers /
developers do not read this list, so you would not be directly alerting
them to the problem. The list is mainly here for discussion between
testers - say you're not sure if something qualifies as a bug, or you
want to know if other testers are seeing the same thing, or you want to
discuss testing procedure, and so on.
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
