-
-
Notifications
You must be signed in to change notification settings - Fork 620
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
Force consistent stty size on travis #6768
Conversation
It apparently got much narrower yesterday, which causes some tests which are sensitive to stty width (around parsing pytest output) to fail.
stty rows 60 |
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.
A comment would be great as to why. I think its probably horrible that we have tests that parse output (and to boot, in this fragile a way). Calling attention to this magic as a hack to support the test hacks seems like a good idea for future cleanup expeditions to be more fearless.
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.
Very open to feedback on the tests in #6661 which are the relevant ones (which I just added).
In the mean time, I'll add a comment and merge to get master green.
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.
Aha. Well, in that case, setting TERM=dumb and / or COLUMNS=XYZ inside just those tests makes a lot more sense to me.
Both of the failures are flakes, and @illicitonion is gone for the day. Going to merge to get master green, and then we can loop back to isolate the fix. |
This reverts commit b2ac372.
It apparently got much narrower yesterday, which causes some tests which
are sensitive to stty width (around parsing pytest output) to fail.