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

build: disable failing optional travis jobs #27657

Closed

Conversation

devversion
Copy link
Member

@devversion devversion commented Dec 13, 2018

build: disable failing optional travis jobs

  • Disables the failing optional Travis jobs because those just acquire limited resources of Saucelabs and BrowserStack and cause API rate limit problems if the caretaker merges multiple PRs. The rate limit error will spread across multiple repositories because we use the same license in multiple Angular projects (e.g. Angular Material, angular.js etc.)

build: re-enable saucelabs non-verbose logging

  • Previously the logging to TravisCI has been disabled because the print-logs.sh file printed the Sauce-Connect logfile output that is verbose by default. See for example.

    Since the default stderr of sauce-connect is pretty much concise and can alert us if we run into any issues (e.g. rate limit exception), we should stop piping these to /dev/null.

* Disables the failing optional Travis jobs because those just acquire limited resources of Saucelabs and BrowserStack and cause API rate limit problems if the caretaker merges multiple PRs. The rate limit error will spread across multiple repositories because we use the same license in multiple Angular projects (e.g. Angular Material, angular.js etc.)
Previously the logging to TravisCI has been disabled because the `print-logs.sh` file printed the Sauce-Connect logfile output that is `verbose` by default. See [for example](https://travis-ci.org/angular/angular/jobs/250578973).

Since the default stdout/stderr of sauce-connect is pretty much concise and can alert us if we run into any issues (e.g. rate limit, outdated tunnel version), we should stop piping these to `/dev/null`.
@devversion devversion force-pushed the build/update-failing-optional-jobs branch from eebf1e4 to c286d5d Compare December 13, 2018 19:15
@devversion devversion added target: patch This PR is targeted for the next patch release action: review The PR is still awaiting reviews from at least one requested reviewer labels Dec 13, 2018
@IgorMinar IgorMinar added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Dec 14, 2018
mhevery pushed a commit that referenced this pull request Dec 14, 2018
* Disables the failing optional Travis jobs because those just acquire limited resources of Saucelabs and BrowserStack and cause API rate limit problems if the caretaker merges multiple PRs. The rate limit error will spread across multiple repositories because we use the same license in multiple Angular projects (e.g. Angular Material, angular.js etc.)

PR Close #27657
mhevery pushed a commit that referenced this pull request Dec 14, 2018
Previously the logging to TravisCI has been disabled because the `print-logs.sh` file printed the Sauce-Connect logfile output that is `verbose` by default. See [for example](https://travis-ci.org/angular/angular/jobs/250578973).

Since the default stdout/stderr of sauce-connect is pretty much concise and can alert us if we run into any issues (e.g. rate limit, outdated tunnel version), we should stop piping these to `/dev/null`.

PR Close #27657
@mhevery mhevery closed this in 31006f7 Dec 14, 2018
mhevery pushed a commit that referenced this pull request Dec 14, 2018
Previously the logging to TravisCI has been disabled because the `print-logs.sh` file printed the Sauce-Connect logfile output that is `verbose` by default. See [for example](https://travis-ci.org/angular/angular/jobs/250578973).

Since the default stdout/stderr of sauce-connect is pretty much concise and can alert us if we run into any issues (e.g. rate limit, outdated tunnel version), we should stop piping these to `/dev/null`.

PR Close #27657
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 3, 2019
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 3, 2019
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 7, 2019
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 8, 2019
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 8, 2019
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 9, 2019
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 9, 2019
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 9, 2019
gkalpak added a commit to gkalpak/angular.js that referenced this pull request Jan 9, 2019
gkalpak added a commit to angular/angular.js that referenced this pull request Jan 10, 2019
gkalpak added a commit to angular/angular.js that referenced this pull request Jan 10, 2019
ngfelixl pushed a commit to ngfelixl/angular that referenced this pull request Jan 28, 2019
* Disables the failing optional Travis jobs because those just acquire limited resources of Saucelabs and BrowserStack and cause API rate limit problems if the caretaker merges multiple PRs. The rate limit error will spread across multiple repositories because we use the same license in multiple Angular projects (e.g. Angular Material, angular.js etc.)

PR Close angular#27657
ngfelixl pushed a commit to ngfelixl/angular that referenced this pull request Jan 28, 2019
Previously the logging to TravisCI has been disabled because the `print-logs.sh` file printed the Sauce-Connect logfile output that is `verbose` by default. See [for example](https://travis-ci.org/angular/angular/jobs/250578973).

Since the default stdout/stderr of sauce-connect is pretty much concise and can alert us if we run into any issues (e.g. rate limit, outdated tunnel version), we should stop piping these to `/dev/null`.

PR Close angular#27657
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants