Make sure that torrent file is deleted after sending torrent-add requ… #1443
main.yml
on: push
build-flatpak
7m 57s
build-windows-mingw
7m 40s
reuse-lint
15s
Matrix: build-deb
Matrix: build-macos / build-macos
Matrix: build-rpm
Matrix: build-windows-msvc
Annotations
70 warnings
build-deb (ubuntu:24.10)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-flatpak
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-deb (ubuntu:24.04)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
build-deb (debian:12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:40, clang)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-rpm (fedora:41, gcc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-rpm (fedora:41, clang)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-rpm (opensuse/tumbleweed:latest, gcc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
reuse-lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
windows-x86_64-msvc-build-logs
Expired
|
40.9 KB |
|
windows-x86_64-msvc-packages
Expired
|
187 MB |
|