Commit graph

11 commits

Author SHA1 Message Date
Jean Boussier
1f9b792168 macOS: Use GMP from homebrew
MRI's BigInt use GMP under the hood if available, and if not
fallbacks to an homemade implementation with much worse performance.

Without GMP:
```
>> Benchmark.realtime { Integer('1' * (10 ** 7)) }
=> 13.80743500002427
```

With GMP
```
>> Benchmark.realtime { Integer('1' * (10 ** 7)) }
=> 0.4098639999865554
```

macOS not being a common production platform, it's not a huge deal
but it would still preferable to compile with `gmp.h` if present.

I'd also suggest to print a warning if compiling on macOS and gmp
isn't installed, but I don't know if it's desirable.

NB: `--with-gmp-dir` was only added recently, so this will only
apply to MRI >= 3.2, as well as rubies on which this flag was backported.
2022-09-22 08:56:34 +02:00
Mislav Marohnić
7f368a7592 Update ruby-build download mirror in GitHub Actions 2021-07-15 20:57:14 +02:00
Benoit Daloze
ebdcf0c26e Only do script/mirror update on TravisCI
* Testing is done on GitHub Actions which is much faster.
2021-07-07 20:04:22 +02:00
Benoit Daloze
964e83a039 Run script/mirror verify on GitHub Actions too
* So the shasums are checked in PRs.
2021-07-07 20:04:22 +02:00
Jason Karns
d5de31f490 TRAVIS_COMMIT_RANGE is correct now
According to https://github.com/travis-ci/travis-ci/issues/1719 (closed by https://github.com/travis-ci/travis-core/pull/383), the behavior of $TRAVIS_COMMIT_RANGE should be correct now. We should be able to use it directly.
2015-11-04 11:05:41 -05:00
Mislav Marohnić
fc5e392a54 Set Travis-specific PATH in travis.yml 2015-02-27 02:16:46 +13:00
Mislav Marohnić
d7b881d20e Fix script/test in a non-Travis environment
`script/test` will now only attempt to call `script/mirror` if either
TRAVIS_PULL_REQUEST or TRAVIS_COMMIT_RANGE is set.
2014-11-16 17:17:35 -08:00
Mislav Marohnić
b14f8c0536 Fill in TRAVIS_COMMIT_RANGE if missing
Workaround for travis-ci/travis-ci#1719
2014-09-09 23:24:14 -07:00
Mislav Marohnić
3add5c4637 Verify checksums for pull requests from other people
This has the CI step verify the checksums for URLs that might have been
added or edited to build definitions in a pull request.
2014-09-08 09:14:43 -07:00
Mislav Marohnić
4ed38ba4bc Run mirror update on CI even if tests failed
If a commit introduced a new Ruby definition, we want it mirrored even
if there might have been an accidental failure on CI.
2013-10-28 02:25:08 +01:00
Mislav Marohnić
4817d20938 Keep mirror up-to-date using Travis CI
When new Ruby definitions get added, our current CloudFront mirror may
get out of date. This adds a task to the CI process that detects
added/changed package URLs and uploads them to our S3 bucket.

Fixes #392, references #395
2013-10-24 17:44:41 +02:00