This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Removed main conflicting data from tc-fixtures.#3120
Merged
dneuman64 merged 1 commit intoDec 13, 2018
Conversation
mitchell852
added
Traffic Ops
This file contains hidden or 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
What does this PR do?
A previous PR I had (#3100) added some tc-fixture data that added side effects, causing some tests to fail. I reverted the main conflicts. There aren't any conflicts left, but if someone wants to create a parameter that already exists there might be due to how the tests currently POST and DELETE fixture data.
Which TC components are affected by this PR?
What is the best way to verify this PR?
Run the tests, make sure nothing fails related to profiles or parameters.
Right now the CRConfig test is failing for me, but I doubt that's related.
Check all that apply