known_fail should not be seen as a build success

[kencu]

when a port sets known_fail on a system version, it should be displayed as a fail in the webapp, not a success

[mascguy]

I'd prefer that we have a 3rd status - like "not supported," or something akin to that - to differentiate from a simple success/failure.

Anyone else... thoughts?

[kencu]

Anything but success

[jmroot]

AFAIK, you currently see the grey question mark for known_fail ports, since no build takes place. An indicator that it is known to fail rather than just not built would be nice.

Of course if there was a successful build of a previous version, #135 will be in effect.

[mascguy]

Similarly, if there was at least one build failure prior to setting known_fail, that will also be in effect.

And that can be a bit frustrating, when drilling down the dependency tree.

[ryandesign]

AFAIK, you currently see the grey question mark for known_fail ports, since no build takes place. An indicator that it is known to fail rather than just not built would be nice.

Only if no build of that port (any version) has ever taken place on that builder. If a build has taken place in the past, then that information is displayed by the web app even if it is outdated. Ideally the web app would not display outdated information.

[jmroot]

Yes, hence the reference to #135.