Compiling and testing gwt for the RF changes has been a tad slow. I'll think about a patch. Maybe extra message on that error message plus up the time out? Still struggling to understand a time out as part of parsing error detection.
The laptop has 2x1.66GHz cores... Not latest and greatest but at my first job the processors were 75MHz and we used to manage to run big web sites... On Sunday, July 28, 2013 5:44:07 PM UTC+1, Thomas Broyer wrote: > > > > On Sunday, July 28, 2013 5:49:15 PM UTC+2, salk31 wrote: >> >> yuk. PegDown processor is non-deterministic!? Turns out my laptop and >> linux server are too slow to compile gwt-site. >> >> Sorry for wasting your time Thomas. I was reading the error message in >> order and thought "[ERROR] org.pegdown.ParsingTimeoutException" must be >> spurious. >> >> I've patched my local version so it compiles. Maybe a note in docs about >> this error or a ticket to possibly change the code? >> >> Sorry again for not posting the important error message. Using a timeout >> like this is new to me. >> > > Oh wow, more than 2 secs (the default timeout) for processing a file?! > Can you do any reasonable Java development in these conditions? > > That said, I agree the default behavior of PegDown should be no timeout, > and maybe we should use Integer.MAX_VALUE in gwt-site (AFAICT, the timeout > cannot be turned off; created an issue for it: > https://github.com/sirthias/pegdown/issues/98) > Feel free to propose such a change in Gerrit, we'll see what Daniel thinks > of it. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
