Tier 3 win64 ASan builds on try
Just a heads up that now we have win64 ASan builds on try. The try format: try: -b o -p win64-asan -u none -t none Bug 1347793 is tracking the failed tests on taskcluster, though by now the tests for normal windows builds are not all green yet and I haven't seen any real ASan issue. I am not sure if js/fuzzing folks are interested, but probably we can try to do fuzzing for jsshell-asan, on windows. (Wonder do we have automated fuzzing tests on any infrastructure.) Note this is still in tier 3, things can regress easily. Ting ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Increased number of e10s related crashes for firefox-ui-tests on mozilla-central and integration branches
Never mind, I just found the command on MDN. However I can't reproduce, will update to bug 1290186 if I find anything. Ting On Fri, Jul 29, 2016 at 3:17 PM, Ting-Yu Chou <tc...@mozilla.com> wrote: > It seems that they're crashed with the test case > firefox-ui/tests/puppeteer/test_windows.py:test_open_close, how can I run > it locally? > > Ting > > On Fri, Jul 29, 2016 at 1:50 PM, Henrik Skupin <m...@hskupin.info> wrote: > >> Hi, >> >> Over the last couple of days I noticed a spike of crashes specifically >> for our firefox-ui-tests as run on Taskcluster (Linux64, Ubuntu 12.04 >> docker image). The crashes are completely related to our e10s jobs. >> There are a lot of different crash signatures, but mostly these are: >> >> [@ libpthread-2.15.so + 0xbd84] >> [@ libc-2.15.so + 0xe7993] >> >> >> https://treeherder.mozilla.org/#/jobs?repo=autoland=firefox%20ui%20e10s >> >> Does anyone know if there were related changes for e10s which might have >> caused those crashes to appear? I'm afraid that we might have some >> unknown top crashers which would go to aurora by the merge early next >> week. >> >> Thanks >> >> -- >> Henrik >> ___ >> 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: Increased number of e10s related crashes for firefox-ui-tests on mozilla-central and integration branches
It seems that they're crashed with the test case firefox-ui/tests/puppeteer/test_windows.py:test_open_close, how can I run it locally? Ting On Fri, Jul 29, 2016 at 1:50 PM, Henrik Skupinwrote: > Hi, > > Over the last couple of days I noticed a spike of crashes specifically > for our firefox-ui-tests as run on Taskcluster (Linux64, Ubuntu 12.04 > docker image). The crashes are completely related to our e10s jobs. > There are a lot of different crash signatures, but mostly these are: > > [@ libpthread-2.15.so + 0xbd84] > [@ libc-2.15.so + 0xe7993] > > > https://treeherder.mozilla.org/#/jobs?repo=autoland=firefox%20ui%20e10s > > Does anyone know if there were related changes for e10s which might have > caused those crashes to appear? I'm afraid that we might have some > unknown top crashers which would go to aurora by the merge early next week. > > Thanks > > -- > Henrik > ___ > 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: IPCStream landed in mozilla-central
On Fri, May 20, 2016 at 2:19 AM, Ben Kellywrote: > On Thu, May 19, 2016 at 1:41 PM, Andrew McCreight > wrote: > > > On Thu, May 19, 2016 at 8:04 AM, Ben Kelly wrote: > > > > > 3) Supports async pipe streams using a new PSendStream actor from > > > *child-to-parent*. I have plans to add support for parent-to-child, > but > > I > > > don't have a consumer yet and we need to figure out some issues with > > > PBackground targeting worker threads. > > > > > > > One place that this would be very useful would be for networking. Right > > now, the various networking protocols send data to the child by calling > > NS_ReadInputStreamToString(), then copying the string into an IPC > message, > > which is bad because it requires a lot of contiguous memory addresses, > and > > also has a fair bit of bloat from all of the copies (bug 1110596, bug > > 1263028). > > > > That would be a good thing to try. I wonder how many consumers assume > nsIChannel::OnDataAvailable() provides a fixed length stream, though. > The copying we want to avoid in bug 1110596 is from a stream to a nsCString buffer, which to let a stream write to the IPC Pickle buffer directly. But I checked SendStreamChildImpl::DoRead() [1], it still reads to a nsCString buffer at first. The good thing is it sends the stream's data in chunks of 32k at maximum, which can avoid the bloat. [1] https://dxr.mozilla.org/mozilla-central/rev/c4449eab07d39e20ea315603f1b1863eeed7dcfe/ipc/glue/SendStreamChild.cpp#276-282 Ting > Here is the bug to track parent-to-child pipe streaming: > > https://bugzilla.mozilla.org/show_bug.cgi?id=1274343 > > Thanks. > > Ben > ___ > 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: nsThread now leaks runnables if dispatch fails
> In bug 1218297 we saw a case where dispatch to a thread (the socket > transport service thread in this case) fails because the thread has > already shut down. In our brave new world, nsThread simply leaks the > runnable. It can't release the reference it holds, because that would > reintroduce the race condition we wanted to avoid, and it can't > release the reference on the correct thread so it's already gone away. > I am a bit confused with this, if the executing thread has already shut down, why would releasing the reference dispatching thread holds reintroduce the race condition? Who is racing with dispatching thread? Ting ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: RFC: Navigation transitions
On Wed, Apr 22, 2015 at 1:02 AM, Christopher Lord cl...@mozilla.com wrote: down. I'm not a huge fan of all aspects of their proposal, so I've made my own: http://chrislord.net/?p=273preview=1_ppp=0afe20d87f Seems the link is outdated? ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Fwd: [b2g] Improve performance on multi-core device
Forward this mail to dev-platform to hopefully get more feedbacks, sorry for the extra mail. Ting - Forwarded Message - From: Ting-Yu Chou tc...@mozilla.com To: dev-b2g dev-...@lists.mozilla.org Sent: Tuesday, November 11, 2014 7:02:29 PM Subject: [b2g] Improve performance on multi-core device Hello, We opened bug 1093564 to improve the performance on quad-core (or more) devices, and currently we're working mainly on application launch time as it is the major requirement from partner. But indeed we want to improve the performance of user's daily use, so I am sending this email to collect things that you expect to be improved with more cores but it is not. That'd help us to have some ideas what to look into, and put them into the task queue. Thanks, Ting ___ dev-b2g mailing list dev-...@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: How to run browser rooting analysis of mozharness locally?
Never mind, I just found this: https://wiki.mozilla.org/Javascript:SpiderMonkey:ExactStackRooting Will try ask on #jsapi. Ting - Original Message - From: Ting-Yu Chou tc...@mozilla.com To: dev-platform dev-platform@lists.mozilla.org Sent: Monday, September 15, 2014 12:11:28 PM Subject: How to run browser rooting analysis of mozharness locally? Hi, The patch of bug 1049290 failed linux64-br-haz_try_dep, I am trying to debug it locally. I read: https://wiki.mozilla.org/ReleaseEngineering/Mozharness/How_to_run_tests_as_a_developer, and use the command (I didn't see installer/test url in the log): $ python scripts/scripts/spidermonkey_build.py --config-file hazards/build_browser.py --config-file hazards/common.py --cfg developer_config.py but it complains: 11:37:00 INFO - # 11:37:00 INFO - # Running checkout-source step. 11:37:00 INFO - # 11:37:00 INFO - Running main action method: checkout_source 11:37:00FATAL - Uncaught exception: Traceback (most recent call last): 11:37:00FATAL - File /home/ting/w/fx/bz/1049290/scripts/mozharness/base/script.py, line 1258, in run 11:37:00FATAL - self.run_action(action) 11:37:00FATAL - File /home/ting/w/fx/bz/1049290/scripts/mozharness/base/script.py, line 1200, in run_action 11:37:00FATAL - self._possibly_run_method(method_name, error_if_missing=True) 11:37:00FATAL - File /home/ting/w/fx/bz/1049290/scripts/mozharness/base/script.py, line 1141, in _possibly_run_method 11:37:00FATAL - return getattr(self, method_name)() 11:37:00FATAL - File scripts/scripts/spidermonkey_build.py, line 33, in wrapper 11:37:00FATAL - assert (val is not None and None not in str(val)), invalid + query.__name__ 11:37:00FATAL - AssertionError: invalid query_repo 11:37:00FATAL - Running post_fatal callback... 11:37:00FATAL - Exiting -1 I have tried to set environment PROPERTIES_FILE with a file which has buildprops.json content from log, but still doesn't work. Anyone know the correct command to run the test locally? Thanks, Ting ___ 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
How to run browser rooting analysis of mozharness locally?
Hi, The patch of bug 1049290 failed linux64-br-haz_try_dep, I am trying to debug it locally. I read: https://wiki.mozilla.org/ReleaseEngineering/Mozharness/How_to_run_tests_as_a_developer, and use the command (I didn't see installer/test url in the log): $ python scripts/scripts/spidermonkey_build.py --config-file hazards/build_browser.py --config-file hazards/common.py --cfg developer_config.py but it complains: 11:37:00 INFO - # 11:37:00 INFO - # Running checkout-source step. 11:37:00 INFO - # 11:37:00 INFO - Running main action method: checkout_source 11:37:00FATAL - Uncaught exception: Traceback (most recent call last): 11:37:00FATAL - File /home/ting/w/fx/bz/1049290/scripts/mozharness/base/script.py, line 1258, in run 11:37:00FATAL - self.run_action(action) 11:37:00FATAL - File /home/ting/w/fx/bz/1049290/scripts/mozharness/base/script.py, line 1200, in run_action 11:37:00FATAL - self._possibly_run_method(method_name, error_if_missing=True) 11:37:00FATAL - File /home/ting/w/fx/bz/1049290/scripts/mozharness/base/script.py, line 1141, in _possibly_run_method 11:37:00FATAL - return getattr(self, method_name)() 11:37:00FATAL - File scripts/scripts/spidermonkey_build.py, line 33, in wrapper 11:37:00FATAL - assert (val is not None and None not in str(val)), invalid + query.__name__ 11:37:00FATAL - AssertionError: invalid query_repo 11:37:00FATAL - Running post_fatal callback... 11:37:00FATAL - Exiting -1 I have tried to set environment PROPERTIES_FILE with a file which has buildprops.json content from log, but still doesn't work. Anyone know the correct command to run the test locally? Thanks, Ting ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform