- common.mk: set UNICODE_VERSION and UNICODE_EMOJI_VERSION to 12.0.0
- lib/unicode_normalize/tables.rb: update table data to Unicode version 12.0.0
- enc/unicode/12.0.0/casefold.h, enc/unicode/12.0.0/name2ctype.h: add generated
files for Unicode version 12.0.0
This is the main commit for #15321.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67169 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* string.c (rb_enc_str_coderange): respect the actual encoding of
if a BOM presents, and scan for the actual code range.
[ruby-core:91662] [Bug #15635]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67167 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* win32/file.c (replace_to_long_name): do not try to glob host
names and share names by FindFirstFile which is useless for that
purpose. [ruby-core:91656] [Bug #15633]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67163 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* test/ruby/test_dir.rb: r67159 closes all files explicitly
but this change breaks attempt of this test introduced at
r56467. Try another solution which removes all references
from an Array with `#clear`.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67161 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
by just randomizing test order.
The original motivation to shard --jit-wait tests was forcing to test
major parts of code without actually stopping to test MJIT after
TracePoint enablement. But it tends to increase the test time because we
often compile the same thing in different shards.
I made this decision because we seem to hit 1.5h timeout of Wercker
these days, and Wercker is really bad at handling timeout (it does not
report timeout as failure, but just keeps it "pending" state)
https://app.wercker.com/ruby/ruby/runs/mjit-test2/5c78f15cc9e725000805b86c?step=5c79031d6c1e2c0008ac41c3
By randomizing this, we could test things randomly. The downside of this
approach is that we may not be able to find a specific commit that
caused a future failure by having TracePoint in a very early phase.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67158 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This reverts commit b0e350fe16.
The issue seems to be invalid tag name including `"` in ancient tag.
We're trying to delete that.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67144 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* They are invoked on Linux and macOS environment.
* Try to build with vs2017. But it's only binary build.
https://dev.azure.com/rubylang/ruby/
[Feature #15181][ruby-core:89222]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67137 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Ruby uses the Oniguruma/Onigmo regular expression engine, including the underlying
character encoding framework. In contrast to other code implementing Ruby, the
regular expression engine related code is formatted with two spaces per indent
level. This commit adds rules for these files. (The commit may not completely cover
all related files.) [ci skip]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67132 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
the bug of memmem(3) was fixed in glibc 2.1 released in 1999.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67129 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Linux and AIX have statx() with different prototype.
Linux: int statx(int, const char*, int, unsigned int, struct statx*)
AIX: int statx(char, struct stat*, int, int)
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67128 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
nobu
naruse
duerst
kazu
hsbt
svn
k0kubun
ko1
glass