Skip to content
Test

Switch to standardrb #48

Sign in to view logs

Switch to standardrb

Switch to standardrb #48

Triggered via pull request May 5, 2025 13:40
@mamhoffmamhoff
opened #234
mamhoff:standardrb
Status Cancelled
Total duration 2m 38s
Artifacts –

test.yml

on: pull_request
Matrix: rspec
Fit to window
Zoom out
Zoom in

Annotations

68 errors and 11 warnings
Solidus v4.4, Rails 7.1 and Ruby 3.1 on mysql
Process completed with exit code 1.
Solidus v4.3, Rails 7.1 and Ruby 3.1 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.3, Rails 7.1 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.3, Rails 7.1 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.3, Rails 7.1 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.1 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.2 and Ruby 3.1 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.1 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.2 and Ruby 3.1 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.2 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.2 and Ruby 3.1 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.2 and Ruby 3.1 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.2 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.2 and Ruby 3.1 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.2 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.2 and Ruby 3.1 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.2 and Ruby 3.1 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.2 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.2 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.2 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.2 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 8.0 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 8.0 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 8.0 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.2 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.2 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 8.0 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 8.0 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 8.0 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.1 and Ruby 3.1 on mysql
The operation was canceled.
Solidus v4.5, Rails 7.1 and Ruby 3.1 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.1 and Ruby 3.1 on sqlite
The operation was canceled.
Solidus v4.4, Rails 7.1 and Ruby 3.1 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.1 and Ruby 3.1 on postgresql
The operation was canceled.
Solidus v4.4, Rails 7.1 and Ruby 3.1 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.3, Rails 7.1 and Ruby 3.1 on postgresql
The operation was canceled.
Solidus v4.3, Rails 7.1 and Ruby 3.1 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.1 and Ruby 3.1 on postgresql
The operation was canceled.
Solidus main, Rails 7.1 and Ruby 3.1 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.1 and Ruby 3.4 on postgresql
The operation was canceled.
Solidus v4.4, Rails 7.1 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.1 and Ruby 3.4 on sqlite
The operation was canceled.
Solidus v4.4, Rails 7.1 and Ruby 3.4 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.1 and Ruby 3.4 on postgresql
The operation was canceled.
Solidus v4.5, Rails 7.1 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.1 and Ruby 3.4 on postgresql
The operation was canceled.
Solidus main, Rails 7.1 and Ruby 3.4 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.1 and Ruby 3.1 on sqlite
The operation was canceled.
Solidus v4.5, Rails 7.1 and Ruby 3.1 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.1 and Ruby 3.1 on sqlite
The operation was canceled.
Solidus main, Rails 7.1 and Ruby 3.1 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.1 and Ruby 3.1 on postgresql
The operation was canceled.
Solidus v4.5, Rails 7.1 and Ruby 3.1 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.3, Rails 7.1 and Ruby 3.1 on mysql
The operation was canceled.
Solidus v4.3, Rails 7.1 and Ruby 3.1 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.1 and Ruby 3.4 on mysql
The operation was canceled.
Solidus v4.5, Rails 7.1 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.1 and Ruby 3.4 on mysql
The operation was canceled.
Solidus v4.4, Rails 7.1 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.1 and Ruby 3.1 on mysql
The operation was canceled.
Solidus main, Rails 7.1 and Ruby 3.1 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus main, Rails 7.1 and Ruby 3.4 on mysql
The operation was canceled.
Solidus main, Rails 7.1 and Ruby 3.4 on mysql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.4, Rails 7.2 and Ruby 3.1 on sqlite
The operation was canceled.
Solidus v4.4, Rails 7.2 and Ruby 3.1 on sqlite
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Solidus v4.5, Rails 7.2 and Ruby 3.1 on postgresql
The operation was canceled.
Solidus v4.5, Rails 7.2 and Ruby 3.1 on postgresql
The strategy configuration was canceled because "rspec._7_1_3_1_v4_4_mysql" failed
Test
Canceling since a higher priority waiting request for test-234/merge exists
Solidus v4.4, Rails 7.1 and Ruby 3.1 on mysql
No files were found with the provided path: spec/dummy/tmp/capybara spec/dummy/tmp/screenshots. No artifacts will be uploaded.
Solidus v4.4, Rails 7.1 and Ruby 3.1 on mysql
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus v4.4, Rails 7.1 and Ruby 3.1 on postgresql
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus v4.4, Rails 7.1 and Ruby 3.4 on sqlite
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus v4.5, Rails 7.1 and Ruby 3.1 on sqlite
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus main, Rails 7.1 and Ruby 3.1 on sqlite
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus v4.5, Rails 7.1 and Ruby 3.1 on postgresql
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus v4.3, Rails 7.1 and Ruby 3.1 on mysql
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus v4.5, Rails 7.1 and Ruby 3.4 on mysql
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus v4.4, Rails 7.1 and Ruby 3.4 on mysql
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Solidus main, Rails 7.1 and Ruby 3.1 on mysql
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists