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

Nightly builds failing on macOS

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: jenkins
    • Labels:
      None
    • Team:
      Architecture
    • Urgent?:
      No

      Description

      Ever since we turned the macOS nodes back on in Jenkins the nightly build has been failing:

      >   from .base import *
      		 
      E   ImportError: dlopen(/Users/square/j/ws/scipipe/lsst_distrib/osx-10.13.clang-1000.10.44.4.py3/lsstsw/build/astshim/python/astshim/base.so, 2): Library not loaded: libastshim.dylib
      		 
      E     Referenced from: /Users/square/j/ws/scipipe/lsst_distrib/osx-10.13.clang-1000.10.44.4.py3/lsstsw/build/astshim/python/astshim/base.so
      		 
      E     Reason: image not found

      This looks like a SIP issue so it pointed us to a repeat of DM-21999 (the long shebang). I think that DM-23098 using a longer conda environment name may have pushed us slightly over the 127 character shebang limit (by 1 or 2 characters).

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-21999 Jenkins fails to build macOS binaries

          • Done
          links to

          Web Link GitHub issue with conda that is being ignored

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            tjenness Tim Jenness added a comment -

            Gabriele Comoretto [X] reminds me that DM-23098 has not quite been merged yet (despite the ticket being marked closed) but we have changed Jenkins to always use the lsst-scipipe-8hexchar form which will cause the path to go over 127 characters.

            Show
            tjenness Tim Jenness added a comment - Gabriele Comoretto [X] reminds me that DM-23098 has not quite been merged yet (despite the ticket being marked closed) but we have changed Jenkins to always use the lsst-scipipe-8hexchar form which will cause the path to go over 127 characters.
            Hide
            Permalink
            ktl Kian-Tat Lim added a comment -

            I think this is the appropriate place to hash this to affect only the path (which is used twice).  It might be nice to hash more of the path (e.g. the pipeline name part), but that looks to be difficult and would make debugging, cleanup, etc. harder.

            Show
            ktl Kian-Tat Lim added a comment - I think this is the appropriate place to hash this to affect only the path (which is used twice).  It might be nice to hash more of the path (e.g. the pipeline name part), but that looks to be difficult and would make debugging, cleanup, etc. harder.
            Hide
            Permalink
            ktl Kian-Tat Lim added a comment - - edited

            Reviewed by Simon Krughoff, who brought up a couple of other uses that turn out not to be in pathnames and so are OK.

            Show
            ktl Kian-Tat Lim added a comment - - edited Reviewed by Simon Krughoff , who brought up a couple of other uses that turn out not to be in pathnames and so are OK.

              People

              Assignee:
              ktl Kian-Tat Lim
              Reporter:
              tjenness Tim Jenness
              Reviewers:
              Joshua Hoblitt
              Watchers:
              Gabriele Comoretto [X] (Inactive), Joshua Hoblitt, Kian-Tat Lim, Simon Krughoff, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.