-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pin chandra_models version to 3.48 for all tests #381
Conversation
I don't understand what's happening with the throwaway tag and problems that the tip was not at tag 3.49. I followed your setup exactly but did not do anything with making fake tags (and have never had to do that). The proseco tests passed in this case. I also did this to be sure I was getting what I thought:
I reviewed the code again and from what I can see the only way to get to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
Did your setup have pitch-roll-constraint-2023_020 checked out in that chandra_models repo? You've said "followed your setup exactly", but what-the-repo-is-checked-out-at -- that seems to be my issue. I think the CHANDRA_MODELS_DEFAULT_VERSION works fine to get the right version of the model from the repo, but code complains if you aren't checked out at the last release. So I probably should have just checked out 3.49 instead of making a throwaway tag.
(git checkout 3.49 of chandra_models in another terminal)
After checking out at 3.49 I don't get the "tip" warning issue (though I suppose this doesn't confirm my default was behaving correctly at pitch-roll-constraint-2023_020 because this acq test is likely about the acquisition model update, but nevertheless). |
Maybe the difference was that my version didn't have the 3.49 tag. I'll look into it. |
Nope that wasn't it. What do you get with this? The only obvious diff now is that I'm using my
|
Yes. |
|
I'm not seeing the issue right now in proseco; my pasted output above was from where I moved on to sparkles. I think the conftest.py test fix is still the right thing either way. |
Description
Pin chandra_models version to 3.48 for all tests with a pytest fixture that sets the environment variable.
Interface impacts
Testing
I configured with CHANDRA_MODELS_REPO_DIR to /Users/jean/git/chandra_models, set that chandra_models to be at pitch-roll-constraint-2023_020, set CHANDRA_MODELS_DEFAULT_VERSION to pitch-roll-constraint-2023_020, and added a throwaway tag in /Users/jean/git/chandra_models so it would still stop complaining that tip wasn't at tag 3.49. With that setup, I was reliably able to get the tests that (apparently) use the acquisition model to fail without this PR. I did not try to isolate acquisition model and pitch/roll changes.
Unit tests
Independent check of unit tests by @taldcroft (with the same setup noted above except without the "throwaway tag")
Functional tests
Unit tests are functional tests for this change.