-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using rspec with OCRAN executable #22
Comments
OCRAN is currently undergoing improvements for operation in Ruby 3 environments. We would greatly appreciate it if you could provide us with detailed information about any issues you are encountering while using OCRAN. Specifically, please include information about your Windows version and Ruby environment (OCRAN has been tested with Windows 10 and later, and Ruby 3.0 and later). Could you possibly clone this repository and try the latest version of OCRAN? By executing the following command, you can compile the necessary binaries such as stub.exe for OCRAN:
Using the --verbose option will log which files are being copied and the environment variables set at runtime. Currently, OCRAN does not perfectly capture all required Gems. We are aware of issues related to the capture of default GEMs, rubygems, and bundler. Please consider trying the --add-all-core and --gem-full options as well. These may help in resolving your issues. |
In my build environment, I am using appveyor with image "Visual Studio 2022", which relies currently on Windows Server 2019 and Ruby 3.2.4-1 x64. My local environment is Windows 11 with Ruby 3.3.1-x64. Using the Why should building OCRAN myself help here? Is it a different version than the published one? |
The latest version of the repository allows for detailed logging with the --verbose option, which can help identify where issues may be occurring. Additionally, you can use the --debug-extract option with the current version of OCRAN to extract files to the current directory when executing the executable. It may or may not be relevant to you, but it is known that OCRAN1.3.15 does not operate correctly under bundle exec in environments using Ruby 3.2 or later. To address this, I am actively developing improvements for OCRAN. |
@divinity666 The new version 1.3.16 is out. please try again with that one. thanks! |
Thanks for giving me the heads up! I did not manage to build OCRAN myself in the meantime, so the new release is highly appreciated! I just retried and can confirm that building the executable without Executing the executable from
Do you have any thoughts here? |
Thanks a lot for this amazing software and keeping it alive! I am using is to build the executable of my open source ruby application and ship it for windows users.
I recognized, that OCRAN somehow does not seem to capture all relevant gems, though I really don't do any fancy stuff on
require
-ing. To solve this, I started mentioning explicitrequire
s for missing parts, which then seems to work.Unfortunately, I recognized, that it's not obvious, what might be missing, so I tried to include the OCRAN built in my automated test pipeline and wanted to call it via
rspec
and simpleKernel#system
calls. And here comes the issue: I get random issues, telling me something withbundler
is not correct, though calling the executable from console works out fine.Could it be, that OCRAN mixes something up, when being called from
rspec
?The text was updated successfully, but these errors were encountered: