aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #2422 from jeremyevans/rb_keyword_given_pJeremy Evans2019-09-036-3/+30
| | | Add rb_keyword_given_p to the C-API
* * 2019-09-04 [ci skip]git2019-09-041-1/+1
|
* Fix Enumerator::Lazy#{to_enum,enum_for} where method is defined in LazyJeremy Evans2019-09-032-1/+116
| | | | | | | | | | | | | | | | | | | 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.
* Remove bad expectation in specJeremy Evans2019-09-031-1/+0
| | | | | This spec should not be checking where methods are defined, only that the method works as expected (returns a Lazy instance).
* Make Enumerator::Lazy#with_index be lazyJeremy Evans2019-09-032-0/+88
| | | | | | | | | | 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]
* Move an unstable bootstraptest to pendingTakashi Kokubun2019-09-032-3/+5
| | | | | | | | 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.
* Stop testing inexistent instructionsTakashi Kokubun2019-09-031-9/+5
|
* Unify SUPPORT_JOKE and OPT_SUPPORT_JOKETakashi Kokubun2019-09-034-5/+4
| | | | | | | | | | 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.
* Roughly retry choco install commandsTakashi Kokubun2019-09-031-1/+6
| | | | | to deal with random failures: https://github.com/ruby/ruby/runs/210617845
* Try extending timeout of IO.selectTakashi Kokubun2019-09-031-1/+2
| | | | | hoping to stabilize: https://app.wercker.com/ruby/ruby/runs/mjit-test1/5d6df8a8a952c20008acf75b?step=5d6df90e4971a6000714c627
* Remove SKIP_DOXYGEN because job.env does not set in `if:`Kazuhiro NISHIYAMA2019-09-031-18/+0
|
* Examine TestIO#test_select_exceptfds on Solaris with 1 byte dataNaohisa Goto2019-09-031-3/+5
| | | | | | | 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.
* delete ruby_eval_string_from_file_protect卜部昌平2019-09-031-21/+0
| | | | Not used from anywhere.
* Avoid defining unused instructionsTakashi Kokubun2019-09-034-20/+25
|
* Disable method definition type checks on Cygwin tood0 (Daisuke Fujimura)2019-09-032-2/+2
| | | | [Bug #16134]
* test/ruby/test_fiber.rb: reduce the count of object creation to cause GCYusuke Endoh2019-09-031-1/+3
| | | | | | | | | | | | | 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>. ```
* Touch tar file itself to make gz file hash stableNobuyoshi Nakada2019-09-031-0/+1
|
* Touch the toplevel directory tooNobuyoshi Nakada2019-09-031-2/+5
|
* --date=iso-local does not work with old gitNobuyoshi Nakada2019-09-031-2/+8
|
* Do not keep tar file by the defaultNobuyoshi Nakada2019-09-031-5/+5
|
* Align timestamps to make tarball stableNobuyoshi Nakada2019-09-031-12/+40
|
* Make Array#uniq return subclass instance if called on subclass instanceJeremy Evans2019-09-022-4/+33
| | | | | | | | 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]
* Make the rb_vmdebug_debug_print_post declarationTakashi Kokubun2019-09-031-1/+5
| | | | consistent with the definition
* Add insn tests for newarraykwsplatTakashi Kokubun2019-09-032-0/+5
|
* Explain how to run an individual btest in helpTakashi Kokubun2019-09-031-1/+1
|
* Now it's always os: linuxTakashi Kokubun2019-09-031-19/+3
|
* Fix accidental leftover for LinuxTakashi Kokubun2019-09-031-1/+0
| | | | In 91aa8bfff8, my understanding of the branch was inverted.
* Drop unstable Travis osx in favor of GitHub ActionsTakashi Kokubun2019-09-035-58/+2
| | | | | | | | | | | | For some reason, the Travis osx environment has been really unstable. It failed on today's cron too: https://travis-ci.org/ruby/ruby/builds/579843163 As we have almost the same test environment (including OpenSSL version) in GitHub Actions and it seems to be more stable and faster, I think there's no motivation to maintain Travis osx CI environment. By removing this, we'd be able to simplify .travis.yml as well.
* Drop obsoleted IRC channel referenceTakashi Kokubun2019-09-031-1/+0
| | | | | travis-ci user does not live in #ruby-ja. Therefore the notification isn't working anymore.
* Drop obsoleted branch referencesTakashi Kokubun2019-09-031-3/+0
| | | | We don't have topic branches on ruby.git anymore.
* Use -z option for git-logNobuyoshi Nakada2019-09-031-3/+1
|
* Merge pull request #2418 from jeremyevans/array-empty-kwsplatJeremy Evans2019-09-023-2/+63
| | | Ignore empty keyword splats in arrays
* * 2019-09-03 [ci skip]git2019-09-031-1/+1
|
* Fix SUPPORT_JOKE CI on TravisTakashi Kokubun2019-09-031-1/+2
| | | | It looks like a flag which cannot be enabled on configure.
* Run daily cron against SUPPORT_JOKETakashi Kokubun2019-09-021-0/+10
|
* Fix compilation error in SUPPORT_JOKETakashi Kokubun2019-09-021-3/+4
| | | | This seems to have been broken since 4e15be8bade.
* Extract git commit log as raw format like git-svn for ChangeLogNobuyoshi Nakada2019-09-021-24/+22
|
* test/drb/drbtest.rb: Skip test_06_timeout on Solaris10sYusuke Endoh2019-09-021-6/+9
| | | | | | | | | | The test seems to have a race condition, which fails on very slow machine like Solaris10s. So skip it. In addition, this change restores timeout guard that was removed at 0660d7cb538cf5284d50f66adfcbd78609839715. This is because the test gets stuck forever when something wrong occurs. It is better to fail the test than stuck.
* Do not clear backtrace in Exception#exceptionNobuyoshi Nakada2019-09-022-2/+14
| | | | [Bug #15558]
* Rewrote using assert_separatelyNobuyoshi Nakada2019-09-021-16/+8
|
* Prohibit nul-separated glob pattern [Feature #14643] (#2419)Nobuyoshi Nakada2019-09-024-28/+23
|
* Add Net::FTP#features and Net::FTP#optionShugo Maeda2019-09-023-0/+135
| | | | | Patch by darkphnx (Dan Wentworth) . Thanks! [Feature #15964]
* Get rid of interpreting BTS references as label-list [ci skip]Nobuyoshi Nakada2019-09-021-8/+8
|
* Revert "Make Enumerator::Lazy#with_index be lazy"Jeremy Evans2019-09-012-88/+0
| | | | | | This reverts commit 83498854eb5a824f1f83c31fac18c9279f9ee10d. This didn't pass rubyspec.
* Fix opt_regexpmatch1 referencesTakashi Kokubun2019-09-022-6/+3
|
* Make Enumerator::Lazy#with_index be lazyJeremy Evans2019-09-012-0/+88
| | | | | | | | | | 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]
* fix shortcut conditionUrabe, Shyouhei2019-09-021-0/+1
| | | | | rb_reg_match expects its first argument to be a Regexp instance. Should check that.
* delete unused functionUrabe, Shyouhei2019-09-021-11/+0
|
* opt_regexpmatch1 is actually making things slower.Urabe, Shyouhei2019-09-023-31/+8
| | | | | | | | | | | | | | | | ---- trunk: ruby 2.6.0dev (2018-09-18 trunk 64767) [x86_64-darwin15] ours: ruby 2.6.0dev (2018-09-18 opt_regexpmatch 64775) [x86_64-darwin15] last_commit=opt_regexpmatch1 is actually making things slower. Calculating ------------------------------------- trunk ours Optcarrot Lan_Master.nes 33.877 35.282 fps Comparison: Optcarrot Lan_Master.nes ours: 35.3 fps trunk: 33.9 fps - 1.04x slower
* Add a benchmark for opt_regexpmatch2Takashi Kokubun2019-09-021-0/+2
| | | | vm2_regexp was for opt_regexpmatch1.
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-18 21:27:02 +0000