tests: test_from_container_spawned_process flaky failure - app starts "too late"

[Jongy]

See test failure of test_from_container_spawned_process[False-ruby-rbspy] here.

It seems that SpawningProcessProfilerBase didn't catch the new Ruby process. Maybe it started too late (although, the entire idea in this state is to catch Ruby processes starting late...). In any case, we see the Ruby in the perf native profile.

Test needs to assert that the Ruby profiler worked (check logs as well) and maybe wait more for app start?

[Jongy]

Also note, as stated in #514 , this leads to the Ruby process leaking the test (not being killed afterwards)

[Jongy]

https://github.com/Granulate/gprofiler/actions/runs/3197725234/jobs/5221613319 again

[Jongy]

I think #535 was enough to avoid this problem. Closing this ticket.