Test suite not run on build
Bug #1197894 reported by
Robie Basak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby-indentation (Debian) |
Fix Released
|
Unknown
|
|||
ruby-indentation (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I was examining ruby-indentation for an MIR (for ruby-safe-yaml, for puppet), and found that the test suite supplied by upstream does not run on a package build.
I'm struggling to understand why. The attached patch fixes it, but I don't like it. Why doesn't "dh_ruby --test" do the right thing here?
Related branches
tags: | added: patch |
Changed in ruby-indentation (Debian): | |
status: | Unknown → New |
Changed in ruby-indentation (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Forwarded to Debian. More information in the bug there.
Since the cause appears to be a mismatch between upstream's expectation of how to run the test suite vs. the information provided in the packaging to dh_ruby in debian/ ruby-test- files.yaml, I felt it best to see what the Debian maintainer wants to do here.
In the meantime, using a dh_override_ auto_test of "rspec" seemed like the best minimal patch to use in Ubuntu, since it's a trivial change to debian/rules and runs the test suite the same way that I believe upstream are running it. Whichever path Debian chooses, we can resync.