You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
I'm trying to run a ClusterFuzz bot in a local instance but encountering an error. I made a few changes to the files to adapt the setup to my environment.
I started the server using the command: python3.11 butler.py run_server --name test --server-storage-path ~/clusterfuzz/test/
Then I loaded my job (openssl heartbleed example). I verified that the binary and the zip archive are set up correctly.
And after that, I ran the bot: python3.11 butler.py run_bot --name test --server-storage-path ~/clusterfuzz/test/ ~/clusterfuzz/test/bot_dir/
The bot fails to run correctly and throws the following error:
run_bot - ERROR - Error occurred while working on task.
Traceback (most recent call last):
...
AttributeError: 'NoneType' object has no attribute 'fully_qualified_name'
It seems that the FuzzTarget object is not being initialized correctly, resulting in this error. The job and the files appear to be set up properly, but the bot is unable to proceed.
Editing env.yaml in the bot directory did not help me: the same error is occurs.
The text was updated successfully, but these errors were encountered:
Hello!
I'm trying to run a ClusterFuzz bot in a local instance but encountering an error. I made a few changes to the files to adapt the setup to my environment.
I modified the following files:
I started the server using the command:
python3.11 butler.py run_server --name test --server-storage-path ~/clusterfuzz/test/
Then I loaded my job (openssl heartbleed example). I verified that the binary and the zip archive are set up correctly.
And after that, I ran the bot:
python3.11 butler.py run_bot --name test --server-storage-path ~/clusterfuzz/test/ ~/clusterfuzz/test/bot_dir/
The bot fails to run correctly and throws the following error:
It seems that the FuzzTarget object is not being initialized correctly, resulting in this error. The job and the files appear to be set up properly, but the bot is unable to proceed.
Editing env.yaml in the bot directory did not help me: the same error is occurs.
The text was updated successfully, but these errors were encountered: