-
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
Upgrade Ubuntu version #6180
Milestone
Comments
We'll also need to coordinate this with ClusterFuzz and FuzzBench. |
+1. We can make migration a little easier if the downstream consumers (ClusterFuzz + FuzzBench) if we upload a 16.04 tag and have those depend on that first. |
Merged
jonathanmetzman
added a commit
to google/fuzzbench
that referenced
this issue
Aug 17, 2021
This is so that we don't have to upgrade FuzzBench images when OSS-Fuzz images upgrade. This is related to google/oss-fuzz#6180
jonathanmetzman
added a commit
to google/clusterfuzz
that referenced
this issue
Aug 17, 2021
This is so that we don't have to these images when we upgrade the OSS-Fuzz images. This is related to google/oss-fuzz#6180
jonathanmetzman
added a commit
that referenced
this issue
Aug 17, 2021
jonathanmetzman
added a commit
that referenced
this issue
Aug 17, 2021
All dependencies must be built with MSAN by the project. OSS-Fuzz will not be providing any instrumented libraries. Related: #6180
jonathanmetzman
added a commit
to google/clusterfuzz
that referenced
this issue
Aug 19, 2021
This is so that we don't have to these images when we upgrade the OSS-Fuzz images. This is related to google/oss-fuzz#6180
This was referenced Aug 19, 2021
jonathanmetzman
added a commit
that referenced
this issue
Aug 20, 2021
suffix and pushing them to gcr.io/oss-fuzz-base. This is useful for testing changes to images. I used it to test changes I made for #6180. This does not support msan as that image is being removed. Also lint.
jonathanmetzman
added a commit
that referenced
this issue
Aug 20, 2021
1. Don't do any special handling for MSAN anymore. It isn't needed. 2. Don't do any special handling for msan-libs-builder it doesn't exist anymore. 3. Don't copy python anymore. python3 comes with base-runner. Related: #6180
jonathanmetzman
added a commit
that referenced
this issue
Aug 20, 2021
When we upgrade to 20.04, python wont be in base-builder and these projects will fail unless they install it. Until then, this change should be a noop. Related: #6180
jonathanmetzman
added a commit
that referenced
this issue
Aug 20, 2021
ninja-build is the intended package name. ninja-build isn't actually needed for this project anyway. ninja is not the build tool and isn't available in Ubuntu 20.04. Removing this to prevent breakage. Related: #6180
jonathanmetzman
added a commit
that referenced
this issue
Aug 20, 2021
install libdrm-dev. Don't rely on cd accepting multiple arguments. This behavior doesn't work in Ubuntu 20.04. Related: #6180
jonathanmetzman
added a commit
that referenced
this issue
Aug 26, 2021
Fix projects so they don't break with upgrade. These fixes are likely not backwards compatible and will fail on Ubuntu 16.04. Related: #6180
jonathanmetzman
added a commit
that referenced
this issue
Aug 26, 2021
jonathanmetzman
added a commit
that referenced
this issue
Aug 26, 2021
jonathanmetzman
added a commit
that referenced
this issue
Aug 26, 2021
jonathanmetzman
added a commit
that referenced
this issue
Aug 26, 2021
jonathanmetzman
added a commit
that referenced
this issue
Aug 26, 2021
Handle upgrade to Ubuntu 20.04 1. Don't do any special handling for MSAN anymore. It isn't needed. 2. Don't do any special handling for msan-libs-builder it doesn't exist anymore. Related: #6180
jonathanmetzman
added a commit
to google/fuzzbench
that referenced
this issue
Aug 26, 2021
This is so that we don't have to upgrade FuzzBench images when OSS-Fuzz images upgrade. This is related to google/oss-fuzz#6180
This was referenced Aug 26, 2021
This was referenced Aug 30, 2021
jonathanmetzman
added a commit
that referenced
this issue
Aug 31, 2021
jonathanmetzman
added a commit
that referenced
this issue
Aug 31, 2021
Functionality was already removed. This is basically dead code right now. Related: #6180
This is done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to do this eventually. I don't want to do it after ClusterFuzzLite launches because I don't want to break people so soon after releasing a project. Delaying this only makes the problem worse.
So far, I've tested a few major projects/configurations. I tested each sanitizer, each engine, each architecture, and each language. It seems like only the swift projects are breaking.
We expect some MSAN users to break also.
The text was updated successfully, but these errors were encountered: