# QA Testing fixed, possible problem **URL:** \ **Category:** GNU Radio\ **Created:** [February 11, 2013, 9:09pm UTC](https://www.ruby-forum.com/t/qa-testing-fixed-possible-problem/229586 "2013-02-11T21:09:56Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Brooke\_H](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/77aa72/32.png) [@Brooke\_H](https://www.ruby-forum.com/u/Brooke_H)\ **Post date:** [February 11, 2013, 9:09pm UTC](https://www.ruby-forum.com/t/qa-testing-fixed-possible-problem/229586/1 "2013-02-11T21:09:56Z")
I finally just took out the line that was returning the error and the testing passed (square\_ff = square\_ff.make;). Not sure why that line would be generated in the gr-howto/build/swig/howto\_swig.py file because I never edited it myself. Just wanted to let someone know in case it was a problem with some generation or build file. ---
**Author:** ![Brooke\_H](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/77aa72/32.png) [@Brooke\_H](https://www.ruby-forum.com/u/Brooke_H)\ **Post date:** [February 12, 2013, 9:52am UTC](https://www.ruby-forum.com/t/qa-testing-fixed-possible-problem/229586/2 "2013-02-12T09:52:58Z")
On Mon, Feb 11, 2013 at 03:09:04PM -0500, Brooke H. wrote: > I finally just took out the line that was returning the error and the testing > passed (square\_ff = square\_ff.make;). Not sure why that line would be generated > in the gr-howto/build/swig/howto\_swig.py file because I never edited it myself. > Just wanted to let someone know in case it was a problem with some generation > or build file. I don’t know how this line could drop in here, and I’ve never seen it happen. Can you tell me which gr\_modtool command line caused that and which version you were using? ## MB Karlsruhe Institute of Technology (KIT) Communications Engineering Lab (CEL) Dipl.-Ing. Martin B. Research Associate Kaiserstraße 12 Building 05.01 76131 Karlsruhe Phone: +49 721 608-43790 Fax: +49 721 608-46071 www.cel.kit.edu KIT – University of the State of Baden-Württemberg and National Laboratory of the Helmholtz Association ---
**Author:** ![Brooke\_H](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/77aa72/32.png) [@Brooke\_H](https://www.ruby-forum.com/u/Brooke_H)\ **Post date:** [February 12, 2013, 3:12pm UTC](https://www.ruby-forum.com/t/qa-testing-fixed-possible-problem/229586/3 "2013-02-12T15:12:44Z")
On Tue, Feb 12, 2013 at 2:51 AM, Martin B. (CEL) [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > 76131 Karlsruhe > [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) > [Discuss-gnuradio Info Page](https://lists.gnu.org/mailman/listinfo/discuss-gnuradio) I get the same line using the gr\_modtool from your github repo using (wget [https://raw.github.com/mbant/gr-modtool/master/gr\_modtool.py](https://raw.github.com/mbant/gr-modtool/master/gr_modtool.py)). Last updated 6 days ago on rev 3d650ba57b177e81cef2c30ab2c00eb1e19ac3bd. I tried again to verify, ctest -V output @ > The first one (ctest1.mak) is what gets generated with `cmake ..`. The second one I removed the offending line (352). Now I forget how I solved it. But I did verify the gr\_howto that comes in the GR repo works as expected. -nathan PS, doubt this matters but I used v3.6.3-65-g7e9a439f ---
**Author:** ![Brooke\_H](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/77aa72/32.png) [@Brooke\_H](https://www.ruby-forum.com/u/Brooke_H)\ **Post date:** [February 12, 2013, 3:41pm UTC](https://www.ruby-forum.com/t/qa-testing-fixed-possible-problem/229586/4 "2013-02-12T15:41:24Z")
On Tue, Feb 12, 2013 at 12:51 AM, Martin B. (CEL) [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)wrote: > I don’t know how this line could drop in here, and I’ve never seen it > happen. Can you tell me which gr\_modtool command line caused that and which > version you were using? This is a result of the ordering issue Tom and I mentioned to you in the swig.i file. You’ve already fixed it in the latest branch set for merging (which I’ll probably do today.) I don’t know if this is fixed in the standalone repo yet. Johnathan