Skip to content

Conversation

@petertseng
Copy link
Member

@petertseng petertseng commented Mar 4, 2018

Otherwise, Travis may assume we're hung if we don't produce output in
10+ minutes. Normally we don't think checking all exercises takes this
long, but this prepares for the future and prevents spurious failures in
instances when outside circumstances cause slowness.

This approach was suggested in response to such a failure in
#435 (comment)

Otherwise, Travis may assume we're hung if we don't produce output in
10+ minutes. Normally we don't think checking all exercises takes this
long, but this prepares for the future and prevents spurious failures in
instances when outside circumstances cause slowness.

This approach was suggested in response to such a failure in
#435 (comment)
@petertseng petertseng merged commit dbffe82 into exercism:master Mar 4, 2018
@petertseng petertseng deleted the progress-warning branch March 4, 2018 19:54
./bin/test-exercise $directory --quiet --no-run
# Output a progress dot; otherwise Travis may assume we're hung,
# if we don't produce output in > 10 mins.
echo -n '.'
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope, bad, now $? will always be 0. Move this before bin/test-exercise please.

petertseng added a commit that referenced this pull request Mar 5, 2018
Notice that below `test-exercise` there is a check of `$?`. This means
nothing should come after `test-exercise`.

If we fail to do this, warnings will never cause the build to fail (as
we would like them to), because the `$?` is examining the exit code of
`echo`.

We need to move the `echo` (progress dot) that we added in
#446
a3a7b16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants