Re: [webkit-dev] Port For Android

2017-03-16 Thread Sergio Villar Senin
O Mar, 07-03-2017 ás 20:07 -0500, Patrick Wright escribiu: > > However, in the source code of android. There is an implementation of > Webkit show here: https://developer.android.com/reference/android/web > kit/package-summary.html . it is just very slow and restrictive.  That's the Android

Re: [webkit-dev] build.webkit.org transition today at 3pm PDT

2017-03-16 Thread Lucas Forschler
I will ensure all commits that happen during transition get staged on the new server. Lucas > On Mar 16, 2017, at 2:52 PM, Ryosuke Niwa wrote: > > Are you making the subversion server readonly meanwhile? > > It's not acceptable for our infrastructure to be down and letting >

Re: [webkit-dev] build.webkit.org transition today at 3pm PDT

2017-03-16 Thread Ryosuke Niwa
Are you making the subversion server readonly meanwhile? It's not acceptable for our infrastructure to be down and letting people commit random things into the repository. - R. Niwa On Thu, Mar 16, 2017 at 2:40 PM, Ling Ho wrote: > Hello WebKit developers: > > We are

Re: [webkit-dev] build.webkit.org transition today at 3pm PDT

2017-03-16 Thread Lucas Forschler
I’ve re-triggered everything that landed after 2:00. This is r214068 through 214074. r214075 was auto-triggered, as the build master was back online before it landed. Lucas > On Mar 16, 2017, at 3:44 PM, Lucas Forschler wrote: > > I will ensure all commits that happen

Re: [webkit-dev] Introduce WebKit Android port

2017-03-16 Thread Michael Catanzaro
Hi, Is this just a code drop? Or will you be committing to its maintenance and attempting to upstream it? It's interesting regardless! Michael ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] build.webkit.org transition today at 3pm PDT

2017-03-16 Thread Ryosuke Niwa
Thanks! - R. Niwa On Thu, Mar 16, 2017 at 3:59 PM, Lucas Forschler wrote: > I’ve re-triggered everything that landed after 2:00. This is r214068 through > 214074. > r214075 was auto-triggered, as the build master was back online before it > landed. > > Lucas > >> On Mar

Re: [webkit-dev] build.webkit.org transition today at 3pm PDT

2017-03-16 Thread Ryosuke Niwa
It looks like Windows testers haven't come back up: https://build.webkit.org/builders/Apple%20Win%207%20Debug%20%28Tests%29 https://build.webkit.org/builders/Apple%20Win%207%20Release%20%28Tests%29 - R. Niwa On Thu, Mar 16, 2017 at 7:37 PM, Ryosuke Niwa wrote: > Thanks! > > -

[webkit-dev] build.webkit.org transition today at 3pm PDT

2017-03-16 Thread Ling Ho
Hello WebKit developers: We are continuing our transitioning of webkit.org servers today and tomorrow. Between 3pm and 4pm Pacific, we will be moving build.webkit.org. Please email us at ad...@webkit.org if you encounter any issue with your build bots after the transition. Thanks, ... ling

[webkit-dev] svn.webkit.org, git.webkit.org, trac.webkit.org and perf.webkit.org transition today on Friday at 10am PDT

2017-03-16 Thread Ling Ho
Hello WebKit developers, We have rescheduled our switch of svn.webkit.org and git.webkit.org for Friday (3/17) morning, between 10 and 11am PDT. We will also be moving trac.webkit.org and perf.webkit.org during the same time. The current svn repository will be made read-only at 10am. We will

[webkit-dev] Proposal to limit the size of the captured exception stack

2017-03-16 Thread Mark Lam
Hi folks, Currently, if we have an exception stack that is incredibly deep (especially for a StackOverflowError), JSC may end up thrashing memory just to capture the large stack trace in memory.This is bad for many reasons: 1. the captured stack will take a lot of memory. 2. capturing the

Re: [webkit-dev] Proposal to limit the size of the captured exception stack

2017-03-16 Thread Brian Burg
> On Mar 16, 2017, at 10:09 PM, Mark Lam wrote: > > Hi folks, > > Currently, if we have an exception stack that is incredibly deep (especially > for a StackOverflowError), JSC may end up thrashing memory just to capture > the large stack trace in memory.This is bad