2 ms·
So what is the current pass rate for language and core specs? I didn’t see a number in any of those links or did I miss it? Do I have to build and run it myself
by chrisseaton 7y ago
So what is the current pass rate for language and core specs? I didn’t see a number in any of those links or did I miss it? Do I have to build and run it myself to find out?
If you can run mspec at all then that’s pretty good to be honest.
- p4lindromica 7y agoI can run MSpec to completion for language, core, and library specs. Thank you for the encouragement :D. I've implemented a runner that can skip known things that cause the spec to hang (e.g. Mutex specs since Artichoke has a single-threaded implementation of Mutex that deadlocks during the specs). $ pushd spec-runner/vendor/ruby/language $ cargo run --bin spec-runner **/*.rb Passed 1078, skipped 35, not implemented 2, failed 476 specs. $ popd; pushd spec-runner/vendor/ruby/core $ cargo run --bin spec-runner **/*.rb Passed 5412, skipped 998, not implemented 201, failed 8629 specs. $ popd; pushd spec-runner/vendor/ruby/library $ cargo run --bin spec-runner **/*.rb Passed 0, skipped 22, not implemented 16, failed 3276 specs. The library specs pass number is a bug in my spec runner. All packages added to Artichoke pass ruby/spec. Those packages are : delegate, forwardable, json, monitor, ostruct, set, srscan, and uri.
- p4lindromica 7y agoI can generate a set of pass rates during build and output it to the gh-pages branch. That's a good idea. Thank you. https://github.com/artichoke/artichoke/issues/101 https://github.com/artichoke/artichoke/issues/101