Skip to content

Merge branch 'release/9.0.6' #785

Merge branch 'release/9.0.6'

Merge branch 'release/9.0.6' #785

Triggered via push February 25, 2024 20:03
Status Failure
Total duration 30m 27s
Artifacts 1

tests.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Tests: spec/requests/gdrive/setup/auth_callback_spec.rb#L79
gdrive auth callback when client_error is returned from /token redirects with error Failure/Error: expect(flash[:error]).to eq("There is a problem with your Google Drive connection." \ "Please contact Gather support.") expected: "There is a problem with your Google Drive connection.Please contact Gather support." got: "There is a problem with your Google Drive connection. Please contact Gather support." (compared using ==)
Tests: spec/system/people/auth/sign_in_invitation_spec.rb#L65
sign in invitations password auth with user created awhile ago behaves like successful password set is expected to have visible css ".alert" with text "Your password has been changed successfully. You are now signed in." Failure/Error: expect(page).to have_alert("Your password has been changed successfully. You are now signed in.") expected to find visible css ".alert" with text "Your password has been changed successfully. You are now signed in." but there were no matches. Also found "x\nPlease sign in to view that page.", which matched the selector but not all filters. [Screenshot Image]: /home/runner/work/gather/gather/tmp/capybara/failures_r_spec_example_groups_sign_in_invitations_password_auth_with_user_created_awhile_ago_behaves_like_successful_password_set_is_expected_to_have_visible_css___alert__with_text__your_password_has_been_cha_586.png Shared Example Group: "successful password set" called from ./spec/system/people/auth/sign_in_invitation_spec.rb:101
Tests
Process completed with exit code 1.
Tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v3, actions/setup-node@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
screnshots Expired
761 KB