Is there a better way to troubleshoot rebuild failures? The output of --show-trace
at times is just too verbose and then sometimes inconsistent. I will admit I likely do not understand something. Overall I find the process abrasive and far from intuitive.
For example, I just had an output that was 702 lines. . Run the identical command a second time, and it is a cached failure of an attribute without any pointers.
So I guess my questions are:
- How can I skip the cached failure so I can get back to the verbose output?
- Any tips for digging in on the verbose output? I mean I personally do not find output like the following helpful.
79| vals = map (d: d.value) vdefs;
80| defTypes = map (x: x.type) vals;
| ^
81| sameOrNull = x: y: if x == y then y else null;
… from call site
When I trolled the output originally, I did not find a reference to any of my files in my repo. So I was not sure where to begin.
Well open to suggestions and education. I have to be doing something wrong here and would like to smooth it out. Tips, tricks, process?
Thanks.