remove pixelfed from CI until fixed (#472)
All checks were successful
deploy-infra / deploy (push) Successful in 2m9s
/ check-pre-commit (push) Successful in 12s
/ check-data-model (push) Successful in 30s
/ check-mastodon (push) Successful in 21s
/ check-peertube (push) Successful in 21s
/ check-panel (push) Successful in 1m32s
/ check-deployment-basic (push) Successful in 33s
/ check-deployment-cli (push) Successful in 41s
/ check-deployment-panel (push) Successful in 1m47s
All checks were successful
deploy-infra / deploy (push) Successful in 2m9s
/ check-pre-commit (push) Successful in 12s
/ check-data-model (push) Successful in 30s
/ check-mastodon (push) Successful in 21s
/ check-peertube (push) Successful in 21s
/ check-panel (push) Successful in 1m32s
/ check-deployment-basic (push) Successful in 33s
/ check-deployment-cli (push) Successful in 41s
/ check-deployment-panel (push) Successful in 1m47s
this test is still borked as per #33. the intent would be to get this test on a feature branch pertaining to that issue - the point being we should be able to rely on CI's boolean result for detecting (newly induced) regressions. Reviewed-on: #472 Co-authored-by: Kiara Grouwstra <kiara@procolix.eu> Co-committed-by: Kiara Grouwstra <kiara@procolix.eu>
This commit is contained in:
parent
67f50f08de
commit
8253288f8a
1 changed files with 0 additions and 6 deletions
|
@ -27,12 +27,6 @@ jobs:
|
|||
- uses: actions/checkout@v4
|
||||
- run: nix build .#checks.x86_64-linux.test-mastodon-service -L
|
||||
|
||||
check-pixelfed:
|
||||
runs-on: native
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- run: nix build .#checks.x86_64-linux.test-pixelfed-garage-service -L
|
||||
|
||||
check-peertube:
|
||||
runs-on: native
|
||||
steps:
|
||||
|
|
Loading…
Add table
Reference in a new issue