Page MenuHomePhabricator

Bug 1765361: Only resolve objdir from virtualenv if mozinfo not ancestor
ClosedPublic

Authored by mhentges on Apr 19 2022, 4:43 PM.
Referenced Files
Unknown Object (File)
Sun, Oct 12, 8:13 PM
Unknown Object (File)
Fri, Oct 10, 7:09 PM
Unknown Object (File)
Sep 15 2025, 4:25 AM
Unknown Object (File)
Sep 7 2025, 9:33 AM
Unknown Object (File)
Aug 11 2025, 1:23 AM
Unknown Object (File)
Jul 14 2025, 4:20 AM
Unknown Object (File)
Jul 6 2025, 1:59 AM
Unknown Object (File)
May 12 2025, 6:20 PM
Subscribers
None

Details

Summary

Virtualenv-based objdir detection doesn't work for instrumented builds,
as instrumentation-specific objdirs aren't created.

Resolve this by:

  • Removing redundant cwd-based topsrcdir resolution - the __file__-based code path below covers this case.
  • Only using virtualenv-based resolving if topsrcdir isn't resolved.
  • Documenting that virtualenv-based resolution is problematic for instrumented builds.

Diff Detail

Event Timeline

phab-bot changed the visibility from "Custom Policy" to "Public (No Login Required)".
phab-bot changed the edit policy from "Custom Policy" to "Restricted Project (Project)".
phab-bot removed a project: secure-revision.
mhentges edited the summary of this revision. (Show Details)
This revision is now accepted and ready to land.Apr 26 2022, 5:34 AM

This revision requires a Testing Policy Project Tag to be set before landing. Please apply one of testing-approved, testing-exception-unchanged, testing-exception-ui, testing-exception-elsewhere, testing-exception-other. Tip: this Firefox add-on makes it easy!

This revision is now accepted and ready to land.Apr 26 2022, 3:22 PM

I've added a windows-specific capitalize() call to work around these failures.

It doesn't smell very good that you need this capitalization...

This revision is now accepted and ready to land.May 3 2022, 6:32 AM