summaryrefslogtreecommitdiffhomepage
path: root/pkg/sentry/uniqueid/context.go
diff options
context:
space:
mode:
authorAyush Ranjan <ayushranjan@google.com>2020-06-22 16:35:35 -0700
committergVisor bot <gvisor-bot@google.com>2020-06-22 16:36:52 -0700
commitc9e6978062b0e7d7f0cc87b838cd84286fcc44f4 (patch)
tree13fad7ea007cac94fe7a867f3a9643a2a545b9c2 /pkg/sentry/uniqueid/context.go
parent4573e7d863d59d59c6a4f72f396f72b0f6458cb2 (diff)
Fix the way PR build clones gVisor.
Copybara force-pushes to the PR immediately before merging which triggers a PR build. Since the PR is merged, the refspec +refs/pull/{pr_num}/merge is not available and the build fails causing all master commit CI builds to show a failure. This change remove the clone step from travis and clone manually in a way which always would succeed. We fetch +refs/pull/{pr_num}/head and cherry pick that onto the target branch. I have tested this in https://github.com/ayushr2/gvisor/pull/1 and https://github.com/ayushr2/gvisor/pull/2. PiperOrigin-RevId: 317759891
Diffstat (limited to 'pkg/sentry/uniqueid/context.go')
0 files changed, 0 insertions, 0 deletions