-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Optional argument "source_path" ignored by build_fuzzers #7634
Comments
Is this related to the qt project? I think it might be because of this commit: a0b3dc9 where the destination folder of the project being cloned switched from The code for Lines 507 to 528 in 5a889cf
The specific code that adds the logic to the docker command is Lines 656 to 669 in 5a889cf
In the case of One way to solve this is to place all source code in the Dockefile inside of e.g. |
The way the oss-fuzz Dockerfile is currently defined does not allow for the use of a local checkout of Qt when building the fuzzers or the test cases. In order to fix that, the first step is to update this script so it is ready for the new version of the Dockerfile but also keep it compatible with the current version so that there's no break on the fuzzing side until the new Dockerfile is merged by the oss-fuzz project. Related: google/oss-fuzz#7634 Change-Id: I98bfa4a3d83d1a3259eb4b7a33e839ededc54751 Reviewed-by: Robert Löhning <robert.loehning@qt.io>
This way the clones will follow the same structure as the Qt sources and it will possible to mount them again to test fixes. To be merged after this patch goes in: https://codereview.qt-project.org/c/qt/qtqa/+/423444 Fixes google#7634
The current Docker image as it is created does not allow the use of external sources to test fixes as the mount will come on top of all the SRC content which has more than just the Qt sources. This patch changes that and moves the clone to a dedicated folder so it will follow the same structure as the Qt sources and it will possible to mount them again to test fixes. Fixes #7634
The help text shown when calling
python infra/helper.py build_fuzzers
without further arguments reads that an optional argument "source_path" can be passed. Some months ago, this used to build sources from that path instead of those in the Dockerfile.
When I try it now, this argument seems to be ignored and the fuzzers are always being build from the Dockerfile. Am I missing something? It looks to me like either build_fuzzers has a bug or the help text is outdated.
The text was updated successfully, but these errors were encountered: