ruby.git/test/ruby/test_autoload.rb, branch v3_2_11 The Ruby Programming Language Fix autoload status of statically linked extensions 2022-11-25T21:21:40+00:00 Alan Wu XrXr@users.noreply.github.com 2022-11-17T22:33:18+00:00 790cf4b6d0475614afb127b416e87cfa39044d67 Previously, for statically-linked extensions, we used `vm->loading_table` to delay calling the init function until the extensions are required. This caused the extensions to look like they are in the middle of being loaded even before they're required. (`rb_feature_p()` returned true with a loading path output.) Combined with autoload, queries like `defined?(CONST)` and `Module#autoload?` were confused by this and returned nil incorrectly. RubyGems uses `defined?` to detect if OpenSSL is available and failed when OpenSSL was available in builds using `--with-static-linked-ext`. Use a dedicated table for the init functions instead of adding them to the loading table. This lets us remove some logic from non-EXTSTATIC builds. [Bug #19115] 
Previously, for statically-linked extensions, we used
`vm->loading_table` to delay calling the init function until the
extensions are required. This caused the extensions to look like they
are in the middle of being loaded even before they're required.
(`rb_feature_p()` returned true with a loading path output.) Combined
with autoload, queries like `defined?(CONST)` and `Module#autoload?`
were confused by this and returned nil incorrectly. RubyGems uses
`defined?` to detect if OpenSSL is available and failed when OpenSSL was
available in builds using `--with-static-linked-ext`.

Use a dedicated table for the init functions instead of adding them to
the loading table. This lets us remove some logic from non-EXTSTATIC
builds.

[Bug #19115]
Prevent a warning "Expected ... to define AutoloadTest but it didn't" 2022-06-20T08:39:58+00:00 Yusuke Endoh mame@ruby-lang.org 2022-06-20T08:39:58+00:00 078db98da42444b3cdbd0f391b680ba8193299fd related: [Bugs #18813] and eca31d24d606a73def3674938112dc3c5b79c445 
related: [Bugs #18813] and eca31d24d606a73def3674938112dc3c5b79c445
[Bug #18813] Warn when autoload has to lookup in parent namespace 2022-06-18T12:49:02+00:00 Jean Boussier jean.boussier@gmail.com 2022-06-18T08:29:52+00:00 eca31d24d606a73def3674938112dc3c5b79c445 This is a verbose mode only warning. 
This is a verbose mode only warning.
Fix Module#const_source_location for autoload constants with direct requires 2022-06-06T18:12:55+00:00 Jeremy Evans code@jeremyevans.net 2022-03-12T05:43:47+00:00 c85d1cda86d75ee2c3f7b42f22c543409cb5a186 If an autoload exists for a constant, but the path for the autoload was required, const_source_location would return [false, 0] instead of the actual file and line. This fixes it by setting the appropriate file and line in rb_const_set, and saving the file and line in const_tbl_update before they get reset by current_autoload_data. Fixes [Bug #18624] 
If an autoload exists for a constant, but the path for the autoload
was required, const_source_location would return [false, 0] instead
of the actual file and line. This fixes it by setting the appropriate
file and line in rb_const_set, and saving the file and line in
const_tbl_update before they get reset by current_autoload_data.

Fixes [Bug #18624]
Fix GC race condition in autoload. 2022-05-25T12:17:30+00:00 Samuel Williams samuel.williams@oriontransfer.co.nz 2022-05-25T11:12:54+00:00 d875445e8a8b073298e8b3db177d1a5e78c92893 






Restore implicit relationship between `autoload_const` and `autoload_data` during GC. (#5911)
2022-05-17T07:12:36+00:00

Samuel Williams
samuel.williams@oriontransfer.co.nz

2022-05-17T07:12:36+00:00

60d45b2ee86a80e248c3bff0c90c981ed2168ac3












Delete autoload data from global features after autoload has completed. (#5910)
2022-05-16T12:50:02+00:00

Samuel Williams
samuel.williams@oriontransfer.co.nz

2022-05-16T12:50:02+00:00

f626998c4fa62973cac3a027597f97cdacd0d3c5

* Update naming of critical section assertions macros.

* Improved locking for autoload.




* Update naming of critical section assertions macros.

* Improved locking for autoload.






Remove autoload for constant if the autoload fails
2021-10-08T21:54:26+00:00

Jeremy Evans
code@jeremyevans.net

2021-10-08T21:54:26+00:00

08759edea8fb75d46c3e75217e6613465426a0d2

Previously, if an autoload failed (the file was loaded, but the
constant was not defined by the autoloaded file). Ruby will try
to autoload again if you delete the autoloaded file from
$LOADED_FEATURES.  With this change, the autoload and the
constant itself are removed as soon as it fails.

To handle cases where multiple threads are autoloading, when
deleting an autoload, handle the case where another thread
already deleted it.

Fixes [Bug #15790]




Previously, if an autoload failed (the file was loaded, but the
constant was not defined by the autoloaded file). Ruby will try
to autoload again if you delete the autoloaded file from
$LOADED_FEATURES.  With this change, the autoload and the
constant itself are removed as soon as it fails.

To handle cases where multiple threads are autoloading, when
deleting an autoload, handle the case where another thread
already deleted it.

Fixes [Bug #15790]






fix for multi-run test.
2020-05-15T05:54:03+00:00

Koichi Sasada
ko1@atdot.net

2020-05-15T05:27:06+00:00

e89b87508160868bd431218872d0d5b7b15bc57b

TestAutoload#test_source_location can't run multiple test-run so
that use assert_separately().

repro command:
make yes-test-all TESTS='--repeat-count=50 ruby/test_autoload -n test_source_location'





TestAutoload#test_source_location can't run multiple test-run so
that use assert_separately().

repro command:
make yes-test-all TESTS='--repeat-count=50 ruby/test_autoload -n test_source_location'







Suffixed memory leak tests as "memory_leak"
2020-05-06T17:53:39+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2020-05-06T17:53:39+00:00

ce00fda9254887388b15a3a9ff505d3473cecf57

So that `TEST_EXCLUDES` option in common.mk works.





So that `TEST_EXCLUDES` option in common.mk works.