Skip to content

Better log output for Saucelabs connect tunnel #27691

Closed

Description

@devversion

Jobs which are unable to even establish a Saucelabs tunnel instance, just print out dots for 10 minutes until Travis terminates the job.

This is not helpful because usually this happens if the API rate limit has been exceeded, and it would be good to log this into the console. Additionally it might be good to add a timeout of ~2 minutes since we don't want Travis to terminate the job, and rather print the log output before exiting.

See: https://travis-ci.org/angular/angular/jobs/468233060#L692

We might be able to just re-add a log file by using stdout and stderr instead of the Saucelabs --logfile option (as this is always verbose and can overwhelm travis)

Activity

  1. added this to the needsTriage milestone on Dec 15, 2018
  2. devversion commented on Jan 9, 2019

    @devversion
    MemberAuthor

    Fixed with #27937

  3. angular-automatic-lock-bot commented on Sep 14, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  4. locked and limited conversation to collaborators on Sep 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: build & ciRelated the build and CI infrastructure of the project

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions