Age | Commit message (Collapse) | Author |
|
Files removed from the working tree were not being properly removed from
the branch, leading to symbol conflicts while building. This requires the
change to 'git add --all' in the tools/go_branch.sh script.
But why was this not caught by CI? The "git clean -f" command by default
only cleans files in the current working directory. In order to clean the
whole tree recursively, we need to specify a pathspec, which is ".".
In addition to these fixes, re-add the "go tests" command to help prevent
this from happening again, since merges on the Go branch will happen in
GitHub actions for simplicity. The Go test is retained in BuildKite.
PiperOrigin-RevId: 351503804
|
|
This requires several changes:
* Templates must preserve relevant tags.
* Pagetables templates are split into two targets, each preserving tags.
* The binary VDSO is similarly split into two targets, with some juggling.
* The top level tools/go_branch.sh now does a crossbuild of ARM64 as well,
and checks and merges the results of the two branches together.
Fixes #5178
PiperOrigin-RevId: 351304330
|
|
PiperOrigin-RevId: 350197814
|
|
For validation, the "on" key in existing YAML files is changed to a literal
string. In the YAML spec, on is a keyword which encodes a boolean value, so
without relying on a specific implementation the YAML files are technically
not encoding an object that complies with the specification.
PiperOrigin-RevId: 350172147
|
|
This GitHub action has been failing since 4e963c9.
PiperOrigin-RevId: 349327675
|
|
Also, drop the pull_request template, since this has not proved to be
helpful, and just results in a commit message the includes the list.
PiperOrigin-RevId: 347636507
|
|
When nogo checks are violated, they will automatically posted
as annotations on the specific GitHub commit. This allows us
to ensure analysis & style rules and have them called out.
PiperOrigin-RevId: 334447285
|
|
We can't actually push the Go branch on pushes to feature branches.
Signed-off-by: Andrei Vagin <avagin@google.com>
|
|
Signed-off-by: Andrei Vagin <avagin@google.com>
|
|
bazel creates sysmlink to the cache on the first invokation.
On a new clone, there are no symlink, thus `rm -rf bazel-bin/gopath`
has no effect. Call `bazel build something` first, then delete
cached gopath.
PiperOrigin-RevId: 327536044
|
|
PiperOrigin-RevId: 324642975
|
|
PiperOrigin-RevId: 324615016
|
|
PiperOrigin-RevId: 324302828
|
|
PiperOrigin-RevId: 324024075
|
|
Fixes #3326
PiperOrigin-RevId: 323589669
|
|
Add a conditional to avoid running the issue reviver on forks. It will
always cause errors since bug references in the source code don't match
issue IDs in forked repos.
PiperOrigin-RevId: 321042060
|
|
PiperOrigin-RevId: 315020368
|
|
PiperOrigin-RevId: 313419745
|
|
Fixes #2722
|
|
PiperOrigin-RevId: 312159017
|
|
PiperOrigin-RevId: 312155686
|
|
PiperOrigin-RevId: 311600872
|
|
Otherwise the labeller will generate an error each time.
PiperOrigin-RevId: 309505731
|
|
This is the first automated GitHub actions workflow, and it simply applies
labels to pull request in a best-effort fashion.
PiperOrigin-RevId: 308112191
|