bugGNU Octave - Bugs: bug #54218, [octave forge] (signal) test fails...

 
 

bug #54218: [octave forge] (signal) test fails marked as PASS?

Submitter:  Colin Macdonald <cbm>
Submitted:  Sun 01 Jul 2018 07:17:28 AM UTC
   
 
Category:  Octave Package Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Build Failure
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * other Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 02 Jul 2018 05:52:33 AM UTC, comment #3: 

Oops, my mistake about the PASS/FAIL labeling.

That was with control 3.0.0; they pass with 3.1.0.

Sorry for the noise, please close.

Colin Macdonald <cbm>
Sun 01 Jul 2018 08:22:47 AM UTC, comment #2: 

I'm not seeing a bug here, can you clarify if I'm missing something?

As Dan said, impinvar.m for example has 12 tests, and you are seeing PASS=0, FAIL=12.

Incidentally I'm not sure why you have those failures, is this with control 3.0.0 or 3.1.0?

Mike Miller <mtmiller>
Group Member
Sun 01 Jul 2018 07:36:13 AM UTC, comment #1: 

Are you running the test from the GUI or from the shell command line.  I was under the impression that failed tests typically give more detailed information, such as what is expect, what is computed and what the difference is.  Anyway, your impinvar.m and invimpinvar.m test are failing all test so the indication is PASS 0/12 with FAIL 12.  The fractional numerator (in this case 0) and the number of FAILs (in this case 12) should add to the fractional denominator.  If the number of FAILs is 0, then no "FAIL" is printed.  impz.m passes 1 out of 2 tests, and that means 1 XFAIL, the added "X" meaning "expected fail".  So, it does look like something is failing on your system.

FWIW, I (and I think others) are having problems compiling the signal processing package with the latest development code.

Dan Sebald <sebald>
Sun 01 Jul 2018 07:17:28 AM UTC, original submission:  

Mike,

I was looking at improving the Fedora package for octave-signal.  I enabled tests and saw:


  ----- 8< -----

  ifwht.m ................................................ PASS   10/10
  impinvar.m ............................................. PASS    0/12   FAIL 12
  impz.m ................................................. PASS    1/2    XFAIL 1
  invimpinvar.m .......................................... PASS    0/12   FAIL 12
  kaiser.m ............................................... PASS    6/6

  ----8<----


Note some lines are marked as both PASS and FAIL!  And I don't think the overall tests fail either.

Details: Octave 4.2.2, signal-1.4.0.

Happy to dig deeper, but not right now.

Colin Macdonald <cbm>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jwe (Updated the item)
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by sebald (Posted a comment)
  • -email is unavailable- added by cbm (Submitted the item)
  • -email is unavailable- added by cbm
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-07-02 jwe Summary[octave-forge] (signal) test fails marked as PASS? [octave forge] (signal) test fails marked as PASS?
    2018-07-02 mtmiller StatusWorks For Me Invalid / Not an Octave Bug
        Open/ClosedOpen Closed
    2018-07-01 mtmiller StatusNone Works For Me
    2018-07-01 cbm Carbon-Copy- Added mtmiller

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code