4 ms·
The problem isn't the warnings and non-fatal errors. In fact, the largest problem is that the noise obscures them. The problem is the pages and pages of "did t
by marcosdumay 5y ago
The problem isn't the warnings and non-fatal errors. In fact, the largest problem is that the noise obscures them.
The problem is the pages and pages of "did that, everything is fine". Since Linux distros stopped optimizing disk usage by omiting the update time of files a couple of decades ago, I haven't seen build tools lose any single step. The failure is never because something that should be done was ignored. Instead, the failure is often because of some non-fatal error that you have no hope of finding because it's mixed with 10k like of "build tool got here" spam.
- gregmac 5y agoActually I totally agree with that. I was being generous in my example, and often what I showed as "Warning" is just a informational-level message. This leads to much more insidious problems like: ....(thousand of lines)... Info: Package X version 1.2.3 successfully added ....(thousand of lines)... Compile error: Unknown type Z Actual problem: Z was added in Package X version 1.3.0, but some other dependency or reference that wasn't updated caused the incorrect version to be loaded.
- marcosdumay 5y agoIf your code has any size, you won't get all that information from a builder log. Even if it is there, if you knew where to look you would have set the version limits correctly from the beginning. Fixing this on your own computer is quite straight forward, you just need to check the dependencies, you don't need the info line. Fixing that kind of problem on the build server is one of the reasons we have all those practices about reproducible compilation. On this specific case, it's a matter of freezing your dependencies.