[BUG] spec suites run results vary based on what specs you run it on and backtrace is not shown
Reported by Michael Klishin | February 2nd, 2008 @ 08:12 PM | in 1.0 preview
After rake distclean && rake build && ./bin/ci I get no errors or failures, build is green. But when I do ./bin/ci spec/ruby/1.8 instead I get the following exception:
An exception has occurred:
strange object detected as exception: nil (NilClass)
Backtrace:
Unable to build backtrace due to errors
Original Exception: nil (NilClass)
New Exception: #<NoMethodError: No method 'awesome_backtrace' on an instance of NilClass.> (NilClass)
with two errors that I cannot identify because there's no backtrace at all. Here is CI run results with spec/ruby/1.8 path using MRI.
I am running Mac OS X Leopard.
Comments and changes to this ticket
-
Michael Klishin February 2nd, 2008 @ 08:14 PM
Do not pay attention to run using MRI, I am using patchlevel 110 and Brian mentioned we are only concerned by official stable version so MRI run pastie does not matter at all.
-
Brian Ford February 2nd, 2008 @ 08:21 PM
- → State changed from “new” to “open”
The reason bin/ci spec/ruby/1.8 fails is because it is running the spec/ruby/1.8/library specs which are normally excluded when just bin/ci is run.
The way bin/ci works is this:
- it uses an internal set of specs to run if it is not given any paths
- it uses the explicit paths given on the command line
Currently, we cannot run the spec/ruby/1.8/library specs together with everything else.
-
Dirkjan Bussink February 22nd, 2008 @ 07:25 PM
- → State changed from “open” to “resolved”
Library specs are now also included in ./bin/mspec ci runs and have proper tags for failing specs
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
