Tests triage: language

Tests triage: language

R=zundel@google.com
BUG=
TEST=

Committed: https://code.google.com/p/dart/source/detail?r=4266

[zundel, 2012-02-13 22:51:09]

https://chromiumcodereview.appspot.com/9350056/diff/1/tests/language/language...
File tests/language/language.status (right):

https://chromiumcodereview.appspot.com/9350056/diff/1/tests/language/language...
tests/language/language.status:140: CTConstTest: Pass
Are the issues previously listed still valid?  If so, let's not lose the
comments with the issue number on this update.   If the problem is different
from what's described in the issue, then this is fine, as long at you closed any
issues that are dependent only on dartc code generation.

[scheglov, 2012-02-14 16:37:37]

https://chromiumcodereview.appspot.com/9350056/diff/1/tests/language/language...
File tests/language/language.status (right):

https://chromiumcodereview.appspot.com/9350056/diff/1/tests/language/language...
tests/language/language.status:140: CTConstTest: Pass
On 2012/02/13 22:51:09, zundel wrote:
> Are the issues previously listed still valid?  If so, let's not lose the
> comments with the issue number on this update.   If the problem is different
> from what's described in the issue, then this is fine, as long at you closed
any
> issues that are dependent only on dartc code generation.

Yes, I've checked all bugs in comments and closed them only if they are for code
generation. If we still should have some warning during analysis, I've opened
new issue.

[zundel, 2012-02-15 13:26:46]

lgtm

http://codereview.chromium.org/9350056/diff/1/tests/language/language.status
File tests/language/language.status (right):

http://codereview.chromium.org/9350056/diff/1/tests/language/language.status#...
tests/language/language.status:140: CTConstTest: Pass
OK, I see now.  If a line is marked 'Pass' and the bug is related to code
generation and now closed, we can just remove that line from the status file.
Feel free to do it in this or a followon change.

On 2012/02/14 16:37:37, scheglov wrote:
> On 2012/02/13 22:51:09, zundel wrote:
> > Are the issues previously listed still valid?  If so, let's not lose the
> > comments with the issue number on this update.   If the problem is different
> > from what's described in the issue, then this is fine, as long at you closed
> any
> > issues that are dependent only on dartc code generation.
> 
> Yes, I've checked all bugs in comments and closed them only if they are for
code
> generation. If we still should have some warning during analysis, I've opened
> new issue.