revi-archive/llvm-premerge-checks
1
0
Fork 0
Code Activity

remove mentions of goncharov from messages

Browse source
This commit is contained in:
Mikhail Goncharov 2024-04-29 16:06:57 +02:00
parent 2d073b0307
commit 4181e4a584
3 changed files with 2 additions and 32 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
README.md
View file

@ -38,20 +38,6 @@ If you notice issues or have an idea on how to improve pre-merge checks, please
create a [new issue](https://github.com/google/llvm-premerge-checks/issues/new)
or give a :heart: to an existing one.
## Sign up for beta-test
To get the latest features and help us developing the project, sign up for the
pre-merge beta testing by adding yourself to the ["pre-merge beta testing"
project](https://reviews.llvm.org/project/members/78/) on Phabricator.
## Opt-out
In case you want to opt-out entirely of pre-merge testing, add yourself to the
[OPT OUT project](https://reviews.llvm.org/project/view/83/).
If you decide to opt-out, please let us know why, so we might be able to improve
in the future.
# Requirements
The builds are only triggered if the Revision in Phabricator is created/updated
@ -69,19 +55,6 @@ please make sure that either:
Only then can the build server apply the patch locally and run the builds and
tests.
# Accessing results on Phabricator
Phabricator will automatically trigger a build for every new patch you upload or
modify. Phabricator shows the build results at the top of the entry: ![build
status](docs/images/diff_detail.png)
The CI will compile and run tests, run clang-format and
[clang-tidy](docs/clang_tidy.md) on lines changed.
If a unit test failed, this is shown below the build status. You can also expand
the unit test to see the details: ![unit test
results](docs/images/unit_tests.png).
# Contributing
We're happy to get help on improving the infrastructure and workflows!
@ -94,9 +67,6 @@ interact together.
[Playbooks](docs/playbooks.md) shows concrete examples how to, for example,
build and run agents locally.
If you have any questions please contact by [mail](mailto:goncahrov@google.com)
or find user "goncharov" on [LLVM Discord](https://discord.gg/xS7Z362).
# Additional Information
- [Playbooks](docs/playbooks.md) for installing/upgrading agents and testing

2
containers/buildbot-linux/entrypoint.sh
View file

@ -42,7 +42,7 @@ else
unset BUILDBOT_ADDRESS
unset BUILDBOT_NAME
unset BUILDBOT_PASSWORD
echo "llvm-premerge-buildbots <llvm-premerge-buildbots@google.com>, Mikhail Goncharov<goncharov.mikhail@gmail.com>" > /build/buildbot/info/admin
echo "llvm-premerge-buildbots <llvm-premerge-buildbots@google.com>" > /build/buildbot/info/admin
echo "Setup analogous to linux agent for Pull Request checks:" > /build/buildbot/info/host
echo "GCP machine c2d-standard-56 56vCPU 224Gb" >> /build/buildbot/info/host
echo "Ubuntu 20 cmake-3.23.3 python-3.10 ninja-1.10.1 LLVM-16" >> /build/buildbot/info/host

2
containers/buildbot-windows/entrypoint.sh
View file

@ -16,7 +16,7 @@ buildbot-worker create-worker /c/ws/buildbot $BUILDBOT_ADDRESS $BUILDBOT_NAME $B
unset BUILDBOT_ADDRESS
unset BUILDBOT_NAME
unset BUILDBOT_PASSWORD
echo "llvm-premerge-buildbots <llvm-premerge-buildbots@google.com>, Mikhail Goncharov<goncharov.mikhail@gmail.com>" > /c/ws/buildbot/info/admin
echo "llvm-premerge-buildbots <llvm-premerge-buildbots@google.com>" > /c/ws/buildbot/info/admin
echo "Setup analogous to windows agent for Pull Request checks:" > /c/ws/buildbot/info/host
echo "GCP machine c2d-standard-32 AMD2 32vCPU 128Gb" >> /c/ws/buildbot/info/host
echo "Windows ltsc2019 vs-2019 LLVM-16+ python 3.9.7 cmake" >> /c/ws/buildbot/info/host