-
Notifications
You must be signed in to change notification settings - Fork 144
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
How to run derailed_benchmark's build locally (for contributing) ? #226
Comments
Clone the project:
Then in your rails app point to that path:
Then use it in your project as you would otherwise i.e That's how I do it. It might be helpful once you get that working to add some docs in the CONTRIBUTING guide. |
Sorry, I may be misunderstanding...or not stating my question clearly :). My intent was to run the actual derailed tests inside my local fork of derailed to verify changes I made, independent of projects we are using derailed with. I saw that there is a sample rails project inside derailed, but I wasn't able to figure out how to run the derailed tests against that sample rails project. For example, I made a small change to a part of Is there something I'm missing to run the derailed tests from a fresh clone, beyond |
@rsanheim hello from the future. there seems to be a bug here but you can work around it: an absolute path must be specified for BUNDLE_GEMFILE this works for me: I get a similar error as shown in your logs if i try: Even though my pwd is correct. It looks like this code in the repo is throwing it off: result = Bundler.with_original_env { `cd '#{rails_app_path}' && #{cmd} 2>&1` } but i havent dug into things enough to know how to address |
I have a tiny fix for an issue we see in our app that I'd like to contribute back, but I can't get tests to run locally. Are there docs anywhere for how to run the build locally? From the looks of the build failures, I think I'm just missing something with how the rails specific gemfiles interact with running the build.
I grabbed a snippet from #220 to try to run things in what I think is the correct way, but the full suite then errors out with environment issues since it can't find rake. I'm using ruby 3.1.2 installed via
asdf
on a M1 Macbook Pro, and this is running off latest HEAD:Full output is included below, though I have to link to the build failure in a gist as its too long.
BUNDLE_GEMFILE=gemfiles/rails_6_1.gemfile bundle install
Then trying to run the full build:
gives a bunch of output, full log is here: https://gist.github.com/rsanheim/4be23c3049a017c0acfa75f4eec17a44
Here is a snippet of the errors that get repeated:
Any help is appreciated, as this library is great and I'd be interested in helping contribute and keep things up to date with latest rails and such. Thanks @schneems!
The text was updated successfully, but these errors were encountered: