Buildbot: Fix bad state within worker repos due to ref
error causes
#115
Labels
No Label
Service
Buildbot
Service
Chat
Service
Gitea
Service
Translate
Type
Bug
Type
Config
Type
Deployment
Type
Feature
Type
Setup
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-projects-platform#115
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After commit 811c1d the repository will return an error on each "first time" run when
git fetch origin --prune
is ran:Source: https://builder.blender.org/admin/#/builders/264/builds/552
The repository has gotten into a bad state on each worker. After encountering one of these fatal errors, the repository appears to "fix" itself by pruning the bad reference. Re-triggering the Buildbot workers helps, however, since there are a multitude of tracks and a significant amount of workers, I will try to deterministically resolve this using our
invoke-workers
commands.I resolved this issue by running the following for each track on all workers: