1
0
Fork 0
Commit graph

21 commits

Author SHA1 Message Date
Mikhail Goncharov
edd0c10f10 call vscmd during the script execution 2022-12-09 11:02:30 +01:00
Arthur Eubanks
33b26e751e Use --config=ci on bazel premerge bots
This fixes the broken premerge bots.

--config=ci implicitly implies all of the removed flags via .bazelrc, except --config=rbe which was removed.
2022-08-31 23:27:05 +02:00
Mikhail Goncharov
1b58075c54 install MLIR python requirements before building 2022-08-23 15:10:05 +02:00
Geoffrey Martin-Noble
fbffc10faf [Bazel] Explicitly build with -Werror
In https://reviews.llvm.org/D123481 we're removing this from the
default builds, but we still want it in CI builds where we know the
platform and compiler configuration.
2022-05-13 10:33:26 +02:00
Mikhail Goncharov
b69eb6f364 don't check clang-tidy
it seems quite unreliable
2021-10-04 16:44:40 +02:00
Mikhail Goncharov
3329564f50 Run bazel build on mainline 2021-09-03 15:54:53 +02:00
Mikhail Goncharov
49be688a27 script to sync fork llvm-premerge-tests/llvm-project
- uniformly append env variables

- resolve current HEAD and pass it as BUILDKITE_COMMIT to script
generators. Add it as ph_commit_sha.
2021-08-11 16:25:29 +02:00
Geoffrey Martin-Noble
8bc6bb7d5d Switch Bazel premerge checks to use llvm-bazel-premerge queue
I created a new queue for the pre-merge checks so that they won't compete for resources
with the post-merge build already running. Obviously that creates some inefficiency, but is
a simple way to make sure neither build gets starved (in particular, we know that the
current setup of 4 agents running on a single 32-core VM is enough to handle the commit
traffic on the main branch whereas pre-merge testing volume is likely to be more
unpredictable.
2021-07-29 17:57:11 +02:00
Mikhail Goncharov
6c2410440e Run bazel builds in premerge
if user is a member of "bazel_build" https://reviews.llvm.org/project/view/107/
or modified /utils/bazel/*

For #328
2021-07-28 16:01:44 +02:00
Mikhail Goncharov
8960ff7dc9 Pre-checkout for windows
Kill all running processes in BUILDKITE_BUILD_PATH and force unlock git
folder.
2021-06-01 15:26:23 +02:00
Mikhail Goncharov
f0d1cc6ab3 update linux node pool (machines w/ no external ssd)
updated llvm version to 12 with relevant fixes in scrips
2021-05-17 10:06:54 +02:00
Mikhail Goncharov
08bb6492fa service queue 2021-04-26 19:56:20 +00:00
Mikhail Goncharov
58e13f22d1 inrease timeout for win, minor doc 2021-04-23 12:28:01 +02:00
Mikhail Goncharov
99e43a8d9a rename master to main branch following LLVM 2020-12-10 09:29:24 +01:00
Mikhail Goncharov
12c4c43bb0 fix x86 debian step 2020-11-26 18:32:27 +01:00
Mikhail Goncharov
681fbbe2cf Process results and unit-test output of libcxx
Now "report" step combines result in a uniform way and processes unit test
results XML output. It works for sub-builds only started from the 'premerge'
pipeline, i.e. non-recursive. One downside is that now one has to wait until
all jobs have finished.

- Add instructions to setup python environment

- added option to do full report cycle but not call Phabricator

- use "annotations" to show build status. That lifts the need to filter ninja
  and other output (thus `ph_no_filter_output` param removed) and output
  everything. That is nice as script failures no longer lead to loss of logs.

- improved annotate() usability

- misc fixes
2020-11-25 15:29:50 +01:00
Mikhail Goncharov
43fae020f5 retry most of the requests with backoff
fixes #192

additionally:

- install python libs after scripts checkout, so we don't need to
rebuild images and restart agents only to add a new python dependency

- updated lib versions

- similar scripts checkout in steps
2020-10-12 17:08:34 +02:00
Mikhail Goncharov
322cfbda8c Add link to the build in "setup" step 2020-10-09 12:51:32 +02:00
Mikhail Goncharov
3925a2a844 get libcxx steps from sh output 2020-10-09 11:06:36 +02:00
Mikhail Goncharov
ea943424f3 Enable windows builds back
Now we run a pre-commit hook that tries to kill any process that locked
a file in target directory.

Updated timeout interval on windows from 120 to 90 minutes.

Fixes #243
2020-10-07 16:59:37 +02:00
Mikhail Goncharov
c350101a23 Allow projects to define custom steps
Now it's possible to allow sub-projects to define own checks and skip
"generic" ones.

To properly accomodate affected projects that might not have special
treatment we:

1. extend the set of affected projecs with dependent (e.g. add 'libc' if
'clang' was modified)

2. add custom steps for projects that define own workflow. At the moment
it's only libcxx and it has a custom trigger pipeline so it's noop.

3. add dependent projects and run generic check on them.

To illustrate: imagine that we have a dependency graph:

llvm -> clang -> openmp

and only clang was modified in a diff; also clang defines own checks.
Thus list of affected projects will be [clang, openmp].
After adding custom checks and removing their projecst: [openmp].
After adding dependencies: [llvm, clang, openmp]. Generic linux /
windows checks will be run on thouse 3 projects.
So as you can see in some scenarios projects with custom checks will
still go through generic checks.

Note that clang-format and clang-tidy checks are run only for "generic"
checks at the moment.
2020-10-02 16:19:57 +02:00