Zed Upgrade #108
Merged
Zed Upgrade #108
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add file to the reno documentation build to show release notes for stable/yoga. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/yoga. Sem-Ver: feature Change-Id: I100f1b72f754df48aaa2446de7ec00a35956139e
This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for zed. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: I8529c1b19ae1bba80f2d4058dd4fbb1bdd5044db
After installing doc build requirements with upper constraints, tox was installing blazar without constraints, which was pulling Jinja2 3.1.0 (released today) as a Flask dependency. This caused a docs build failure on stable/wallaby, because Jinja2 dropped support for environmentfilter used by the version of Sphinx in upper constraints. Use skip_install to instruct tox not to install blazar when not needed. This requires adding oslo.config and oslo.policy to doc/requirements.txt because we use their sphinx extensions. Change-Id: Ic55dba0038a2209e9fb291a604a5c1da57607e1e
As discussed in TC PTG[1] and TC resolution[2], we are dropping the lower-constraints.txt file and its testing. We will keep lower bounds in the requirements.txt file but with a note that these are not tested lower bounds and we try our best to keep them updated. [1] https://etherpad.opendev.org/p/tc-zed-ptg#L326 [2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal Change-Id: I24fd4700d59b30e4e5b3fed6c892a4f8ade7bb47
This job fails because the tox environment has been removed in I24fd4700d59b30e4e5b3fed6c892a4f8ade7bb47. Change-Id: I2e66b482b6310b0608c8df9e6b415d49f1373db0
Change-Id: I01abce1ddee907ce8f0bb1ed9340e5508ac173f3
Change-Id: I700630802e38c7c930d77f5d23786ad81c42f608 Closes-Bug: #1975508
Change-Id: I8a3ee4d774451d8211d0d7f2a5db7a42d51b288d
In Zed cycle, we have dropped the python 3.6/3.7[1] testing and its support. Removing the py36 centos8 job as well as updating the python classifier also to reflect the same. [1] https://governance.openstack.org/tc/reference/runtimes/zed.html Change-Id: I6c31cc6ab8c58f77216d869dbbcd6c68bec09b7e
Pecan has made WebTest an optional dependency for testing only [1]. Since it is used for blazar unit testing, we need to add it to the test-requirements. The lower version bound is required by requirements-check. It is (arbitrarily) taken from the Queens' upper-constraints. [1] pecan/pecan#140 Change-Id: I67b730a21676a8191756effec7e15ab1895e1c95
The blazar installation was removed in [1]. However, stevedore requires blazar to generate docs for configuration. Currently, they are mostly empty. Instead of removing the blazar installation, this change makes sure that deps are installed with constraints so that blazar installation does not bring havoc and the original issue is fixed. [1] Ic55dba0038a2209e9fb291a604a5c1da57607e1e Change-Id: I28d06ae31c4cf44d010e0892a094138112b08641
Co-Authored-By: Jacob Colleran <jakecoll@uchicago.edu> Co-Authored-By: Jason Anderson <jasonanderson@uchicago.edu> Co-Authored-By: Pierre Riteau <pierre@stackhpc.com> Change-Id: I0728f556829ba84e222c27bd8c407738b4be2f76
Replace 'called_once_with' with 'assert_called_once_with'. Replace 'called_once' with 'assert_called_once_with'. Change-Id: I1d3c444c3e01b862a1a2571cf13d054dfd2fb463 Closes-Bug: 1989267 Signed-off-by: Takashi Natsume <takanattie@gmail.com>
Apply my comments from the original patch [1] and add unit tests. [1] https://review.opendev.org/c/openstack/blazar/+/781917 Change-Id: I116aad6677423aedb5dda48f06b36afc32819ba8
Change-Id: I828d70fa5ae542eb1dbbb09a95777ef99a618634
Update the URL to the upper-constraints file to point to the redirect rule on releases.openstack.org so that anyone working on this branch will switch to the correct upper-constraints list automatically when the requirements repository branches. Until the requirements repository has as stable/zed branch, tests will continue to use the upper-constraints list on master. Change-Id: Ieb9ecac8017b2a6a4b5d20ca9beb36160eb6e602
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.