Skip to content

compact display is only compact for wide terminal windows #288

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

Closed
skybrian opened this issue Jul 14, 2015 · 1 comment
Closed

compact display is only compact for wide terminal windows #288

skybrian opened this issue Jul 14, 2015 · 1 comment
Labels
closed-duplicate Closed in favor of an existing report

Comments

@skybrian
Copy link

When I run the protobuf tests, it looks like it doesn't clear the line properly when the window isn't wide enough to display the filename and test name together. (I use fairly long test names, so perhaps that triggers this effect.)

Example output:

With a wide window:

$ pub run test
00:01 +33: All tests passed!                                                                       
skybrian@skybrian5:~/dart/work/dart-protobuf
$ 

With a normal sized window:

$ pub run test
00:00 +0: loading test/readonly_message_test.dart             00:01 +0: loading test/coded_buffer_reader_test.dart          00:01 +0: test/readonly_message_test.dart: can write a read-on00:01 +1: test/readonly_message_test.dart: can write a read-on00:01 +2: test/json_test.dart: testWriteToJson                00:01 +3: test/json_test.dart: testWriteToJson                00:01 +4: test/json_test.dart: testWriteToJson                00:01 +5: test/json_test.dart: testWriteToJson                00:01 +6: test/json_test.dart: testWriteToJson                00:01 +7: test/json_test.dart: testWriteToJson                00:01 +8: test/json_test.dart: testWriteToJson                00:01 +9: test/json_test.dart: testWriteToJson                00:01 +10: test/json_test.dart: testWriteToJson               00:01 +11: test/json_test.dart: testWriteToJson               00:01 +12: test/reserved_names_test.dart: GeneratedMessage res00:01 +13: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +14: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +15: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +16: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +17: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +18: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +19: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +20: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +21: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +22: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +23: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +24: test/coded_buffer_reader_test.dart: testCodedBuffer00:01 +25: test/codec_test.dart: testFloat                    00:01 +26: test/codec_test.dart: testFloat                    00:01 +27: test/codec_test.dart: testFloat                    00:01 +28: test/codec_test.dart: testFloat                    00:01 +29: test/codec_test.dart: testFloat                    00:01 +30: test/codec_test.dart: testFloat                    00:01 +31: test/codec_test.dart: testFloat                    00:01 +31: test/codec_test.dart: testDouble                   00:01 +32: test/codec_test.dart: testDouble                   00:01 +32: test/codec_test.dart: testVarint                   00:01 +33: test/codec_test.dart: testVarint                   00:01 +33: All tests passed! 

skybrian@skybrian5:~/dart/work/dart-protobuf
$ 

(It's actually displayed better than that in the terminal window; each output line is on a separate line but they're all flush left.)

This is using GNOME Terminal 3.6.2, but I think it was similar on my Mac. (I didn't realize that it was a bug and was trying to figure out why some tests were being printed but not others.)

@nex3
Copy link
Member

nex3 commented Jul 14, 2015

There are a long chain of blocked issues that mean the test runner can't use stdout.terminalColumns to detect how wide your terminal is, so it just limits its line width to 100 characters. If your terminal isn't 100 characters wide, you see effects like this. The best workaround at the moment is to either make your terminal wider or use -r expanded.

Duplicate of #86.

@nex3 nex3 added type-enhancement A request for a change that isn't a bug status-blocked Blocked from making progress by another (referenced) issue closed-duplicate Closed in favor of an existing report and removed status-blocked Blocked from making progress by another (referenced) issue labels Jul 14, 2015
@nex3 nex3 closed this as completed Jul 14, 2015
@nex3 nex3 removed the type-enhancement A request for a change that isn't a bug label Jul 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report
Projects
None yet
Development

No branches or pull requests

2 participants