PSA: Android Hardware testing on Try only available via mach try fuzzy

2018-12-21 Thread Bob Clary 

To help cut down on inadvertent invocations of tests on the limited
Android hardware, I've landed Bug 1515599 - Prevent android hardware
tests from running when using try option syntax on mozilla-inbound.

If you actually want to run tests on Android hardware, you must use
mach try fuzzy.

See

for details on installing and running mach try fuzzy.

You can easily see the available tests via

$ ./mach try fuzzy --no-push --full --query "android-hw"
Commit message:
Fuzzy query=android-hw

Pushed via `mach try fuzzy`
Calculated try_task_config.json:
{
"tasks": [

"test-android-hw-g5-7-0-arm7-api-16/opt-raptor-speedometer-geckoview-e10s",

"test-android-hw-g5-7-0-arm7-api-16/opt-raptor-speedometer-geckoview-power-e10s",

"test-android-hw-g5-7-0-arm7-api-16/opt-raptor-unity-webgl-geckoview-e10s",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-1",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-10",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-2",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-3",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-4",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-5",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-6",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-7",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-8",
"test-android-hw-p2-8-0-android-aarch64/opt-jittest-9",

"test-android-hw-p2-8-0-android-aarch64/opt-raptor-speedometer-geckoview-e10s",

"test-android-hw-p2-8-0-android-aarch64/opt-raptor-speedometer-geckoview-power-e10s",
"test-android-hw-p2-8-0-arm7-api-16/debug-mochitest-media-1",
"test-android-hw-p2-8-0-arm7-api-16/debug-mochitest-media-2",
"test-android-hw-p2-8-0-arm7-api-16/debug-mochitest-media-3",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-1",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-10",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-2",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-3",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-4",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-5",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-6",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-7",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-8",
"test-android-hw-p2-8-0-arm7-api-16/opt-jittest-9",
"test-android-hw-p2-8-0-arm7-api-16/opt-mochitest-media-1",
"test-android-hw-p2-8-0-arm7-api-16/opt-mochitest-media-2",
"test-android-hw-p2-8-0-arm7-api-16/opt-mochitest-media-3",

"test-android-hw-p2-8-0-arm7-api-16/opt-raptor-speedometer-geckoview-e10s",

"test-android-hw-p2-8-0-arm7-api-16/opt-raptor-speedometer-geckoview-power-e10s",

"test-android-hw-p2-8-0-arm7-api-16/opt-raptor-unity-webgl-geckoview-e10s"
],
"templates": {
"env": {
"TRY_SELECTOR": "fuzzy"
}
},
"version": 1
}

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

Re: nasm will soon become a build dependency

2018-12-21 Thread Kartikaya Gupta 
Looks like the default nasm in the Ubuntu 16.04 repositories is 2.11.
Are there plans to make `./mach bootstrap` find a 2.13 version from
somewhere, instead of just installing via `apt-get` and assuming it's
the right version?


On Fri, Dec 21, 2018 at 12:00 AM Thomas Daede  wrote:
>
> On 12/20/18 8:17 PM, Martin Thomson wrote:
> > The OP said >= 2.10.  But you appear to have that.
>
> At the time of writing it was, but we now need 2.13. The configure
> script doesn't check for that either, I will make a note of it in the
> bug to fix this detection.
>
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to Implement and Ship: break-before, break-after, break-inside CSS properties

2018-12-21 Thread Eric Shepherd (Sheppy) 
I just now saw this; as both a developer and as a writer on the MDN docs
team, I can tell you this will really be fantastic to have, and I can’t
wait! Not having control over breaks makes a lot of layout fail, especially
when trying to use multiple columns or grids to do layout.

On December 7, 2018 at 9:12:39 AM, Emilio Cobos Álvarez (emi...@crisal.io)
wrote:

Summary: Implement these properties to control breaks in the page, make
page-break-{before,after} legacy shorthands of those.


Eric Shepherd
Senior Technical Writer
MDN Web Docs 
Blog: https://www.bitstampede.com/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to Implement and Ship: break-before, break-after, break-inside CSS properties

2018-12-21 Thread Emilio Cobos Álvarez 



On 12/21/18 7:23 PM, Eric Shepherd (Sheppy) wrote:

I just now saw this; as both a developer and as a writer on the MDN docs
team, I can tell you this will really be fantastic to have, and I can’t
wait! Not having control over breaks makes a lot of layout fail, especially
when trying to use multiple columns or grids to do layout.


FWIW Firefox allows you to control breaks as well (even before my 
change) via the page-break-* properties (which we honored too for 
non-paginated contexts).


But yeah, this should make the whole setup much clearer, and allow 
people to write interoperable CSS too :)


 -- Emilio


On December 7, 2018 at 9:12:39 AM, Emilio Cobos Álvarez (emi...@crisal.io)
wrote:

Summary: Implement these properties to control breaks in the page, make
page-break-{before,after} legacy shorthands of those.


