-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete projects/clickhouse directory #13129
base: master
Are you sure you want to change the base?
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
yakov-olkhovskiy is a new contributor to projects/clickhouse. The PR must be approved by known contributors before it can be merged. The past contributors are: nickitat, Felixoid, evillique, CurtizJ, nikitamikhaylov, kitaisreal, blinkov, qoega, kyprizel |
We ended up just moving the infra to our own CI because we found that to be more convenient! Don't worry, we will continue fuzzing! |
@jonathanmetzman Can you please review? 😢 |
Sure :-( Is there anything annoying or bad about OSS-Fuzz that prompted the switch? Are you going to be using ClusterFuzzLite? |
@jonathanmetzman I was listed in the list of maintainers :)
The OSS-Fuzz is not annoying, but it is just inconvinient for us to access its results + the build system is quite different which complicates supporting it. We constantly receive the emails about that the build is broken, while it is working Ok in our CI - possibly because we are switching to the new compiler way faster than the OSSFuzz. |
No description provided.