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

LSST shared stack build broken on Tiger & Perseus (at Princeton)

    XMLWordPrintable

Details

    • Bug
    • Status: Done
    • Resolution: Done
    • None
    • None
    • None

    Description

      They seem to have gotten stuck at `w_2018_14` (should now be at `w_2018_20`):

      lam3@tiger-sumire:~ $ source /tigress/HSC/LSST/stack_tiger/loadLSST.bash
      lam3@tiger-sumire:~ $ setup lsst_distrib
      lam3@tiger-sumire:~ $ eups list -s lsst_distrib
       15.0-2-gda316d8 current w_2018_14 setup

      vs.

      lauren@lsst-dev01:~ $ source /software/lsstsw/stack/loadLSST.bash
      lauren@lsst-dev01:~ $ setup lsst_distrib
      lauren@lsst-dev01:~ $ eups list -s lsst_distrib
         15.0-2-gda316d8+37   current w_2018_20 setup
      

      Attachments

        Issue Links

          Activity

            Turns out that in forcing git-lfs onto the path, I'd managed to break devtoolset-6. Now resolved that, and a build is running on tiger-sumire. It should start with w_2018_28 and pick up newer versions from there; I don't intend to backfill unless somebody expresses a requirement.

            I'll do the same thing on Perseus in a moment.

            Since I'm no longer in Princeton and hence not really paying attention to such things, I'm confused about where this code is actually needed. Are tiger-sumire and the Perseus head node still the most appropriate places? Should we be doing something different for Tiger Mk 2?

            swinbank John Swinbank added a comment - Turns out that in forcing git-lfs onto the path, I'd managed to break devtoolset-6 . Now resolved that, and a build is running on tiger-sumire . It should start with w_2018_28 and pick up newer versions from there; I don't intend to backfill unless somebody expresses a requirement. I'll do the same thing on Perseus in a moment. Since I'm no longer in Princeton and hence not really paying attention to such things, I'm confused about where this code is actually needed. Are tiger-sumire and the Perseus head node still the most appropriate places? Should we be doing something different for Tiger Mk 2?

            We now have w_2018_28 on both Tiger-Sumire and Perseus, and they should be automatically updated to new weeklies as they are published. Phew.

            Per the above, if we need these on other systems (new-Tiger, etc), please file new tickets to request that.

            swinbank John Swinbank added a comment - We now have w_2018_28 on both Tiger-Sumire and Perseus, and they should be automatically updated to new weeklies as they are published. Phew. Per the above, if we need these on other systems (new-Tiger, etc), please file new tickets to request that.

            Thanks John, both shared stacks have been successfully updated.  As for the "new" tigers, see DM-15130.

            lauren Lauren MacArthur added a comment - Thanks John, both shared stacks have been successfully updated.  As for the "new" tigers, see DM-15130 .
            price Paul Price added a comment -

            swinbank: tiger-sumire and the Perseus head node are the right places for now. I believe there are plans for tiger-sumire to be replaced with a new machine running the same OS as Perseus and tiger2, at which point we will only need to build on the new tiger-sumire.

            price Paul Price added a comment - swinbank : tiger-sumire and the Perseus head node are the right places for now. I believe there are plans for tiger-sumire to be replaced with a new machine running the same OS as Perseus and tiger2, at which point we will only need to build on the new tiger-sumire .

            Thanks both!

            swinbank John Swinbank added a comment - Thanks both!

            People

              swinbank John Swinbank
              lauren Lauren MacArthur
              Lauren MacArthur
              John Swinbank, Lauren MacArthur, Paul Price
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.