octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #61786] [octave forge] (image) many image pack


From: Hartmut
Subject: [Octave-bug-tracker] [bug #61786] [octave forge] (image) many image package test failures under Octave 7
Date: Mon, 10 Jan 2022 07:11:14 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:95.0) Gecko/20100101 Firefox/95.0

URL:
  <https://savannah.gnu.org/bugs/?61786>

                 Summary: [octave forge] (image) many image package test
failures under Octave 7
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Mon 10 Jan 2022 12:11:12 PM UTC
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 7.0.90
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Currently the release candidate 7.0.90 under Windows comes bundled with the
latest released image package version (2.12.0.). Via some patches in
mxe-octave to the image package, the image package installs fine (i.e. without
errors during "pkg install") on Octave 7.

But: Running "pkg test image" under Octave 7.0.90 produces many failing tests,
for several reasons. Several of the image package funtions probably not work
at all under Octave 7. A first glance gave me the impression that some changes
to core Octave result in those test failurs.

This issue is ment to collect and eventually solve these test failures. Here
is a short overview of failing unit tests, including a short first comment to
what the problem seems to be:

* @imref2d/contains.m
** something with the error-id
* @imref2d\intrinsicToWorld.m
** something with the error-id
* @imref2d\worldToIntrinsic.m
* @imref2d\worldToSubscript.m
* @imref3d\contains.m
* @imref3d\intrinsicToWorld.m
* @imref3d\worldToIntrinsic.m
* @imref3d\worldToSubscript.m
* blockproc.m
** those should be fixed already in the next image relase
* colorangle.m
** something with the error-id
* graythresh.m
** usage of hist changed?
* im2bw.m
** the "+=" operator seems to be obsolete now
* imfindcircles.m
** usage of hist changed?
* imlincomb.m
** the "--" operator seems to be obsolete now
* integralImage3.m
** changed error message
* label2rgb.m
** something with a function name as parameter
* otsuthresh.m
** something with the error-id

Probably some of those issues are also present in image package functions,
that do not have any unit tests...










    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61786>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]