1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Commit graph

19 commits

Author SHA1 Message Date
k0kubun
2482d1f9e6 Partially allow failures in test-bundled-gems
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
2019-04-03 12:48:02 +00:00
k0kubun
f4a1235abe vs2019 build is not functional now
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67427 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-04-03 11:16:47 +00:00
k0kubun
5370244337 Azure Pipeline tests on Linux are not reliable
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
2019-04-02 10:51:35 +00:00
k0kubun
c33da35ddf Fix broken retry logic
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
2019-03-29 00:49:35 +00:00
ktsj
831e93d928 Update power_assert to 1.1.4
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
2019-03-24 00:28:51 +00:00
k0kubun
ae0f20c6bf Retry vcpkg install failures
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67324 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-21 05:30:27 +00:00
k0kubun
d4b6198d8f Roughly increase Azure Pipelines fetch depth
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
2019-03-17 05:32:53 +00:00
k0kubun
7fe77cbca9 Ignore test-bundled-gems failure on CI for now
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
2019-03-16 16:53:55 +00:00
k0kubun
46a3b440fd Do not build Azure Pipelines on Pull Request
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
2019-03-16 16:26:44 +00:00
k0kubun
e4885d8acc Use --depth=1 for vs2019 as well
to shorten time to clone

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67162 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-03 13:35:25 +00:00
hsbt
4fd5a9e9bb Try to build readline extension with vcpkg on Azure Pipelines.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67157 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-01 13:16:29 +00:00
hsbt
fe28e007f3 Try to build vs2019preview on Azure Pipelines.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67156 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-01 08:46:07 +00:00
k0kubun
fb04855c41 Drop obsoleted continueOnError
now it's passing thanks to r67149

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67151 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-01 03:56:33 +00:00
k0kubun
7b81d7f5c2 Mark vs2017 build as continueOnError for now
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67145 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-02-28 13:26:14 +00:00
k0kubun
12eca471a4 Revert "Try clean: true for vs2017 checkout failure"
This reverts commit b0e350fe16.

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
2019-02-28 12:47:36 +00:00
k0kubun
b0e350fe16 Try clean: true for vs2017 checkout failure
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
2019-02-28 12:32:24 +00:00
k0kubun
f03775fc0f Try fetchDepth: 1
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67142 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-02-28 12:19:08 +00:00
hsbt
ef8ed5deee Removed fake environment variable because It is not necessary for macOS.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67140 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-02-28 12:01:06 +00:00
hsbt
019864b4a5 Test Bundler examples and bundled gems tests with Azure Pipeline.
* 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
2019-02-27 12:30:24 +00:00