Skip to content
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

Travis tests are hard to quickly parse from their output. #83

Closed
GrayHatter opened this issue Sep 1, 2016 · 0 comments
Closed

Travis tests are hard to quickly parse from their output. #83

GrayHatter opened this issue Sep 1, 2016 · 0 comments
Labels
P3 Low priority
Milestone

Comments

@GrayHatter
Copy link

Ideally, I'd like to see some padding lines with the test that's about to run echo,'d before each test so I can see at a short glance what happened in what order.

================================
==   Running ASTYLE           ==
================================
iphydf added a commit to iphydf/c-toxcore that referenced this issue Sep 13, 2016
This test is already performed by `make test` later on. We originally
had it in the Travis script to make it fail fast when the format is
wrong, but there is also some value in running all tests despite format
errors.

Fixes TokTok#83. There are no more relevant phases that would benefit from the
padding lines proposed.
iphydf added a commit to iphydf/c-toxcore that referenced this issue Sep 14, 2016
This test is already performed by `make test` later on. We originally
had it in the Travis script to make it fail fast when the format is
wrong, but there is also some value in running all tests despite format
errors.

Fixes TokTok#83. There are no more relevant phases that would benefit from the
padding lines proposed.
iphydf added a commit to iphydf/c-toxcore that referenced this issue Sep 16, 2016
This test is already performed by `make test` later on. We originally
had it in the Travis script to make it fail fast when the format is
wrong, but there is also some value in running all tests despite format
errors.

Fixes TokTok#83. There are no more relevant phases that would benefit from the
padding lines proposed.
@iphydf iphydf modified the milestone: v0.0.1 Nov 6, 2016
@iphydf iphydf added the P3 Low priority label Feb 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Low priority
Projects
None yet
Development

No branches or pull requests

2 participants