-
Notifications
You must be signed in to change notification settings - Fork 207
Correct running of integration tests #574
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
Correct running of integration tests #574
Conversation
aa224e5
to
ee43f63
Compare
I had to do the |
@chadlwilson We could add a placeholder issue here to switch that to JRuby once the arjdbc issue is fixed. |
Probably not necessary right now, as (for better or worse) I just committed the migrated sqlite DB so it's a no-op on future runs - rather than needing to run special lifecycle within the tests. The previous code didn't have it doing automatic migrations, and seemed to be using the |
@chadlwilson That makes me cringe a bit when I remember us checking in binary files to the JRuby subversion repository many years ago... which is a big reason why the repo is over 300MB now. It's fine for this one case and as long as there's a way to recreate it we can move forward. |
Yeah, cringe for me also. I observed that they were committed in the old Rails 4 tests here https://github.com/jruby/warbler/blob/c45992c7577fd60abbf6495ae263f202357497ba/integration/rails4_test/src/main/ruby/db/development.sqlite3 and concluded that was "the way". At now we have git partial clones and |
Hello @tillsc 👋- since you did most of the grunt work on the integration tests, I'd really appreciate your input on this follow-up to your work. I think this will help us find a way forward on #564 and all the related bundler issues, since it gives us a clear baseline with failing integration tests demonstrating the issue in a real (jetty) environment.
I'm not 100% sure at the merits of removing the |
e5173a6
to
2d2bb19
Compare
Avoid need for CI to be aware; just use the default bundler with whatever JRuby version we are running with
JRuby 9.0 isn't supported now.
ca58c52
to
a938153
Compare
Unfortunately, #567 was misleading and the integration tests were not actually running, eg this run.
This happened due to 7053471 which accidentally disabled all tests by removing the required Maven lifecycle.
In addition to enabling them, this PR then fixes them; and related issues:
9.4.14.0
/ JDK 8 which have been failing due to the change in the platform visible to bundlerBUNDLE_DEPLOYMENT
maven-jar-plugin
,maven-tools
is not compatible with v3)9.4.58.v20250814
. Others are insecure and unpatched.3.1.0
(JRuby 9.4) since earlier rubyzip upgrade broke9.3
usage anyway.CAVEAT / TODO
JRuby 9.4+
andRails 7+
#572 and other issues. With the fix in Correct Bundler 2.x Gem path on war/jar load #575 they do pass, however. (edit: now fixed)