You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
@bjfish Specs seem to have been all messed up over the past 24 hours. I'm not sure why, but I think I fixed some String-related stuff. After that, I started seeing this Array#delete_if spec fail. I've retagged it for now. If you get a chance to look at it, that'd be helpful.
The reason will be displayed to describe this comment to others. Learn more.
@nirvdrum I was investigating this a little but haven't found the exact cause. I had trouble consistently reproducing the errors. I was suspicious of my reject! changes. I'll investigate more when I can.
The reason will be displayed to describe this comment to others. Learn more.
Yeah that's a failure inside MSpec, rather than inside a spec, so MSpec doesn't have a chance to set a nice error condition. We should probably exit(1) if an exception gets to the top level - we don't do that at the moment. I think @nirvdrum is working on the problem with chomp! anyway.
ed2f7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bjfish Specs seem to have been all messed up over the past 24 hours. I'm not sure why, but I think I fixed some String-related stuff. After that, I started seeing this
Array#delete_if
spec fail. I've retagged it for now. If you get a chance to look at it, that'd be helpful.ed2f7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nirvdrum I was investigating this a little but haven't found the exact cause. I had trouble consistently reproducing the errors. I was suspicious of my reject! changes. I'll investigate more when I can.
ed2f7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also saw green builds when specs were failing, is this the default behavior?
ed2f7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have a link to the build? Travis sometimes flakes out.
ed2f7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks green but has a spec failure in the middle https://travis-ci.org/jruby/jruby/jobs/55324179
ed2f7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that's a failure inside MSpec, rather than inside a spec, so MSpec doesn't have a chance to set a nice error condition. We should probably
exit(1)
if an exception gets to the top level - we don't do that at the moment. I think @nirvdrum is working on the problem withchomp!
anyway.ed2f7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
chomp!
issue should be fixed. If you see otherwise, please let me know.ed2f7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
delete_if
should be fixed at 0bc4a57