Skip to content

feat(m2m-fields): allow to pass custom through M2M #1332

feat(m2m-fields): allow to pass custom through M2M

feat(m2m-fields): allow to pass custom through M2M #1332

Triggered via pull request September 28, 2023 13:56
Status Failure
Total duration 3m 9s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

test.yml

on: pull_request
Check generated files
33s
Check generated files
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 2 warnings
Check generated files
Process completed with exit code 1.
build (Python 3.11, Django 4.2)
Process completed with exit code 255.
build (Python 3.8, Django 4.1)
Process completed with exit code 255.
build (Python 3.11, Django 4.1)
Process completed with exit code 255.
build (Python 3.10, Django 4.1)
Process completed with exit code 255.
build (Python 3.9, Django 3.2)
Process completed with exit code 255.
build (Python 3.8, Django 4.2)
Process completed with exit code 255.
build (Python 3.10, Django 4.2)
Process completed with exit code 255.
build (Python 3.12-dev, Django 4.2)
Process completed with exit code 255.
build (Python 3.8, Django 3.2)
Process completed with exit code 255.
build (Python 3.10, Django 3.2)
Process completed with exit code 255.
build (Python 3.10, Django main)
Process completed with exit code 255.
build (Python 3.9, Django 4.1)
Process completed with exit code 255.
build (Python 3.11, Django main)
Process completed with exit code 255.
build (Python 3.12-dev, Django 4.1)
Process completed with exit code 255.
build (Python 3.12-dev, Django main)
Process completed with exit code 255.
build (Python 3.9, Django 4.2)
Process completed with exit code 255.
build (Python 3.9, Django 4.2)
Failed to download action 'https://api.github.com/repos/actions/checkout/tarball/8ade135a41bc03ea155e62e844d188df1ea18608'. Error: Response status code does not indicate success: 502 (Bad Gateway).
build (Python 3.9, Django 4.2)
Back off 20.221 seconds before retry.