Closed Bug 999020 Opened 10 years ago Closed 9 years ago

customizing .mozconfig used w/mozregression -- generating non-debug builds with mozregression?

Categories

(Testing :: mozregression, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: wlach, Unassigned)

References

Details

[import from github]

stepheneb:

I'm using mozregression to track down a performance regression in SVG. 

I'd like to specify the .mozconfig settings used by mozregression to:

- disable debug
- disable tests

And to make it run faster MOZ_MAKE_FLAGS should use 4 cores.

I edited `~    ./moz-commitbuilder-cache/mozbuild-trunk/obj-ff-dbg/.mozconfig` as follows:

    mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-ff-dbg
    ac_add_options --disable-optimize
    ac_add_options --disable-debug
    ac_add_options --disable-tests
    mk_add_options MOZ_MAKE_FLAGS="-s -j 4"

But when I run mozregression the the `.mozconfig` Is re-written:

Example output from console:

    Testing changeset 108541:6c68ef18d340 (104 changesets remaining, ~6 tests)
    198 files updated, 0 files merged, 64 files removed, 0 files unresolved

    Configuring mozconfig:
    Configured to run with 1 cores.

    Building...

I skimmed the code looking for what is running when this console message is generated ... but didn't see it:

    Configuring mozconfig:

stepheneb:

Learning more about these tools I tried using mozcommitbuilder directly specifying a custom mozconfig and that is working:

    mozcommitbuilder --good=2012-09-28 --bad=2012-09-29 -m ~/dev/mozconfig
See Also: → 1096244
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.