Skip to content
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

Temporary build workaround no longer required #11896

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jreiser
Copy link

@jreiser jreiser commented May 3, 2024

The upx project itself already applied such a change in order to make its own CI work properly. Also, a newer version of the default compilers obviated the change anyway.

The upx project itself already applied such a change in order to make its own CI work properly.  Also, a new version of the default compilers obviated the change anyway.
Copy link

google-cla bot commented May 3, 2024

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.

Copy link

github-actions bot commented May 3, 2024

jreiser is a new contributor to projects/upx. The PR must be approved by known contributors before it can be merged. The past contributors are: MykolaMykhno

@jreiser
Copy link
Author

jreiser commented May 3, 2024

I cannot tell whether my additional email address [email protected] has passed the CLA check.
I intend that to be the case, and I entered my alternate address on the CLA that I signed.
(Note that my "alternate" email address is the one that I have used for contributions to the underlying project upx. I am a project Member of upx.)

Copy link
Contributor

@maflcko maflcko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. This is no longer needed, as clang was bumped in oss-fuzz.

@jreiser
Copy link
Author

jreiser commented May 5, 2024

This pull request was approved yesterday by @maflcko but did not get applied in time for a build which failed this morning https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=66785#c16 . Why not?

[Edit] The Actions page https://github.com/google/oss-fuzz/actions/runs/8940978935/job/24563455468?pr=11896 shows 5 successes (green checkmark icons adjacent to jobs) and 6 failures (red X icons on jobs). The failures all are

+ for fuzzer in $(find $SRC -name '*_fuzzer.cpp')
++ basename -s .cpp /src/upx/fuzzers/list_packed_file_fuzzer.cpp
+ fuzz_basename=list_packed_file_fuzzer
+ cmake --build . --target list_packed_file_fuzzer -v
make: *** No rule to make target 'list_packed_file_fuzzer'.  Stop.
ERROR:__main__:Building fuzzers failed.

So this looks like inconsistent propagation of the pull request, because there were no changes elsewhere.

@maflcko
Copy link
Contributor

maflcko commented May 6, 2024

This pull request was approved yesterday by @maflcko but did not get applied in time for a build which failed this morning https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=66785#c16 . Why not?

A maintainer needs to merge it first. (I am not a maintainer here)

So this looks like inconsistent propagation of the pull request, because there were no changes elsewhere.

The failures are real. This happens because the patch is no longer applied. You can either apply the patch in the build script here (you can also use patch -p1, which is less strict than git apply), or you can apply the patch (and fuzz targets) upstream, which would be https://google.github.io/oss-fuzz/advanced-topics/ideal-integration/ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants