Yusuke Endoh
5dd8fdd3f3
test/net/imap/test_imap.rb: wait for the server thread to start
...
In some slow CI environments, the invocation of a thread seems very
slow. This causes a test failure to attempt to connect a server that
does not start yet.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-master/log/20190615T002420Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-master/log/20190611T022407Z.fail.html.gz
2019-06-15 11:06:39 +09:00
Nobuyoshi Nakada
d365fd5a02
An operator is not allowed just after `|>`
...
https://twitter.com/yukihiro_matz/status/1139454774640726019
2019-06-14 18:17:50 +09:00
Kazuhiro NISHIYAMA
d780c36624
Pipeline operator is experimental [ci skip]
2019-06-14 17:30:12 +09:00
Nobuyoshi Nakada
aa32465ab3
irb.rb: [DOC] the default prompt includes :PROMPT_N [ci skip]
2019-06-14 15:31:03 +09:00
Nobuyoshi Nakada
50bb8b6052
Use Exception#full_message for traceback
2019-06-14 08:46:22 +09:00
aycabta
9402d019a5
Remove debug print
2019-06-14 08:45:52 +09:00
aycabta
d0e5564140
Set allow_escape_code for prompt
2019-06-14 08:45:35 +09:00
aycabta
f80771f0a9
Use Reline.prompt_proc in IRB
2019-06-14 08:26:06 +09:00
git
3757e492fb
* 2019-06-14
2019-06-14 07:46:01 +09:00
aycabta
64310b2573
Add Reline.prompt_proc
2019-06-14 07:42:53 +09:00
Yusuke Endoh
56d595198b
test/webrick/test_ssl_server.rb: Use EnvUtil.timeout for timeout scale factor
...
https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-master/log/20190613T091708Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-master/log/20190612T011708Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-master/log/20190611T211707Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-master/log/20190604T171708Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-master/log/20190529T091707Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-master/log/20190528T031708Z.fail.html.gz
2019-06-13 23:04:41 +09:00
Yusuke Endoh
e75c278183
test/lib/test/unit/assertions.rb (assert_cpu_usage_low): tweak the wait
...
It still fails randomly.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/amazon2/ruby-master/log/20190613T093003Z.fail.html.gz
https://rubyci.org/logs/mswinci.japaneast.cloudapp.azure.com/vc12-x64/ruby-master/log/20190613T051547Z.fail.html.gz
2019-06-13 22:44:01 +09:00
Nobuyoshi Nakada
aa7211836b
Continue to the next line beginning with a pipeline
2019-06-13 22:19:47 +09:00
Nobuyoshi Nakada
043f010c28
parse.y: moved pipeline to expr
...
To allow arguments without parentheses.
2019-06-13 22:03:10 +09:00
Nobuyoshi Nakada
f169043d81
Add pipeline operator [Feature #15799 ]
2019-06-13 18:44:32 +09:00
Nobuyoshi Nakada
e717d6faa8
IO#set_encoding_by_bom
...
* io.c (rb_io_set_encoding_by_bom): IO#set_encoding_by_bom to set
the encoding by BOM if exists. [Bug #15210 ]
2019-06-13 18:13:05 +09:00
git
bdc8b3789a
* expand tabs.
2019-06-13 18:07:19 +09:00
Luke Gruber
02b1a85385
remove 2 redundant calls to rb_str_dup
...
Because `rb_class_path` calls `rb_str_dup` already.
Closes: https://github.com/ruby/ruby/pull/2232
2019-06-13 18:05:04 +09:00
Kazuhiro NISHIYAMA
69509df2f4
squeeze space [ci skip]
2019-06-13 16:42:31 +09:00
Martin Dürst
7f79a86d8b
add comments to mention sort.reverse!
...
For array.c (Array#sort) and enum.c (Enumerable#sort_by),
add comments mentioning that sort.reverse! / sort_by { ... }.reverse!
can/should be used to reverse the result. [ci skip]
2019-06-13 15:30:03 +09:00
Takashi Kokubun
2a26c1ea24
Clarify the Ruby version support status in IRB more
2019-06-13 00:41:00 +09:00
git
8d84e119da
* 2019-06-13
2019-06-13 00:32:59 +09:00
Takashi Kokubun
1808029061
make sync-default-gems GEM=irb
...
Upgrade IRB to 41ea43a4a7
Mostly backport changes.
2019-06-13 00:32:20 +09:00
Nobuyoshi Nakada
88411d350e
Another incomplete string case
2019-06-12 15:30:07 +09:00
Nobuyoshi Nakada
9593e76ac2
Ripper::Lexer: fallback parse error token to the previous one
2019-06-12 15:25:06 +09:00
aycabta
8354cfd03b
Treat "begin rescue end" correctly
2019-06-12 11:00:25 +09:00
Neeraj Bhunwal
c1d78a7f0e
do_mutex_lock: release mutex before checking for interrupts (fixes issue 15360)
2019-06-11 15:44:11 -07:00
Jeremy Evans
5e018214e7
Fix SystemStackError when calling a method in an unused refinement
...
Fixes [Bug #15720 ]
2019-06-11 09:43:38 -07:00
git
4f9e7c95e4
* 2019-06-12
2019-06-12 01:16:49 +09:00
git
23e3c1704b
* expand tabs.
2019-06-12 01:16:45 +09:00
Aaron Patterson
6db2d6d852
Add compaction support for more types.
...
This commit adds compaction support for:
* Fibers
* Continuations
* Autoload Constants
2019-06-11 09:16:14 -07:00
Nobuyoshi Nakada
c4cbaef216
assert_cpu_usage_low with timeout scale
...
* test/lib/test/unit/assertions.rb (assert_cpu_usage_low): apply
the timeout scale to measuring period. this assertion is very
runtime environment dependent.
2019-06-11 23:15:46 +09:00
Nobuyoshi Nakada
42f0a8fd6f
MIN_HZ and MIN_MEASURABLE constants
...
* test/lib/test/unit/assertions.rb (Test::Unit::Assertions):
promoted MIN_HZ and MIN_MEASURABLE as constants, which should be
constant through the process.
2019-06-11 23:15:46 +09:00
Nobuyoshi Nakada
eb016d8353
Generalize timeout_scale
...
* test/lib/test/unit.rb (Test::Unit::TimeoutOption): renamed
SubprocessOption.
* test/lib/test/unit.rb (Test::Unit::TimeoutOption#setup_options):
prefer `--timeout-scale` option.
* test/lib/test/unit.rb (Test::Unit::TimeoutOption#non_options):
prefer `ENV["RUBY_TEST_TIMEOUT_SCALE"]`.
2019-06-11 23:15:46 +09:00
Nobuyoshi Nakada
39ae88ad0d
Refined syntax error messages
2019-06-11 22:31:57 +09:00
Nobuyoshi Nakada
140b8117bd
&. is not allowed inside LHS of massign
...
https://hackerone.com/reports/605262
2019-06-11 15:22:16 +09:00
Kazuhiro NISHIYAMA
42ac8890ef
Fail test if load ~/.irbrc
2019-06-11 12:33:34 +09:00
Hiroshi SHIBATA
e4364dbf6e
Fixed the code-style with the upstream rule.
2019-06-11 12:16:26 +09:00
Yusuke Endoh
4adc6f07ef
test/lib/test/unit/assertions.rb (assert_cpu_usage_low): Relax the limit
...
CPU usage 1% causes occesional test failure. Try to use 5%.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/gentoo/ruby-master/log/20190604T153002Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/gentoo/ruby-master/log/20190610T153002Z.fail.html.gz
2019-06-11 07:17:59 +09:00
git
fe9701ee00
* expand tabs.
2019-06-11 06:56:46 +09:00
Yusuke Endoh
de4b2930f7
ext/socket/ipsocket.c: Use SO_REUSEADDR for local_host/port
...
Sometimes ruby/spec fails when trying to specify local_host and
local_port for TCPSocket.open.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris11s-sunc/ruby-master/log/20190610T192504Z.fail.html.gz
2019-06-11 06:53:33 +09:00
Yusuke Endoh
6096baea5d
test/net/http/test_http.rb: Extend the timeout
...
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20190610T071910Z.log.html.gz
2019-06-11 06:45:49 +09:00
git
d7e7e99862
* 2019-06-11
2019-06-11 00:25:57 +09:00
Kazuki Tsujimoto
be6b462489
Use checktype for performance
2019-06-11 00:20:10 +09:00
Takashi Kokubun
f0bfa71ab3
Use UTC for file2lastrev timezone
...
02155da7ba
got a claim about sacrificing
ability to compare arbitrary `RUBY_DESCRIPTION`s without converting
timezones.
Because most of the people would be familiar with timezone conversion
with UTC but it'd be harder when it comes to JST, this commit just
changes the timezone in f42588f754
to UTC.
Another bonus in using UTC is that we can use a shorter variant of
ISO 8601 format like "2019-06-10T14:26:24Z" (the last Z part).
2019-06-10 23:31:07 +09:00
Takashi Kokubun
02155da7ba
Make file2lastrev timezone consistent with git log
...
Using the same timezone for all commits is convenient when just looking
dates in RUBY_DESCRIPTION, but usually we also check `git log` when
we're interested in the order of commits.
`git log` shows times in committer's timezone and forcing RUBY_RELEASE_DATE
to JST makes it harder to find a corresponding commit from `git log`.
Because this label is only used in development, I believe there's no
strict requirement to use traditional timezone for release here.
Also when building Ruby after committing from a non-JST timezone, I'd be
surprised to see a strange time (in a different timezone) for my very new
commit in `ruby -v`.
2019-06-10 22:35:32 +09:00
Takashi Kokubun
caa90202c9
Make sure to suppress .irbrc on benchmark
...
By the way, this is already improved by nobu:
```
$ benchmark-driver benchmark/irb_exec.yml --rbenv '2.6.3;2.7.0-preview1;before;after' -v
2.6.3: ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]
2.7.0-preview1: ruby 2.7.0preview1 (2019-05-31 trunk c55db6aa27
) [x86_64-linux]
before: ruby 2.7.0dev (2019-06-10T21:13:14+09:00 master 973fd18f11
) [x86_64-linux]
after: ruby 2.7.0dev (2019-06-10T21:18:56+09:00 master 976c689ad4
) [x86_64-linux]
Calculating -------------------------------------
2.6.3 2.7.0-preview1 before after
irb_exec 11.868 5.872 6.297 10.278 i/s - 30.000 times in 2.527776s 5.108997s 4.764167s 2.918821s
Comparison:
irb_exec
2.6.3: 11.9 i/s
after: 10.3 i/s - 1.15x slower
before: 6.3 i/s - 1.88x slower
2.7.0-preview1: 5.9 i/s - 2.02x slower
```
2019-06-10 22:04:52 +09:00
Nobuyoshi Nakada
880204cf55
irb/cmd/help.rb: return nil after the redefinition
2019-06-10 21:45:46 +09:00
Nobuyoshi Nakada
976c689ad4
irb: defer requiring rdoc to improve the start up time
2019-06-10 21:18:56 +09:00
Takashi Kokubun
973fd18f11
Add a benchmark of irb boot time
...
```
$ benchmark-driver benchmark/irb_exec.yml --rbenv '2.6.3;2.7.0-preview1'
Calculating -------------------------------------
2.6.3 2.7.0-preview1
irb_exec 11.844 5.171 i/s - 30.000 times in 2.532887s 5.801960s
Comparison:
irb_exec
2.6.3: 11.8 i/s
2.7.0-preview1: 5.2 i/s - 2.29x slower
```
2019-06-10 21:13:14 +09:00