The reasoning for this is that we want to have a sufficiently low
timeout to catch performance regressions, but still want to maintain
the support for having a few tests that takes a longer time to
complete.
This cl adds 2 slow functions, I will add more if any additional tests timeout on the buildbot.
Review URL: https://chromiumcodereview.appspot.com//10854156
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@10714 260f80e4-7a28-3924-810f-c04153c831b5
The File class used to have two synchronous methods
openInputStream and openOutputStream for getting streams for a
file. These have now been changed to work asynchronously by the
associated callback inputStreamHandler or outputStreamHandler
when the stream is opened and available.
To support the synchronous API two new methods
openInputStreamSync and openOutputStreamSync which returns the
stream directly as before have been added.
The actual implemnetation of the file streams still uses the
synchronous file API internally. However this change
adds "simulated" handling of noPendingWriteHandler and
closeHandler for file output stream.
R=ager@google.com
BUG=dart:1784
TEST=
Review URL: https://chromiumcodereview.appspot.com//9432023
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@4452 260f80e4-7a28-3924-810f-c04153c831b5
1. The string input stream now calls the data or line handler if there
is still data available after returning from the data or line
handler. These callbacks are scheduled on the event loop.
2. The reading of data is now throtteld so that calls to read or
readLine will not eagerly try to read from the wrapped input
stream. After each call to read the data handler is installed if
no more buffered data is available. Also when the data handler
is called the data handler on the wrapped input stream is
un-installed if no more data is required for the current data or
line handler.
One side effect of this change is that just reading from an input
stream obtained from a file is no longer possible. One will have to
set up a data handler callback of some kind before any calls to read
will return data. We can of cause change this to allow synchronous
usage of an input stream obtained from a file (maybe with an optional
argument to openInputStream).
Fixed a related throtteling issue with the chunked input stream.
R=ager@google.com
BUG=
TEST=
Review URL: http://codereview.chromium.org//8885032
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@2310 260f80e4-7a28-3924-810f-c04153c831b5
This adds the line handler to the string stream to provide callbacks
when a line is known to be available.
This change also refactors parts of the string stream to avoid
converting decoded char codes to a string before checking for line
break sequences. With this change the string decoder tracks all line
breaks.
There is still room for improvement as e.g. the coping of the list of
char codes when reading lines can be avoided by using anoher offset.
R=ager@google.com
BUG=
TEST=
Review URL: http://codereview.chromium.org//8772008
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@2016 260f80e4-7a28-3924-810f-c04153c831b5
Updated the TestExpectations class to be able to deal with the
odd matching rules that are used for co19.
Currently we are using a lot of memory when running all of these
tests. I have optimized the test expectation part quite a bit.
The thing that seems bad now if the processing of all the lines
of every simple test to find DartOptions. We need to work on that.
R=whesse@google.com
BUG=
TEST=
Review URL: http://codereview.chromium.org//8539044
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@1563 260f80e4-7a28-3924-810f-c04153c831b5
kustermann@google.com