With your crashpad PR merged, you can also bump the submodule ;-)

@Swatinem, updated the PR with your feedback.

@Swatinem before we merge this in, could you please check if the HTTP implementation in Crashpad works now? The last time I checked, Crashpad was not able to make HTTPS requests and generally had troubles with getting requests out.

Adding at least a smoketest for crashpad here: #310
Although that runs on http right now, without TLS.

Thanks Arpad, I updated the tests script.

Looks like CI broke after enabling Crashpad tests on Linux, something related to pytest:

https://dev.azure.com/sentry-builds/sentry-native/_build/results?buildId=2534&view=logs&j=ad746dd1-389b-5d3a-67ba-32f8fe0c787d&t=ac971eda-1633-5f8a-d283-de94f79a855c&l=3552

NameError: name 'pytest' is not defined

I'm gonna have to get familiar with the CI setup to understand what's going on, but if you have any ideas please let me know.

Ah, that is just my oversight.
The real error is this one:

In file included from /home/vsts/work/1/s/include/sentry.h:81:
/home/vsts/work/1/s/external/crashpad/compat/linux/signal.h:18:2: error: #include_next is a language extension [-Werror,-Wgnu-include-next]
#include_next <signal.h>
 ^
1 error generated.

I remember we had one of these already. Also I’m surprised that all the compat includes are leaking into sentry.

Crashpad integration tests have moved to #311

This was done as part of #320 now