Thanks for reporting this! (I see that Steven also ran into this bug). I do think it needs another issue, for whatever changes in the test harness (which I know has been also changed recently) that hid this bug from the unit testing. Your running all the tests individually makes me feel a bit more comfortable with working on v0.5 master, however, until the problem with the test harness is fixed, we can't tell what sorts of bugs might slip in unnoticed.
Any thoughts as to what exactly is masking the error in the unicode test? (I just noticed it, because for some strange reason, the error is not masked on my "julia-lite" branch, and it showed up after I merged in the last couple days of changes from JuliaLang/julia and ran the unit tests before pushing it to GitHub for people to play with) Scott On Sunday, February 14, 2016 at 5:16:17 AM UTC-5, Mauro wrote: > > Reported here https://github.com/JuliaLang/julia/issues/15072 > > On Sat, 2016-02-13 at 22:33, Scott Jones <[email protected] > <javascript:>> wrote: > > I'm seeing a very strange failure recently (within the last week), where > > running "test/runtests.jl" seems to pass, but running the individual > test shows > > a very different result. > > I've reduced it to this, it seems to be a problem with the scope used > for s in > > the third line. > > > > let s = "b\u0300lahβlahb\u0302láh", > > g = ["b\u0300","l","a","h","β","l","a","h","b\u0302","l","á","h"] > > g_ = map(s -> normalize_string(s, :NFC), g) > > g0 = map(x -> normalize_string(x, :NFC), g) > > println(g_) > > println(g0) > > end > > > > > > I'm rather concerned, because this failure when running test/unicode.jl > is > > masked when running test/runtests.jl - could other failures on master be > > getting masked? >
