summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-09-05[rubygems/rubygems] Move build gem logic to its own methodbronzdoc
https://github.com/rubygems/rubygems/commit/a16eacd650
2019-09-05[rubygems/rubygems] Don't fail when `uninstall --all` with default gemDavid Rodríguez
Instead, display an informative message saying that uninstallation of specific versions is being skipped because of being default gems. https://github.com/rubygems/rubygems/commit/b44845aa1d
2019-09-05[rubygems/rubygems] Little refactor to avoid rubocop's false positiveDavid Rodríguez
Otherwise it detects duplicate methods here, because it doesn't see that we are reopening the class in two different places. https://github.com/rubygems/rubygems/commit/ae3fb47f5f
2019-09-05[rubygems/rubygems] Use IAM role to extract security-credentials for EC2 ↵Alexander Pakulov
instance https://github.com/rubygems/rubygems/commit/9a401646e1
2019-09-05[rubygems/rubygems] Move empty check earlierDavid Rodríguez
https://github.com/rubygems/rubygems/commit/fc224e9717
2019-09-05Try to fix `invalid option`Kazuhiro NISHIYAMA
https://github.com/ruby/ruby/runs/212727409#step:11:67 ``` invalid option: -j5 ```
2019-09-05Change name to `Tests (test-bundled-gems)` in macos.yml tooKazuhiro NISHIYAMA
2019-09-05add tests卜部昌平
Some coverage improvements.
2019-09-05Removed -git option of make-snapshotNobuyoshi Nakada
Git is not for direct access to a remote repository. Most of its operations need a local clone.
2019-09-05interesting (but annoying) tidbit warning suppressed卜部昌平
This changeset is to suppress clang's -Wimplicit-int-float-conversion warning. In 64 bit signed long and IEEE 754 double combination (== almost everyone these days), LONG_MAX is 9,223,372,036,854,775,807. This value is _not_ exactly representable by double. The nearest value that a double can represnt is 9,223,372,036,854,775,808. It is one greater than LONG_MAX. Let's call this value the "x". The expression `LONG_MAX < yi` is a long versus double comparison. According to ISO/IEC 9899:1999 Section 6.3.1.8 (that defines the "usual rithmetic conversions"), The long value must first be casted into double. Because FLT_ROUNDS is typically 1 ("round to the nearest" mode), the conversion yields the "x" value shown above. So the comparison is in fact `x < yi`. This comparison is false for yi == x situation, i.e. yi is still bigger than LONG_MAX. On such situation the `yn = (long)yi;` statement that appear several lines below renders underfined behaviour, as per ISO/IEC 9899:1999 Section 6.3.1.3. To remedy, we just change the comparison from `<` to `<=` so that yi == x situation can properly be handled.
2019-09-05hide rb_funcallv_with_cc from public卜部昌平
Requested by ko1. Also, because now that this function is internal use only, why not just directly use struct rb_call_cache to purge the ZALLOC.
2019-09-05use existing vm_search_method()卜部昌平
Ko1 plans to implement Guild. That can interface the caching mechanism introduced here. To prevent future breakage we would better avoid rolling our own code here. Instead use the existing vm_search_method() which would be modified by him. This commit deletes some asserions, but they are in fact checked inside of vm_search_method().
2019-09-05* 2019-09-05 [ci skip]git
2019-09-05Separate VCS::DEBUG_OUTNobuyoshi Nakada
2019-09-04Describe #eager in the Enumerator::Lazy sectionAkinori MUSHA
2019-09-04Implement Enumerator::Lazy#eager [Feature #15901]Akinori MUSHA
2019-09-04add rb_funcallv_with_cc()Urabe, Shyouhei
Why not cache the method entry at each caller site. The void** is in fact a method entry, but this struct is hidden from ruby.h so intentionally left opaque. Notes: Merged: https://github.com/ruby/ruby/pull/1981
2019-09-04Add TEST_BUNDLED_GEMS_ALLOW_FAILURES=minitestKazuhiro NISHIYAMA
2019-09-04Use `git pull` instead of `git fetch` if master branchKazuhiro NISHIYAMA
2019-09-04`$JOBS` does not set in `env:`Kazuhiro NISHIYAMA
2019-09-04Use RUBY_TESTOPTS instead of TESTOPTSKazuhiro NISHIYAMA
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.
2019-09-04Check frozen flag on MJIT setinstancevariableTakashi Kokubun
It does not seem to have a significant performance impact, hopefully? ``` $ benchmark-driver -v benchmark.yml --rbenv 'before --jit;after --jit' --repeat-count=24 --output=all before --jit: ruby 2.7.0dev (2019-09-03T21:02:24Z master 77596fb7a9) +JIT [x86_64-linux] after --jit: ruby 2.7.0dev (2019-09-04T01:54:44Z master 7363e22d79) +JIT [x86_64-linux] Calculating ------------------------------------- before --jit after --jit Optcarrot Lan_Master.nes 48.44054595799523 71.67010255902900 fps 71.32797692837639 71.97846863769546 72.51921961607691 78.87360980544105 73.54082925611047 79.80408132389941 74.03503843709451 79.85739528572826 74.04863857926493 79.89850834901381 75.30266276129467 80.34607233076015 75.69063990896244 80.88474397425360 75.70458132587405 81.09234267781642 77.39842764662852 82.13766823612643 77.76922944068329 82.20398304840373 81.17984044023393 82.26722630628272 82.85235776076533 82.71375902781254 83.04906099135320 82.75893420702198 83.10214168136230 82.79668965325972 83.71456007558125 82.85131667916379 84.06658306760725 82.95676565411722 84.25690684305728 83.19972846225775 84.27938663923503 83.28510503845854 84.45467716218090 83.41003730434703 84.51563186125925 83.67773614721280 84.56139892968321 84.02082201151110 84.69819452180658 84.10495346787033 84.78125989622576 84.47867803506055 ``` Note for backporter: test_jit's `success_count` would be 1 in Ruby 2.6, since 2.7 introduced "MJIT recompile" on JIT-ed code cancel. [Bug #16139]
2019-09-03Do not turn on keyword_init for Struct subclass if keyword hash is emptyJeremy Evans
This was accidentally turned on because there was no checking for Qundef. Also, since only a single keyword is currently supported, simplify the rb_get_kwargs call. Notes: Merged: https://github.com/ruby/ruby/pull/2423 Merged-By: jeremyevans <code@jeremyevans.net>
2019-09-03Merge pull request #2422 from jeremyevans/rb_keyword_given_pJeremy Evans
Add rb_keyword_given_p to the C-API Notes: Merged-By: jeremyevans <code@jeremyevans.net>
2019-09-04* 2019-09-04 [ci skip]git
2019-09-03Fix Enumerator::Lazy#{to_enum,enum_for} where method is defined in LazyJeremy Evans
Previously, passing to_enum/enum_for a method that was defined in Lazy itself returned wrong results: [1,2,3].to_enum(:map).to_a # => [1, 2, 3] [1,2,3].lazy.to_enum(:map).to_a # => [] I'm not sure why methods that are designed to be lazy do not work with to_enum/enum_for. However, one possible way to work around this bug is to have to_enum/enum_for use the implementation found in Enumerable/Enumerator, which is what this commit does. While this commit works around the problem, it is a band-aid, not a real fix. It doesn't handle aliases of Enumerable::Lazy methods, for instance. A better fix would be appreciated. Notes: Merged: https://github.com/ruby/ruby/pull/2421
2019-09-03Remove bad expectation in specJeremy Evans
This spec should not be checking where methods are defined, only that the method works as expected (returns a Lazy instance). Notes: Merged: https://github.com/ruby/ruby/pull/2421
2019-09-03Make Enumerator::Lazy#with_index be lazyJeremy Evans
Previously, Enumerator::Lazy#with_index was not defined, so it picked up the default implementation from Enumerator, which was not lazy. Based on earlier patch from nobu. Fixes [Bug #7877] Notes: Merged: https://github.com/ruby/ruby/pull/2421
2019-09-03Move an unstable bootstraptest to pendingTakashi Kokubun
This has been unstable on AppVeyor mswin since the introduction 3fd83cb6fcc483d2eac0795bc139c521a3a59bd2. https://ci.appveyor.com/project/ruby/ruby/builds/27103307/job/j7xwjmsos2k22cck Let's have it in pending.rb to be fixed.
2019-09-03Stop testing inexistent instructionsTakashi Kokubun
2019-09-03Unify SUPPORT_JOKE and OPT_SUPPORT_JOKETakashi Kokubun
for simplicity and consistency. Now SUPPORT_JOKE needs to be prefixed with OPT_ to make the config visible in `RubyVM::VmOptsH`, and the inconsistency was introduced. As it has never been available for override in configure (no #ifndef guard), it should be fine to rename the config.
2019-09-03Roughly retry choco install commandsTakashi Kokubun
to deal with random failures: https://github.com/ruby/ruby/runs/210617845
2019-09-03Try extending timeout of IO.selectTakashi Kokubun
hoping to stabilize: https://app.wercker.com/ruby/ruby/runs/mjit-test1/5d6df8a8a952c20008acf75b?step=5d6df90e4971a6000714c627
2019-09-03Remove SKIP_DOXYGEN because job.env does not set in `if:`Kazuhiro NISHIYAMA
2019-09-03Examine TestIO#test_select_exceptfds on Solaris with 1 byte dataNaohisa Goto
On Solaris, it seems that the select(3C) in this test works only when sending 1 byte out-of-band data, though I cannot investigate the cause. The behavior is observed on a Solaris 10 server in addition to Solaris 11 on which the test had been skipped.
2019-09-03delete ruby_eval_string_from_file_protect卜部昌平
Not used from anywhere.
2019-09-03Avoid defining unused instructionsTakashi Kokubun
Notes: Merged: https://github.com/ruby/ruby/pull/2420
2019-09-03Disable method definition type checks on Cygwin tood0 (Daisuke Fujimura)
[Bug #16134]
2019-09-03test/ruby/test_fiber.rb: reduce the count of object creation to cause GCYusuke Endoh
The test consistently fails on OpenBSD. https://rubyci.org/logs/rubyci.s3.amazonaws.com/openbsd-current/ruby-master/log/20190903T010009Z.fail.html.gz ``` 1) Failure: TestFiber#test_fork_from_fiber [/home/chkbuild/chkbuild/tmp/build/20190903T010009Z/ruby/test/ruby/test_fiber.rb:327]: [ruby-core:41456]. <0> expected but was <1>. ```
2019-09-03Touch tar file itself to make gz file hash stableNobuyoshi Nakada
2019-09-03Touch the toplevel directory tooNobuyoshi Nakada
2019-09-03--date=iso-local does not work with old gitNobuyoshi Nakada
2019-09-03Do not keep tar file by the defaultNobuyoshi Nakada
2019-09-03Align timestamps to make tarball stableNobuyoshi Nakada
2019-09-02Make Array#uniq return subclass instance if called on subclass instanceJeremy Evans
Previously, Array#uniq would return subclass instance if the length of the array were 2 or greater, and would return Array instance if the length of the array were 0 or 1. Fixes [Bug #7768]
2019-09-03Make the rb_vmdebug_debug_print_post declarationTakashi Kokubun
consistent with the definition
2019-09-03Add insn tests for newarraykwsplatTakashi Kokubun
2019-09-03Explain how to run an individual btest in helpTakashi Kokubun
2019-09-03Now it's always os: linuxTakashi Kokubun
2019-09-03Fix accidental leftover for LinuxTakashi Kokubun
In 91aa8bfff8, my understanding of the branch was inverted.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-21 19:16:47 +0000