Skip to content
build

Fixed has_one bug with really_destroy! after destroy #124

Sign in to view logs

Fixed has_one bug with really_destroy! after destroy

Fixed has_one bug with really_destroy! after destroy #124

Triggered via pull request November 9, 2023 10:55
@mathieujobinmathieujobin
synchronize #428
harryhlai:fix_has_one
Status Failure
Total duration 2m 14s
Artifacts –

build.yml

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

Annotations

25 errors
test (~> 7.0.0, 3.0.6)
Process completed with exit code 1.
test (~> 6.0.0, 3.2.2)
Process completed with exit code 1.
test (~> 6.1.0, 3.1.4)
Process completed with exit code 1.
test (~> 7.0.0, 3.2.2)
Process completed with exit code 1.
test (~> 6.1.0, 3.2.2)
Process completed with exit code 1.
test (~> 6.0.0, 3.1.4)
Process completed with exit code 1.
test (3.2, ~> 7.1.0)
Process completed with exit code 1.
test (~> 6.1.0, 3.0.6)
Process completed with exit code 1.
test (~> 6.0.0, 2.7.8)
Process completed with exit code 1.
test (~> 6.0.0, 3.0.6)
Process completed with exit code 1.
test (3.2, edge)
Process completed with exit code 1.
test (~> 6.1.0, 2.7.8)
Process completed with exit code 1.
test (~> 7.0.0, 2.7.8)
Process completed with exit code 1.
test (~> 7.1.0, 3.2.2)
Process completed with exit code 1.
test (~> 7.0.0, 3.1.4)
Process completed with exit code 1.
test (~> 7.1.0, 3.1.4)
Process completed with exit code 1.
test (~> 7.1.0, 3.0.6)
Process completed with exit code 1.
test (~> 7.1.0, 2.7.8)
Process completed with exit code 1.
test (2.6, ~> 5.1.0)
Process completed with exit code 1.
test (2.5, ~> 6.0.0)
Process completed with exit code 1.
test (2.6, ~> 6.1.0)
Process completed with exit code 1.
test (2.6, ~> 5.2.0)
Process completed with exit code 1.
test (2.5, ~> 5.2.0)
Process completed with exit code 1.
test (2.5, ~> 5.1.0)
Process completed with exit code 1.
test (2.6, ~> 6.0.0)
Process completed with exit code 1.