Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(94)

Issue 148733003: Update status of mirrors/regress_16321_test/01 for dartium. (Closed)

Created:
6 years, 11 months ago by rmacnak
Modified:
6 years, 10 months ago
Reviewers:
vsm
CC:
reviews_dartlang.org
Visibility:
Public.

Description

Update status of mirrors/regress_16321_test/01 for dartium. BUG=http://dartbug.com/16351 TBR Committed: https://code.google.com/p/dart/source/detail?r=32047

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -2 lines) Patch
M tests/lib/lib.status View 1 chunk +2 lines, -2 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
rmacnak
Can we not detect compile-time errors in dartium? Only drt?
6 years, 11 months ago (2014-01-28 01:00:34 UTC) #1
rmacnak
Committed patchset #1 manually as r32047 (presubmit successful).
6 years, 11 months ago (2014-01-28 01:01:06 UTC) #2
vsm
On 2014/01/28 01:00:34, Ryan Macnak wrote: > Can we not detect compile-time errors in dartium? ...
6 years, 10 months ago (2014-01-28 18:28:30 UTC) #3
rmacnak
6 years, 10 months ago (2014-01-28 19:00:40 UTC) #4
Message was sent while issue was closed.
On 2014/01/28 18:28:30, vsm wrote:
> On 2014/01/28 01:00:34, Ryan Macnak wrote:
> > Can we not detect compile-time errors in dartium? Only drt?
> 
> What's the difference you are seeing?  This may be also related to how the
test
> framework hooks into Dartium vs DRT.

I see drt reporting a runtime error now; I think I was looking at the wrong
thing.

Powered by Google App Engine
This is Rietveld 408576698