Closed Bug 1570515 Opened 5 years ago Closed 5 years ago

clang toolchain build logs are essentially empty

Categories

(Firefox Build System :: Toolchains, defect)

defect
Not set
normal

Tracking

(firefox70 fixed)

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: glandium, Assigned: glandium)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Bug 1546136 wrapped process execution logs to capture cmake output. But it did so by capturing the output of all subprocesses. And their output is only printed out if they are failures (also, stderr is hidden entirely).

Bug 1546136 wrapped subprocess execution output to capture cmake's, but
at the detriment of other output, and hiding everything unless an error
occurs.

So instead, we only capture the output when the called process is cmake,
and even when it is cmake, we don't pipe stderr at all (since we only
care about cmake's stdout) and we print out stdout as it comes in rather
than later. We then later check the output for hints at the more useful
cmake logs and dump them.

While here, add verbosity to ninja output (which gives the command
lines, rather than generic "Building foo.o" output).

Blocks: 1570564
Pushed by mh@glandium.org:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6ef2d2e3f4b9
Change how build-clang.py consumes subprocess output. r=froydnj
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
Regressions: 1571576
Has Regression Range: --- → yes
Keywords: regression
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: