You should use ./mach mochitest-* to run mochitests.
Gavin
On Mon, Aug 18, 2014 at 4:45 PM, Neil wrote:
> Time was that you could just python runtests.py to run mochitests.
>
> Then we needed modules that you don't get in the default python, so you had
> to invoke python from the virtualenv inst
On 8/18/2014 4:45 PM, Neil wrote:
> Time was that you could just python runtests.py to run mochitests.
>
> Then we needed modules that you don't get in the default python, so you
> had to invoke python from the virtualenv instead.
>
> Now that doesn't work either, because it's trying to run .mozc
On 19.08.2014 01:19, Nicholas Nethercote wrote:
Hi,
I wrote a blog post about a bug that was hard to diagnose because it
involved a rarely-used cookie-related preference
(https://blog.mozilla.org/nnethercote/2014/08/15/the-story-of-a-tricky-bug/).
One of the commenters made an interesting sugges
Time was that you could just python runtests.py to run mochitests.
Then we needed modules that you don't get in the default python, so you
had to invoke python from the virtualenv instead.
Now that doesn't work either, because it's trying to run .mozconfig, so
my questions are a) why and b) h
I seem to remember that the SUMO folk had an add-on that would install
restartlessly and gather system info to pass along to them. I don't
remember the specifics though.
On Mon, Aug 18, 2014 at 4:19 PM, Nicholas Nethercote wrote:
> Hi,
>
> I wrote a blog post about a bug that was hard to diagno
Nicholas Nethercote wrote:
One of the commenters made an interesting suggestion: some kind of about:config
export tool that would make it easier for Firefox devs to reproduce these kinds
of problems.
The profile prefs.js only contains the modified preferences, if that's
all you need.
--
Hi,
I wrote a blog post about a bug that was hard to diagnose because it
involved a rarely-used cookie-related preference
(https://blog.mozilla.org/nnethercote/2014/08/15/the-story-of-a-tricky-bug/).
One of the commenters made an interesting suggestion: some kind of
about:config export tool that w
The next MemShrink meeting will be brought to you by the Asynchronous Pan/Zoom
Controller (APZC) not leaking testing data when disabled:
https://bugzilla.mozilla.org/show_bug.cgi?id=1041751
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioriti
Hi!
Structured logging[1] for mochitest (along with other test suites) has landed
and this could affect some of your scripts/workflows.
Since the test harness now generates structured JSON logs instead of formatted
strings, you can use different formatters to format your logs. [2]
The followin
On 8/15/14, 1:03 AM, Gijs Kruitbosch wrote:
> On 15/08/2014 07:17, Jeff Walden wrote:
>> I think our best bet is probably to evangelize the change hard,
>> update AMO linters to flag the issue, and (gulp) wait for, and assist
>> wherever possible, addon authors to update their code. Part #1,
>> sh
Bobby Holley writes:
[...]
> If you find yourself itching to do something complicated, write a
> mochitest-chrome test. The default template [2] now generates html files
> (rather then XUL files), so the ergonomics there should be easier than
> before.
>
> If you don't want to write a mochitest-ch
11 matches
Mail list logo
