On Fri, 15 Jan 2021 16:29:11 +0100 Lukas Ocilka <[email protected]> wrote:
> Hi guys, > > I've already mentioned this at some calls before, but this is actually > the right channel for discussing the idea. > > I've seen many times before, that there is, for instance, a media layout > error, but we simply report that problem into the log and try to > continue. Usually it's nothing critical in our eyes. As an example, > we've recently seen that someone reported a missing Czech license in > installer. Ladislav found out that the license actually exists, but > wrongly uses "cz" instead of "cs" in its filename. The installer > actually reported a warning into the log. Something like "unknown > language 'cz'". > > So, what is the problem? It could have been spotted 3 months earlier. > Plus it could have been fixed without us debugging the problem. > > Proposed solution: In case of Y2DEBUG==1, raise an internal error or > rather show a pop-up error/warning message. This would not influence > common installations, but openQA would catch and record it. With a > little piece of work openQA could even skip it if needed. I would like > to have a separate Y2SOMETHING variable to control the behavior (by > default, X==1 in case of Y2DEBUG==1). > > Obviously, this means more work now and from time to time for adding > such warning/error reports one by one. But that IMO pays off mid-to-long > term. At the end we could have more time to fix "our" bugs :) > > What do you think? > Thx > Lukas I quite like idea. Something like assert call in C which check conditions and if it failed then it log warning or raise exception depending on ENV variable. Josef
