Allow range of width values in tests #110
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
Windows computers in my CI cluster report different width values than the Windows computers on ci.jenkins.io . The precise width values have not been an issue, so long as they are within reasonable limits.
MarkEWaite
added
the
chore
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.
Allow a range of width values in status image tests
Windows computers in my CI cluster report slightly different values for text widths than the Windows computers on ci.jenkins.io.
Linux and other computers report same values.
Specific values are not as important as keeping the width value within a reasonable range.
Other changes included in the pull request include:
None of those other improvements are substantial enough to justify a separate pull request.