Unplanned Phabricator Update - June 4th 2019 between 14:00 and 15:00 UTC
Due to missing the normal update window normally on Mondays, we will be deploying a Phabricator update to add new functionality tomorrow June 4th between 14:00 and 15:00 UTC (10:00am ET). Upgrades usually have no visible impact on the user; however, some updates may cause Phabricator to be partially unavailable during this window. If you have any questions about this, we’re available in #phabricator on slack for any questions and concerns. Regards, David Lawrence Engineering Workflow Team. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Did Firefox's JS Debugger improve for you?
Hi everyone, Tl;dr: Please help us with testing/feedback on Firefox DevTools after we fixed long-standing performance & quality issues in Firefox’s JavaScript debugging capabilities. During Firefox development, from platform to frontend to web compat, JavaScript debugging is a key aspect and needs to be rock solid. Responding to your feedback, we (the Firefox DevTools team) have put in tremendous effort to make all aspects of the Debugger more reliable, faster and convenient. Firefox 67 and 68 is where a lot of this work comes together: # 1. Debug workers within the debugger without a new toolbox Fast web applications depend on concurrency, but DevTools’ worker support has been clunky at best. Now you can switch between workers in a new Debugger panel and see their source files along the other sources – all in the Debugger without opening a new toolbox. # 2. Set breakpoints on lines and columns (aka Column/Inline Breakpoints) Pausing on columns, not just lines, provides much needed accuracy for pausing in the right locations and into minified code. To make this work we refactored all aspects of how pausing locations are determined and used; with a focus on performance and reliability. # 3. Set breakpoints to log messages (aka LogPoints) Lets you switch breakpoints to print message and variables to the Console instead of pausing code execution. This can give you superpowers for tricky situations, like when pausing would break the test case or where source code can’t be edited. # 4. Significantly improved quality for breakpoints, stepping & overall performance We have been burning through a backlog of long-standing issues that made debugging feel flaky and slow in some situations. No more losing breakpoints, stepping into wrong functions! Meanwhile our source maps, the glue that makes modern web apps debuggable, took over other devtools. We will keep honing the foundations of the debugger, making it more reliable and faster with every release. Those changes touched major parts of the server and frontend. We need your help now with testing the Debugger against your projects, Firefox, extension, or web, and providing feedback! Even if you find an issue that you experienced in the past, please don’t hesitate to bring it to our attention. File bugs: https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools=Debugger Recording a performance issue: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem Join us in Slack/IRC: #devtools Read more in our hacks article: https://hacks.mozilla.org/2019/05/faster-smarter-javascript-debugging-in-firefox/ Thank you for your continued support to improve the experience for the web's creators, Harald on behalf of Firefox DevTools team! p.s. Special thanks to Jason Laster, Logan Smyth, David Walsh, Brian Hacket, Jan Honza Odvarko, Nicolas Chevobbe, Anshul Malik, Hubert Boma Manilla ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Enable cargo pipelining to speed up Firefox builds
Also sprach Nicholas Nethercote: > - Set the environment variable `CARGO_BUILD_PIPELINING=true`. And if you want to include it in your mozconfig I imagine you likely have to do something like this: mk_add_options 'export CARGO_BUILD_PIPELINING=true' ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
New xpcshell-test option to aid debugging failures when run in parallel
tl;dr We now have a --verbose-if-fails option that outputs a log if a xpcshell-test fails when being run in parallel. If you ever have seen output from xpcshell-tests like this: 0:05.68 TEST_START: toolkit/components/search/tests/xpcshell/test_remove_profile_engine.js 0:08.57 TEST_END: FAIL 0:08.61 INFO toolkit/components/search/tests/xpcshell/test_remove_profile_engine.js failed or timed out, will retry. ... 0:19.50 INFO Retrying tests that failed when run in parallel. 0:19.50 TEST_START: toolkit/components/search/tests/xpcshell/test_remove_profile_engine.js 0:21.27 TEST_END: PASS and wondered if that's an intermittent you're trying to fix or just why is that failing... now you have a new tool. --verbose is typically too noisy as it outputs all the logs of the parallel tests at the same time. I've just added the new option --verbose-if-fails which will output logs for any failing test(s) during the parallel run. 0:07.72 TEST_END: FAIL 0:07.75 INFO >>> 0:06.49 INFO (xpcshell/head.js) | test MAIN run_test pending (1) 0:06.49 INFO (xpcshell/head.js) | test run_next_test 0 pending (2) ...More logs... 0:07.79 INFO <<< 0:07.79 INFO toolkit/components/search/tests/xpcshell/test_require_engines_in_cache.js failed or timed out, will retry. ... I've used this style of output in the past to figure out why some of our search tests were taking a long time to timeout, then would pass on the second run. This is just formalising it into a usable option. Mark. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
[desktop] Bugs logged by Desktop Release QA in the last 7 days
Hello, Here's the list of new issues found and filed by the Desktop Release QA team in the last 7 days. Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://tinyurl.com/yytqspws. Bugs logged by Desktop Release QA in the last 7 days: Firefox: Installer RESOLVED INCOMPLETE - https://bugzil.la/1555015 - [Stub Installer] Wrapping text issue inside Reinstall prompt on a certain Windows 7 configuration Firefox: Installer NEW - https://bugzil.la/1555265 - Both the Re-install button and checkbox option can be selected in the Reinstall UI Firefox: Installer RESOLVED WONTFIX - https://bugzil.la/1555316 - Install and re-install stub install UI broken while OS is in High Contrast Firefox: Installer NEW - https://bugzil.la/1555348 - Firefox is not successfully installed if two stub installers are open at the same time Core: Graphics NEW - https://bugzil.la/1555690 - [Linkedin] Glitches on certain buttons inside starting steps section Core: Layout NEW - https://bugzil.la/1555695 - [Instagram] Like button is slightly cut off when toggled This is available as a Bugzilla bug list as well: https://tinyurl.com/yx8l8qvb. Regards, Mihai Boldan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
