summaryrefslogtreecommitdiff
path: root/spec/mspec
AgeCommit message (Collapse)Author
2025-03-27Update to ruby/mspec@484310dAndrew Konchin
Notes: Merged: https://github.com/ruby/ruby/pull/12984
2025-01-30Update to ruby/mspec@0aabb3eAndrew Konchin
Notes: Merged: https://github.com/ruby/ruby/pull/12679
2024-12-12Launchable: Start recording test-spec results (#12302)Naoto Ono
Notes: Merged-By: ono-max <[email protected]>
2024-12-10Update to ruby/mspec@c600b8fAndrew Konchin
Notes: Merged: https://github.com/ruby/ruby/pull/12297
2024-11-27Added --env option to mspec for test-bundled-gemsHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12179
2024-11-06Update to ruby/mspec@6499325Benoit Daloze
2024-08-20Remove dependency on Tempfile::Remover in leakchecker.rbPeter Zhu
2024-07-24Get fixnum_{min,max} from RbConfig::LIMITS when availableAlan Wu
It's better than guessing based on the pointer size if the implementation provides it directly. Notes: Merged: https://github.com/ruby/ruby/pull/11130
2024-07-24Stop depending on Integer#size to return `sizeof(long)`Alan Wu
There is no guarantee that Integer#size will continue to return `sizeof(long)` for small integers. Use the `l!` specifier for Array#pack instead. It is a public interface that has a direct relationship with the `long` type. Notes: Merged: https://github.com/ruby/ruby/pull/11130
2024-07-24Add "c_long_size" guard, supplanting "wordsize" and stop using Integer#sizeAlan Wu
What a "word" is when talking about sizes is confusing because it's a highly overloaded term. Intel, Microsoft, and GDB are just a few vendors that have their own definition of what a "word" is. Specs that used the "wordsize" guard actually were mostly testing for the size of the C `long` fundamental type, so rename the guard for clarity. Also, get the size of `long` directly from RbConfig instead of guessing using Integer#size. Integer#size is not guaranteed to have anything to do with the `long` type. Notes: Merged: https://github.com/ruby/ruby/pull/11130
2024-06-14respect `--error-output stderr` on parallel modeKoichi Sasada
`MultiFormatter#print_exception` should respect `--error-output stderr`.
2024-06-12`File.umask` does not make sense on WindowsNobuyoshi Nakada
2024-06-11check `SPEC_TEMP_DIR` is world-writable or notKoichi Sasada
``` 1) Dir.mktmpdir when passed a block yields the path to the passed block ERROR ArgumentError: parent directory is world writable but not sticky: /tmp/rubytest.wlu5cs_11 /tmp/ruby/src/trunk/lib/tmpdir.rb:113:in 'Dir.mktmpdir' /tmp/ruby/src/trunk/spec/ruby/library/tmpdir/dir/mktmpdir_spec.rb:39:in 'block (2 levels) in <top (required)>' ``` This weird error comes from world-writable (and not sticky) directory of `SPEC_TEMP_DIR`. This patch checks `SPEC_TEMP_DIR` is not world-writable if exists and `File.umask` contains o+w mask.
2024-03-14Update to ruby/mspec@b8f8f4eBenoit Daloze
2024-02-26Update to ruby/mspec@36e8ed8Benoit Daloze
2024-02-15Only check constant leaks by default for `make test-spec`Benoit Daloze
* See https://github.com/ruby/ruby/pull/9548
2024-02-05Update to ruby/mspec@31f51e0Benoit Daloze
2024-01-22Disable NSS modules when using the leakcheckerKJ Tsanaktsidis
The leakchecker will report leaked file descriptors when tests do things like access `Etc.getgrgid`, for example, if NSS modules (like `sss`) handle these lookups by connecting to a daemon like `sssd` and leave the connection open. To address this, we can call glibc's `__nss_configure_lookup` to override NSS modules configured in /etc/nsswitch.conf and only use ordinary file/DNS lookups. (This is a cherry-pick of a patch applied to ruby/mspec here: https://github.com/ruby/mspec/pull/62)
2023-11-27Update to ruby/mspec@9f83eeaBenoit Daloze
2023-10-30Update to ruby/mspec@d03ad9cBenoit Daloze
2023-09-04Update to ruby/mspec@55d1a62Benoit Daloze
2023-06-26Update to ruby/mspec@3cf2d16Benoit Daloze
2023-04-25Update to ruby/mspec@1d8cf64Benoit Daloze
2023-02-27Update to ruby/mspec@dc2eb26Benoit Daloze
2023-01-05Update to ruby/mspec@fef9b81Benoit Daloze
2022-11-07Update to ruby/mspec@1e16420Benoit Daloze
2022-09-28Update to ruby/mspec@b60306dBenoit Daloze
2022-09-21Rescue File.expand_path in MSpecScript#try_load if HOME is unavailableYuta Saito
mspec tries to load ~/.mspecrc, but some platforms (e.g. WASI) doesn't have HOME concept, so `~` cannot be expanded and `File.expand_path` can fail. Notes: Merged: https://github.com/ruby/ruby/pull/5566
2022-08-29Update to ruby/mspec@37151a0Benoit Daloze
2022-07-27Update to ruby/mspec@290e36aBenoit Daloze
2022-06-26Update to ruby/mspec@78b5d86Benoit Daloze
2022-04-25Update to ruby/mspec@215497eBenoit Daloze
2022-03-17spec: skip specs where set TZ environment variable for WASIYuta Saito
WASI doesn't respect TZ env var for now Notes: Merged: https://github.com/ruby/ruby/pull/5673
2022-03-14spec: skip ruby_exe tests for wasi due to lack of subprocessYuta Saito
Notes: Merged: https://github.com/ruby/ruby/pull/5654
2022-03-03Update to ruby/mspec@bd47c2aBenoit Daloze
2022-01-28Update to ruby/mspec@49adc2fBenoit Daloze
2022-01-10Update to ruby/mspec@3ea3d32Benoit Daloze
2021-11-29Update to ruby/mspec@098b320Benoit Daloze
2021-10-20Update to ruby/mspec@08e1275Benoit Daloze
2021-09-07Update to ruby/mspec@e768949Benoit Daloze
2021-07-29Update to ruby/mspec@9542a88Benoit Daloze
2021-06-02Update to ruby/mspec@0091e8aBenoit Daloze
2021-05-17Prefer respond_to? to defined? in MSpecBenoit Daloze
2021-05-17spec/ruby/library/yaml: Test YAML.unsafe_load instead of YAML.load in 3.1Yusuke Endoh
2021-05-17Revert "Use YAML.unsafe_load instead of YAML.load."Yusuke Endoh
This reverts commit a0e97b0e2e4314a0815d09beb825e38f234778da.
2021-05-17Use YAML.unsafe_load instead of YAML.load.Hiroshi SHIBATA
This is a temporary workaround. We should rewrite the examples with permitted_classes.
2021-03-27Update to ruby/mspec@d1adf59Benoit Daloze
2020-12-27Update to ruby/mspec@a40a674Benoit Daloze
2020-12-21Fixed indefinite articles before "Integer" [ci skip]Nobuyoshi Nakada
2020-12-05Add MSpec tool to automatically wrap spec files with a guardBenoit Daloze
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-18 16:27:34 +0000