Closed
Bug 1044657
Opened 10 years ago
Closed 10 years ago
Move PYTHON_UNIT_TESTS to moz.build
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla34
People
(Reporter: Ms2ger, Assigned: Ms2ger)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
Attachments
(1 file)
12.55 KB,
patch
|
mshal
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•10 years ago
|
||
As a first step, this moves PYTHON_UNIT_TESTS to moz.build as a passthru
variable. In the future, we could hook it up to |mach test|.
Attachment #8463163 -
Flags: review?(mshal)
Assignee | ||
Comment 2•10 years ago
|
||
Comment 3•10 years ago
|
||
Comment on attachment 8463163 [details] [diff] [review]
Move PYTHON_UNIT_TESTS to moz.build
>+PYTHON_UNIT_TESTS += [
>+ '../build/compare-mozconfig/compare-mozconfigs-wrapper.py',
>+]
Any idea if we can move this into build/moz.build? Seems weird to have it referenced from browser (although the mozconfigs it checks are under browser, the test is in build).
>+PYTHON_UNIT_TESTS += [
>+ 'mach/mach/test/__init__.py',
Do we really need all of these __init__.py files? Or things like common.py?
Attachment #8463163 -
Flags: review?(mshal) → review+
Comment 4•10 years ago
|
||
(In reply to Michael Shal [:mshal] from comment #3)
> Any idea if we can move this into build/moz.build? Seems weird to have it
> referenced from browser (although the mozconfigs it checks are under
> browser, the test is in build).
The intent was to only run them under Firefox builds, IIRC, so sticking them under browser/ was the simplest way to accomplish that. We could move this to build/ and just check CONFIG['MOZ_APP_NAME'] instead.
Assignee | ||
Comment 5•10 years ago
|
||
Comment 6•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Updated•10 years ago
|
QA Whiteboard: [qa-]
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•