Re: firefox build failure

On 1/11/20 7:44 PM, Botond Ballo wrote: Thanks. So, the header file is indeed missing the declaration of the method InitSandboxTesting(). That suggests that, at the time it was generated, this condition [1] was false. Is it possible that you added "--enable-debug" after the build was first start

Re: firefox build failure

On 1/11/20 6:55 PM, Botond Ballo wrote: Could you post the generated header file mozilla-central/obj-x86_64-pc-linux-gnu/ipc/ipdl/_ipdlheaders/mozilla/gfx/PGPUChild.h ? Thanks, Botond The file is attached. ___ dev-builds mailing list dev-builds@lists

Re: firefox build failure

On 1/11/20 6:05 PM, Botond Ballo wrote: Hi Dave, On Sat, Jan 11, 2020 at 8:35 PM Dave wrote: I am a newbie trying to build mozilla-central on debian/Buster but I am running into a compiler error. I have run bootstrap.py and have the pulled and updated as of this email. I am running ".

firefox build failure

ere\u001b[0m"}] [1578780962.16122, "build_output", {"line": "mSandboxTestingParents[type] = InitializeSandboxTestingActors(gpuChild);"}] [1578780962.161462, "build_output", {"line": "\u001b[0;1;32m ^&q

Supporting tests generated as part of the build in test manifests

I just posted about a plan to switch the Jetpack tests to be more like the other test suites in the tree including using manifests to define tests ( https://groups.google.com/d/msg/mozilla.dev.tree-management/QquG-CNvmgU/Z8A67brrSjgJ). I'm hitting a problem with our testaddons tests though. This p