Skip to content
ci

fix: ensure a new lock isn't conflicting with itself #779

Sign in to view logs

fix: ensure a new lock isn't conflicting with itself

fix: ensure a new lock isn't conflicting with itself #779

Triggered via pull request February 7, 2024 10:30
@mhenrixonmhenrixon
opened #830
fix/unique-while-self-conflict
Status Failure
Total duration 42s
Artifacts –

rspec.yml

on: pull_request
coverage
20s
coverage
Matrix: rspec
Fit to window
Zoom out
Zoom in

Annotations

6 errors
rspec (2.7, sidekiq_7.0)
Process completed with exit code 1.
rspec (3.1, sidekiq_7.2)
The job was canceled because "_2_7_sidekiq_7_0" failed.
rspec (2.7, sidekiq_7.2)
The job was canceled because "_2_7_sidekiq_7_0" failed.
rspec (2.7, sidekiq_7.2)
Process completed with exit code 1.
rspec (2.7, sidekiq_7.1)
The job was canceled because "_2_7_sidekiq_7_0" failed.
rspec (2.7, sidekiq_7.1)
Process completed with exit code 1.