Remove incorrect test for #22872

[apasel422]

The original issue was not fixed, but the test passed due to disabled debug assertions.

[rust-highfive]

r? @huonw

(rust_highfive has picked a reviewer for you, use r? to override)

[alexcrichton]

Hm, why delete the test though? Seems like it's fine to leave in and if we add a builder for debug assertions it'd require fixing this?

[apasel422]

I'm not sure what the final test will look like (i.e. if the errors will
have to change), and it currently causes make check to fail when debug
assertions are enabled locally.

On Wed, Sep 16, 2015 at 1:01 PM, Alex Crichton notifications@github.com
wrote:

Hm, why delete the test though? Seems like it's fine to leave in and if we
add a builder for debug assertions it'd require fixing this?

—
Reply to this email directly or view it on GitHub
#28438 (comment).

[alexcrichton]

@bors: r+ f5b69b3

hm ok, seems fine

[bors]

⌛ Testing commit f5b69b3 with merge 6c18dd5...

[bors]

☀️ Test successful - auto-linux-32-nopt-t, auto-linux-32-opt, auto-linux-64-nopt-t, auto-linux-64-opt, auto-linux-64-x-android-t, auto-mac-32-opt, auto-mac-64-nopt-t, auto-mac-64-opt, auto-win-gnu-32-nopt-t, auto-win-gnu-32-opt, auto-win-gnu-64-nopt-t, auto-win-gnu-64-opt, auto-win-msvc-32-opt, auto-win-msvc-64-opt