Ref #33199 - Try nock restore for pipeline failure #9532
Merged
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
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.
Going down the list of things we can do to resolve the intermittent katello-master-source-release pipeline failure.
The 2nd take is to use nock.restore() and nock.activate() between tests in this file.
Also nudging @jeremylenz and @Andrewgdewar for awareness and ideas cause my next idea is to use jest --no-cache and it will slow down the test run times. It would probably be better to write new tests for the CVDetailsRepo component even though I don't see the issue with the way it is written today.
See for reference: #9526