| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
https://github.com/ruby/ruby/runs/224877570#step:3:1008
```
Error: No such file or directory @ dir_s_rmdir - /Users/runner/Library/Caches/Homebrew/downloads/ca756e367eb98d2b525e72b311633c27ffc74eca825a5392153b3488d1adb732--libssh2-1.9.0.mojave.bottle.tar.gz
```
|
| |
|
| |
|
| |
|
|
|
|
|
| |
https://docs.aws.amazon.com/cli/latest/reference/s3/sync.html
> --no-progress (boolean) File transfer progress is not displayed. This flag is only applied when the quiet and only-show-errors flags are not provided.
|
| |
|
|
|
|
|
|
|
| |
https://github.com/ruby/ruby/runs/212727409#step:11:67
```
invalid option: -j5
```
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
https://github.com/ruby/ruby/pull/2417#issuecomment-526884646
> `TESTOPTS` is defaulted to `$(RUBY_TESTOPTS)` in `common.mk` file.
> Use the latter name to pass options via an environment variable.
|
|
|
|
|
| |
to deal with random failures:
https://github.com/ruby/ruby/runs/210617845
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
because default value overrides it.
https://help.github.com/en/articles/virtual-environments-for-github-actions#environment-variables
|
| |
|
| |
|
|
|
|
|
|
|
| |
- Fix checkout error: `fatal: destination path '.' already exists and is not an empty directory.`
- Remove `GITHUB_SHA` in env, because set automatically
https://help.github.com/en/articles/virtual-environments-for-github-actions#environment-variables
- Change minute from 0 to 20 for test soon
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
a little.
Doing both `git clone --depth=1` and `git reset --hard ${sha}` does not
make sense (the latter command either does nothing or just fails), so I
added non-1 value as a depth.
Maybe we don't need depth=50 for pull_request and schedule, so it's 10
for now.
|
|
|
|
| |
workflows, because mame said he has never seen it.
|
| |
|
| |
|
|
|
| |
* .github/workflows/doxygen.yml: add a workflow for doxygen in Actions
|
|
|
|
|
|
| |
This reverts commit 9bc1667a188392b94971b9b96507af76cbd5f413.
`name` lines are not expanded.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Expand JOBS instead of meaningless export
* Remove -j option in TESTOPTS of test-bundled-gems
https://github.com/ruby/ruby/runs/203129516#step:10:167
> invalid option: -j3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with Travis, rather than AppVeyor.
Formerly it was made similar to AppVeyor to provide some normal set of
CI failure notification. But for some reason people preferred a shorter
variant and introduced a1d606c079f6c3d1779d885e0bf2e3991251609e and
d8d8015b93c6daa8d8433895464db3493a2056e2.
Instead of AppVeyor format, this commit chose Travis-like format to achieve
consistency and to include usual CI-failure information, while keeping
it one-liner for people who prefer short notifications.
Note that this shrinks the 40-char sha to 10-char, using the new feature
of k0kubun/action-slack@v2.0.0:
https://github.com/k0kubun/action-slack/commit/1c88a05dac664cbafa1c99a37f292ed23ac1c289
|
| |
|
| |
|
|
|
|
|
|
| |
sometimes Slack notification footer becomes just " at ".
It seems like `github.event.head_commit` is missing. Let me debug the
context.
|
|
|
|
|
| |
It seems that we cannot easily apply job-level [ci skip].
Therefore this commit skips only Tests step if it's [ci skip].
|
| |
|
|
|
|
| |
as it failed randomly https://github.com/ruby/ruby/runs/196712109
|
|
|
|
|
|
| |
by marking continue-on-error.
I dropped it to test Slack notification, and I finished to test it.
|
|
|
|
| |
by using toJson with fields.
|
|
|
|
|
|
| |
for macOS / Windows as well.
Docker-based GitHub Action does not work on these OSes.
|
| |
|
|
|
|
|
|
| |
This reverts commit d8807e8b1a9d09ee1543e18618b4ef7e8203c616.
We'd need more features. Reverting to customize this later.
|
|
|
|
|
| |
https://github.com/8398a7/action-slack
https://github.com/marketplace/actions/action-slack
|
|
|
|
| |
Like macos.yml, we don't need to ignore `make check` failure.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This is default: true
https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast
When `make check` fails, we do not want to cancel `make test-bundler`.
|
|
|
|
|
| |
because these tests have failed too often and it's false-positive for
checking healthiness of the master branch.
|
| |
|