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

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

[Octave-bug-tracker] [bug #56082] [octave forge] (dicom) addpath warning


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #56082] [octave forge] (dicom) addpath warning in BIST tests on installed package
Date: Fri, 5 Apr 2019 20:34:21 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36

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

                 Summary: [octave forge] (dicom) addpath warning in BIST tests
on installed package
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Fri 05 Apr 2019 05:34:19 PM PDT
                Category: Octave Forge Package
                Severity: 2 - Minor
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

As part of its install, the dicom package includes test scripts in the
${prefix}/test directory.

Running these tests on the installed and loaded dicom package prints a bunch
of addpath warnings, presumably because the tests are normally run in the
source tree


warning: addpath: ../inst: No such file or directory
PASSES 4 out of 4 tests
warning: addpath: ../inst: No such file or directory
warning: addpath: ../inst: No such file or directory
PASSES 5 out of 5 tests
warning: addpath: ../inst: No such file or directory
PASSES 3 out of 3 tests
…


It would be nice to avoid these warning messages when the tests are run on the
already-installed package. Maybe just add 'if (isfolder ("../inst"))', or
assume the directory is in the path and leave it to the makefile to set
correctly when developing.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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