Unable to run donate-cpu
Static source code analysis tool for C and C++ code
Brought to you by:
danielmarjamaki
Menu
▾
▴
When I run donate-cpu, I receive the following errors:
The entire output of the command
python /cppcheck-2.1/tools/donate-cpu.py -j2can be found at https://pastebin.com/R1F7WXjxthanks!
sorry but that script is a bit old. I made some changes on june 15th, two days after the cppcheck-2.1.
Thanks. I now pull from Github main before running donate-cpu and it's working better. There are however two issues though:
[1] Timeout when processing gcc-riscv64-unknown-elf_8.3.0.
[2] Upload failures when size exceeds 1.5MB. Server side/ web server limit? All of these appear when "Uploading information output" is attempted.
Last edit: Anand Bhat 2020-07-20
Command to replicate upload failure:
python donate-cpu.py --package=ftp://ftp.de.debian.org/debian/pool/main/g/glide/glide_2002.04.10ds1.orig.tar.gzIt's an intentional limitation with 1MB. We could abort more nicely.
Ok. If this is deliberate, an early exit from upload_info if len(info_output) > the limit may be better as it'd save the time and connection overheads of the 3 retries.
Would it also be a possibility to increase the limit? I have noticed a few packages falling into this category. That is, unless you really don't need those.
But yes, the more cores you throw at the problem, the more significant those 2 x 30s become.
Last edit: Andreas Grob 2020-07-25
it can be increased. but can we make this safer somehow. if an attacker would send random garbage to this server then it will happily store that on the disk. do you have suggestions? maybe start using some personal logins.
You could use replication, i.e. distribute one job to multiple clients and then compare the results with a suitable metric. Of course this would slow down overall progress.
The problem with logins, e.g. for elevated upload permissions, might be how to assess trustworthiness in the first place.