-
Notifications
You must be signed in to change notification settings - Fork 329
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
Fix System Tests in CI environment #538
Fix System Tests in CI environment #538
Conversation
2a4640e
to
d4abcd8
Compare
d4abcd8
to
bc5a9ce
Compare
1950a13
to
50e4853
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but maybe want to squash the commits.
Tested locally and it fixes the system tests. 👍
50e4853
to
c60056b
Compare
As part of reading from the `RAILS_VERSION` environment set in CI, update the `test/dummy/config/application.rb` to use that environment variable when loading defaults. Fix a test failure when `rails@7.1` by delegating `Message#to_s` to `Message#content` so that tests that broadcast messages without text continue to pass. Also remove an entry with `ruby: "head"`, since we aren't specifying `head` in the `ruby:` key.
Resolve breaking changes introduced in `@hotwired/turbo` that were later fixed in [@hotwired/turbo#4f334da][] (and further resolved in [@hotwired/turbo#7a7c6e2][]). CI is failing because those changes are not available as part of a beta release. Despite the fact that these changes wouldn't be necessary if that release were available, this resolves the broken build pipeline more immediately. [@hotwired/turbo#4f334da]: hotwired/turbo@4f334da [@hotwired/turbo#7a7c6e2]: hotwired/turbo@7a7c6e2
c60056b
to
a2adbb1
Compare
Thanks for fixing this.
Values used in 'include' do not need to be in the normal matrix. For instance, Ruby Windows has four head builds available in GitHub Actions, EDIT: I just ran CI in my fork with the 'include' ruby head line added back in, passed here. |
With the changes made in the prior commit to pass CI merged, the fact that Turbo and Turbo Rails somehow have differing references to `Turbo` and `window.Turbo`. This commit reverts the test harness change that sets `window.Turbo`, and instead assigns that value as part of the `@hotwired/turbo-rails/index` module: ```diff -import { Turbo } from "@hotwired/turbo-rails" - -window.Turbo = Turbo +import "@hotwired/turbo-rails" ```
a2adbb1
to
3011025
Compare
@jorgemanrubia are you able to review these changes? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much @seanpdoyle
Thanks. Puma's turbo-rails workflow, which uses both Puma head and turbo-rails head is now passing. |
Add
rails@7.1
to the CI Test MatrixAs part of reading from the
RAILS_VERSION
environment set in CI,update the
test/dummy/config/application.rb
to use that environmentvariable when loading defaults.
Fix a test failure when
rails@7.1
by delegatingMessage#to_s
toMessage#content
so that tests that broadcast messages without textcontinue to pass.
Also remove an entry with
ruby: "head"
, since we aren't specifyinghead
in theruby:
key.Fix System Tests in CI environment
Resolve breaking changes introduced in
@hotwired/turbo
that were laterfixed in @hotwired/turbo#4f334da (and further resolved in
@hotwired/turbo#7a7c6e2).
CI is failing because those changes are not available as part of a beta
release. Despite the fact that these changes wouldn't be necessary if
that release were available, this resolves the broken build pipeline
more immediately.
Assign
window.Turbo
in@hotwired/turbo-rails/index
With the changes made in the prior commit to pass CI merged, the fact
that Turbo and Turbo Rails somehow have differing references to
Turbo
and
window.Turbo
.This commit reverts the test harness change that sets
window.Turbo
,and instead assigns that value as part of the
@hotwired/turbo-rails/index
module: