Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-7701

conda-lsst ndarray test failure

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ndarray
    • Labels:
      None

      Description

      The conda-lsst build log for the test failure can be found here:

      https://gist.github.com/jmatt/dcb6ce8312aac1ff81cbb923703d8430

      Running tests...
      Test project /Users/square/dev/conda-lsst/miniconda/conda-bld/work/build
          Start 1: test_ndarray
      1/5 Test #1: test_ndarray .....................   Passed    0.01 sec
          Start 2: test_views
      2/5 Test #2: test_views .......................   Passed    0.01 sec
          Start 3: test_ndarray-fft
      3/5 Test #3: test_ndarray-fft .................***Exception: Other  0.00 sec
          Start 4: test_ndarray_eigen
      4/5 Test #4: test_ndarray_eigen ...............   Passed    0.01 sec
          Start 5: swig_test
      5/5 Test #5: swig_test ........................   Passed    0.11 sec
       
      80% tests passed, 1 tests failed out of 5
       
      Total Test time (real) =   0.14 sec
       
      The following tests FAILED:
      	  3 - test_ndarray-fft (OTHER_FAULT)
      Errors while running CTest
      make: *** [test] Error 8
      

        Attachments

          Issue Links

            Activity

            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            This is finally pushed upstream in in DM-8135

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - This is finally pushed upstream in in DM-8135
            Hide
            tjenness Tim Jenness added a comment -

            This seems to be a reasonable short term hack.

            Show
            tjenness Tim Jenness added a comment - This seems to be a reasonable short term hack.
            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            I created a patch to create a patch to remove the fft ndarray test that was failing due to a missing path. This is a workaround to finish v12.1

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - I created a patch to create a patch to remove the fft ndarray test that was failing due to a missing path. This is a workaround to finish v12.1
            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            I used Conda's patch system to create an eups patch to remove the fft test that was failing on Mac OS X in ndarry.

            https://github.com/jmatt/conda-lsst/commit/9dbadf0fcfa6dd7fc369a6682a8c87a7cb55ab14

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - I used Conda's patch system to create an eups patch to remove the fft test that was failing on Mac OS X in ndarry. https://github.com/jmatt/conda-lsst/commit/9dbadf0fcfa6dd7fc369a6682a8c87a7cb55ab14
            Hide
            tjenness Tim Jenness added a comment -

            That's a bit strange. I was thinking about this last night and it occurs to me that (1) we never usually run tests of third party packages so ndarray running tests is anomalous, and (2) the reason why this works in an lsstsw build but not (at least for most of us) in conda is that make is a SIP program so strips DYLD_LIBRARY_PATH but when we build fftw normally with lsstsw it has a full path burned in to the library so that the location is available to the test binary. scons builds know about SIP and forward on the LSST_LIBRARY_PATH when running tests. In conda builds it's @rpath as we've stated above. This is also discussed in DM-5753.

            Show
            tjenness Tim Jenness added a comment - That's a bit strange. I was thinking about this last night and it occurs to me that (1) we never usually run tests of third party packages so ndarray running tests is anomalous, and (2) the reason why this works in an lsstsw build but not (at least for most of us) in conda is that make is a SIP program so strips DYLD_LIBRARY_PATH but when we build fftw normally with lsstsw it has a full path burned in to the library so that the location is available to the test binary. scons builds know about SIP and forward on the LSST_LIBRARY_PATH when running tests. In conda builds it's @rpath as we've stated above. This is also discussed in DM-5753 .

              People

              • Assignee:
                jmatt J Matt Peterson [X] (Inactive)
                Reporter:
                jmatt J Matt Peterson [X] (Inactive)
                Reviewers:
                Tim Jenness
                Watchers:
                J Matt Peterson [X] (Inactive), Pim Schellart [X] (Inactive), Robert Lupton, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel