Closed Bug 1680584 Opened 4 years ago Closed 4 years ago

profileserver.py failures aren't shown when doing full PGO build

Categories

(Firefox Build System :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mhentges, Assigned: sheehan)

References

Details

Attachments

(1 obsolete file)

When doing MOZ_PGO=1, as documented here Firefox does :

  1. [subprocess, pipe output] Perform a Firefox build that will generate performance stats
  2. [subprocess, check_call] Run a bunch of tests with the built Firefox to get performance stats
  3. [subprocess, pipe output] Perform a Firefox build using the generated performance stats

Unfortunately, if step 2 (profilerserver.py) fails, then the output isn't shown, so it's hard to debug.
We should pipe the output of profileserver.py so debugging profiling failures is easier.

Priority: -- → P3
See Also: → 1680306
Assignee: nobody → sheehan

Switches the invocation of profileserver.py from using subprocess.check_call
to subprocess.run. Checks the return code of the profileserver process and
returns it if it is non-zero. profileserver.py only prints output to the
screen when it encounters an error, so this change shouldn't cause any new
output during the build unless an error is encountered.

Attachment #9191207 - Attachment is obsolete: true

After taking a closer look it seems the errors are indeed displayed when doing a full PGO build.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: