increase java heap memory during tests

[brahyt-sf]

There is currently a test that has been flaky during the build workflow in github. It will fail with the underlying reason being wiremock running out of heap memory:

java.lang.OutOfMemoryError: Java heap space

This test will typically pass when you re-run this specific job on its own. The current fix is to increase the macos job runner to macos-14-large and increase heap memory for the Java environment. Tests running in these jobs have yet to fail while running simultaneously.

The purpose of this specific test is to generate a large test dataset that would be returned by salesforce and to handle that payload accordingly.

[dhagberg-sf]

Seems kinda huge - must be storing a large number of requests/responses in wiremock possibly without clearing results after each test? Oh, but this sets --no-request-journal so it shouldn't be preserving requests/responses.

Anyway, it's just there to be a mock server for tests - so if this works and de-flakes some flakiness, ship it.

[brahyt-sf]

Seems kinda huge - must be storing a large number of requests/responses in wiremock possibly without clearing results after each test? Oh, but this sets --no-request-journal so it shouldn't be preserving requests/responses.

Anyway, it's just there to be a mock server for tests - so if this works and de-flakes some flakiness, ship it.

@dhagberg-sf
There is a specific test in the bulk actions thats generating a huge payload here

heroku-applink-nodejs/test/sdk/bulk-api.test.ts

Line 1057 in 0df8981

function createLargeDataset(bulkApi: BulkApi) {

this is the one thats causing the failure, but it appears to be generating data thats similar to how SF can send those resources, so I figured that volume is important to test.

[dhagberg-sf]

Yah, that would do it. 🚢 .