Another trivial patch attached.
Created attachment 129427 [details] [review] test: Add some OOM paths to the test-pending-call-timeout test This is mostly pointless, but will shut Coverity up. Coverity ID: 54718 Signed-off-by: Philip Withnall <withnall@endlessm.com>
Created attachment 129428 [details] [review] test: Add some OOM paths to the shell-test I am increasingly of the opinion that this is a gigantic waste of time. But at least Coverity will be happy. Coverity IDs: 60585, 60586 Signed-off-by: Philip Withnall <withnall@endlessm.com>
Created attachment 129429 [details] [review] test: Add a missing OOM path in manual-dir-iter test Odd that this one was missing but all the other ones were in place. Coverity ID: 54721 Signed-off-by: Philip Withnall <withnall@endlessm.com>
Created attachment 129430 [details] [review] dbus-message-util: Add some missing OOM paths to an internal test Coverity ID: 54688 Signed-off-by: Philip Withnall <withnall@endlessm.com>
Created attachment 129474 [details] [review] dbus-list: Add some missing OOM paths to an internal test Coverity ID: 54715 Signed-off-by: Philip Withnall <withnall@endlessm.com>
Created attachment 129475 [details] [review] dbus-message-factory: Add some missing OOM paths to an internal test Coverity ID: 54692 Signed-off-by: Philip Withnall <withnall@endlessm.com>
Looks fine as far as here.
(In reply to Simon McVittie from comment #7) > Looks fine as far as here. That’s all of them now.
Fixed in git for 1.11.10, thanks
(In reply to Philip Withnall from comment #3) > Created attachment 129429 [details] [review] [review] > test: Add a missing OOM path in manual-dir-iter test > > Odd that this one was missing but all the other ones were in place. > > Coverity ID: 54721 > > Signed-off-by: Philip Withnall <withnall@endlessm.com> Looks like this one wasn’t pushed to master.
(In reply to Philip Withnall from comment #10) > Looks like this one wasn’t pushed to master. Really applied. Sorry about that.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.