diff options
| author | Ayush Ranjan <ayushranjan@google.com> | 2020-10-28 19:52:32 -0700 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2020-10-28 19:54:15 -0700 |
| commit | 37b57ecd0469d225ca5997558a8a47968bc83eec (patch) | |
| tree | 5609a741cee4a4b48ecbde42483b377f1b7cf265 /pkg/sentry/arch/signal_arm64.go | |
| parent | 265f1eb2c7abbbf924448ef6bbd8cddb13e66b9f (diff) | |
[infra] Deflake Go / generate (pull_request) GitHub action.
As you can see https://github.com/google/gvisor/commits/master, there are a lot
of red commits. This is because the Go / generate GitHub action flakes.
On merge, two variants of this workflow run:
- one triggered by the pull request (copybara force pushes to the PR right
before merge)
- one triggered by the push (merge)
If the push action ends up finishing before the pull request action can run
go_branch.sh, then the changes that go_branch.sh makes is already pushed to
the remote go branch. Consequently, the pull request action ends up having
nothing to commit causing this action to fail.
This change also fixes lint warnings.
Now we skip running the go_branch.sh if we find that our current working commit
has already been committed to remote.
PiperOrigin-RevId: 339586760
Diffstat (limited to 'pkg/sentry/arch/signal_arm64.go')
0 files changed, 0 insertions, 0 deletions