Eric Shepherd
Senior Technical Writer
MDN Web Docs 
Blog: https://www.bitstampede.com/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


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

Re: nasm will soon become a build dependency

2018-12-21 Thread Thomas Daede 
On 12/21/18 8:08 AM, Kartikaya Gupta wrote:
> Looks like the default nasm in the Ubuntu 16.04 repositories is 2.11.
> Are there plans to make `./mach bootstrap` find a 2.13 version from
> somewhere, instead of just installing via `apt-get` and assuming it's
> the right version?

There is a toolchain build for nasm for windows:
https://bugzilla.mozilla.org/show_bug.cgi?id=1511224

If getting a newer nasm version is inconvenient for a majority of linux
users, the toolchain build could be used to produce nasm binaries for
mach bootstrap as well.

(I forgot to mention, you can also --disable-av1 as a temporary workaround)
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: nasm will soon become a build dependency

2018-12-21 Thread Kartikaya Gupta 
On Fri, Dec 21, 2018 at 4:10 PM Thomas Daede  wrote:
> There is a toolchain build for nasm for windows:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1511224
>
> If getting a newer nasm version is inconvenient for a majority of linux
> users, the toolchain build could be used to produce nasm binaries for
> mach bootstrap as well.

I would certainly prefer this, and having this work smoothly would
also be good for new contributors. Having to build and install extra
packages is always a hassle.

> (I forgot to mention, you can also --disable-av1 as a temporary workaround)

Good to know, thanks. Although I already had to get 2.13 to unblock my build.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Better incremental builds - Tup backend available on Linux

2018-12-21 Thread kmoir 
On Friday, September 28, 2018 at 3:56:45 PM UTC-4, Michael Shal wrote:
> Hi everyone,
> 
> Tup is a modern build system that enables fast and correct builds. I'm
> pleased to announce the availability of Tup for building Firefox on Linux.
> Compared to Make, building with Tup will result in faster incremental build
> times and reduce the need for clobber builds. See the in-tree docs for
> details [1].
> 
> We announced this on dev-builds[2] a few weeks ago, and addressed much of
> the feedback from early adopters. Now we’re looking for more users to try
> it out and let us know what issues you have, and whether or not it improves
> your development workflow.
> 
> Quick howto:
> 
> You’ll need to install the Tup executable, as well as the nightly
> rust/cargo toolchain:
> 
> cd ~/.mozbuild && mach artifact toolchain --from-build linux64-tup
> rustup default nightly-2018-09-16
> 
> *  Note that normally “rustup default nightly” would suffice, but until
> https://github.com/rust-lang/cargo/issues/6082 is in nightly, try
> 2018-09-16 for now.
> 
> Your mozconfig needs to describe how to find the executable if it’s not in
> your PATH, and enable the Tup backend:
> 
> export TUP=~/.mozbuild/tup/tup
> ac_add_options --enable-build-backends=Tup
> 
> If you have any issues, feel free to file a bug blocking “buildtup” [3], or
> contact mshal or chmanchester in #build on IRC.
> 
> [1] https://firefox-source-docs.mozilla.org/build/buildsystem/tup.html
> 
> [2]
> https://groups.google.com/d/msg/mozilla.dev.builds/c4rxss-ScmM/8M8fo_uzDAAJ
> 
> [3] https://bugzilla.mozilla.org/show_bug.cgi?id=buildtup
> 
> Thanks!
> 
> -Mike

Thank you to everyone for your work to test this new build backend.  We have 
put this work on hold for now as we address on other priorities.  We will have 
an update on the state of this work in early 2019.

Thanks,
Kim
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: nasm will soon become a build dependency

2018-12-21 Thread Mike Hommey 
On Fri, Dec 21, 2018 at 04:21:03PM -0500, Kartikaya Gupta wrote:
> On Fri, Dec 21, 2018 at 4:10 PM Thomas Daede  wrote:
> > There is a toolchain build for nasm for windows:
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1511224
> >
> > If getting a newer nasm version is inconvenient for a majority of linux
> > users, the toolchain build could be used to produce nasm binaries for
> > mach bootstrap as well.
> 
> I would certainly prefer this, and having this work smoothly would
> also be good for new contributors. Having to build and install extra
> packages is always a hassle.

It's a hassle downstream too.

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

Re: nasm will soon become a build dependency

2018-12-21 Thread Thomas Daede 
On 12/21/18 3:09 PM, Mike Hommey wrote:
> On Fri, Dec 21, 2018 at 04:21:03PM -0500, Kartikaya Gupta wrote:
>> I would certainly prefer this, and having this work smoothly would
>> also be good for new contributors. Having to build and install extra
>> packages is always a hassle.
> 
> It's a hassle downstream too.
> 
> Mike
> 

Not sure what I can do for downstream though - afaik most Linux distros
don't use any of our toolchain builds?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform