Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: obs_lsst
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
test_translator.LsstMetadataTranslatorTestCase testMethod=test_imsim_translator failed in the lsst_distrib clean build, probably since we're now less than 53 weeks from the purported observation date, so it's not far enough in the future to trigger the expected warning.
Attachments
Activity
You could try installing from binaries instead; I think that should bypass the tests.
Alternatives include waiting for the much-improved and almost-out-the-door v22 or requesting a v21_0_1 patch (which, due to various reasons, almost certainly cannot come out before v22 does).
The machines involved are on Ubuntu, so newinstall demands a rebuild 
.
I'm trying again with w_latest (need this for later today, unfortunately).
Binaries work fine on Ubuntu (ever since we switched to conda compilers/stdlibs); I do it all the time. You just need to lie about your OS, by setting
EUPS_PKGROOT=https://eups.lsst.codes/stack/redhat/el7/conda-system/miniconda3-py38_4.9.2-0.6.0
Thanks Jim Bosch – while it comes too late this time around, I will use it next time I need it.
This seems like a bug, though – shouldn't the install script know this? If so, can someone (Kian-Tat Lim?) pass this issue on to the right person in the packaging team to be considered for a fix? I've spent about 6 hours waiting for numerous from-source builds to fail yesterday (until the last one succeeded).
I think I just hit this trying to build {{eups distrib install -t v21_0_0 lsst_distrib }}for the SolSysSciCol sprint.
Is there a workaround (I'd like to stick to the official release, as this will be used for the next ~year)?