Age | Commit message (Collapse) | Author |
|
Let's stop reporting the failure until it gets stable.
We can see the build status on console with this config anyway.
|
|
to fix
https://dev.azure.com/rubylang/ruby/_build/results?buildId=1162&view=logs
|
|
to avoid cancelling overall build pipeline when stucking there.
|
|
It has not been stable recently. Let's stop notifying them for now.
|
|
This reverts commit 1ebe9a2f82fef5190454e68d430004282f5da172.
because it did not help.
|
|
CI seems to have a weired behavior now. Debugging.
Revert "azure-pipelines.yml: Fix typo"
This reverts commit f69d28fbca1eec8b9722cea1f989ee9554e8dad5.
Revert "azure-pipelines.yml: Use simpler trigger syntax"
This reverts commit 709756d89747bd36664593eda4156a7bf5ad7631.
Revert "azure-pipelines.yml: Do not run CI on trunk"
This reverts commit bec877b46fd4d0f621a75591b519a7e266eaa89b.
Revert "appveyor.yml: Do not doubly run CI on trunk"
This reverts commit d9b338a53f520b2dbb05555f18b8de8072300f40.
|
|
|
|
|
|
|
|
It looks like the old definition was not working as intended...
https://dev.azure.com/rubylang/ruby/_build/results?buildId=394
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67557 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
it seems not working in
https://dev.azure.com/rubylang/ruby/_build/results?buildId=392
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67555 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67510 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67509 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67508 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
trying to fix
https://dev.azure.com/rubylang/ruby/_build/results?buildId=363
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67507 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
Tests of minitest randomly fails with strange errors:
https://dev.azure.com/rubylang/ruby/_build/results?buildId=303
https://dev.azure.com/rubylang/ruby/_build/results?buildId=314
Instead of marking `continueOnError` for all, let me select
failure-allowed gems individually.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67428 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67427 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
test-bundler started to fail with r67383
https://dev.azure.com/rubylang/ruby/_build/results?buildId=278
which is very unlikely to be Ruby implementation's fault.
test-bundled_gems also started to fail with r67413
https://dev.azure.com/rubylang/ruby/_build/results?buildId=303
I'm not sure the commit is related to the failure.
Overall, they are not useful as testing environment of Ruby itself for
now since nobody seems to take care of these CI statuses. Let's stop
reporting the status to GitHub until it becomes reliable.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67414 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
previous retry logic did not work
https://dev.azure.com/rubylang/ruby/_build/results?buildId=266
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67367 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
This update fixes a failure of test-bundled-gems, so we revert r67275.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67340 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67324 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
because --depth=1 may randomly break checkout:
https://dev.azure.com/rubylang/ruby/_build/results?buildId=208&view=logs&jobId=7ded14dc-7a77-59da-f40a-71e137ad96c0&taskId=2045950f-1dcd-54a4-4c23-fae2521239c1&lineStart=1554&lineEnd=1555&colStart=1&colEnd=1
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67280 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
ktsj-san recognizes this issue and it's intentionally left failing now.
As failure notification of this task is NOT indicating ruby is broken,
let's stop notifying the failure fo rnow.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67275 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
For 2 reasons:
* bundled_gems tend to be left broken (like now)
* We don't want Slack notification for pull request and it can't be
disabled on Azure Pipelines
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67273 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
to shorten time to clone
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67162 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67157 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67156 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
now it's passing thanks to r67149
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67151 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67145 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
This reverts commit b0e350fe16ad17eabf5bbc603f7d817c06ce8554.
The issue seems to be invalid tag name including `"` in ancient tag.
We're trying to delete that.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67144 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
https://dev.azure.com/rubylang/ruby/_build/results?buildId=107
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67143 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67142 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67140 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
* They are invoked on Linux and macOS environment.
* Try to build with vs2017. But it's only binary build.
https://dev.azure.com/rubylang/ruby/
[Feature #15181][ruby-core:89222]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67137 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|