Test run sometimes ends with: Received "killed" signal

We have our test runs partitioned into 4 runs. Sometimes, but not always, our 2nd partition fails with the following error:
Received “killed” signal

I’ve read that this could be an OOM problem, but when I click on the resources tab, the CPU does get pegged to 100%, but memory usage does not exceed 33%

To check to see if it is a memory-related issue can you use the next size of Resource Class and run the job again?

That does seem to have done the trick. Spot checking recent runs, this seems to have stopped happening after we bumped the resource size.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.