Hi,

I would agree with the folks in #introduction that it's OK if it passes on try, and that you can generally run the tests relevant to your work if you're doing things locally. When in doubt about test coverage, you should always be able to ask the person mentoring you and/or the bug in question.

If you feel like it, you could try to figure out why the error in question happens in the automated test run on your machine - it might be a real problem, but with the information we have so far it's hard to be sure what the issue is. If you want to dive into this further, it'd probably be useful to file a bug (product: Firefox, component: Toolbars & Customization) and provide more details, such as if you're "just" building Firefox desktop, or Fx OS simulator, or something else, whether this is an opt or debug build, if you can reproduce the issue when running just one or two tests, what the stack for the error is, and anything else you think is relevant. If you decide to do this, please feel free to CC/needinfo me and we can take it from there.

Hope that helps,
Gijs

On 28/05/2014 17:49, thills wrote:
Hi Gijs,

I'm still seeing this even when I don't use the sudo.

I also asked about this on the #introduction a few days ago and it was mentioned that if this was a real issue, it would be something seen also on the try servers. The advice they gave me was to just try running the specific tests needed to test my work vs. the whole suite. This is a bit concerning to me as a newbie as I want to make sure I've got all the proper tests chosen.

Thanks,

-tamara

On 5/26/14, 8:44 AM, Gijs Kruitbosch wrote:
On 22/05/2014 14:56, thills wrote:
Hi Gijs:
Thanks for your response.  Please see inline.
On 5/22/14, 9:46 AM, Gijs Kruitbosch wrote:
Some questions:

What platform is this on?
This is on Mac OSX Mavericks
How are you invoking the test suite?
I'm doing a sudo ./mach mochitest-browser from the command line.
Don't use sudo. :-)


Which test is running when this error happens?
The test that executes right before is this one:
6:17.02 TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_932928_show_notice_when_palette_empty.js | The empty palette notice should not be shown when there are items in the palette.

After that executes, it gets stuck in this loop just repetitively printing out that error with the type error below.
Are you using mozilla-central, fx-team, mozilla-inbound, ...?
I'm using mozilla-central.
Can you paste a copy of your .mozconfig configuration?
It's empty

Please let us know (on the newsgroup/mailing list as well - I've looped them back in) if you're still seeing this if not using sudo.

~ Gijs


_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to