[Chapel Merge] Add a future test to capture set leaking behavior

Branch: refs/heads/main
Revision: 4874041
Author: bmcdonald3
Link: Add a future test to capture set leaking behavior and fix existing tests by bmcdonald3 · Pull Request #18889 · chapel-lang/chapel · GitHub
Log Message:

Merge pull request #18889 from bmcdonald3/set-leaks

Add a future test to capture set leaking behavior and fix existing tests

[ reviewed by @lydia-duncan - thanks ]

The tests added in Document that set operations will favor the LHS and add test to lock in that behavior by bmcdonald3 · Pull Request #18842 · chapel-lang/chapel · GitHub exposed an existing memory leak in set where adding the same instance of a record that has a string field twice will cause a memory leak. Those leaking tests are cleaned up here to illustrate the same behavior as before, but without having memory leaks and adds a new future test to capture that leaking behavior.

Tracking issue: https://github.com/Cray/chapel-private/issues/2871

Modified Files:
A test/library/standard/Set/leaks/doubleStringAdd.chpl

A test/library/standard/Set/leaks/doubleStringAdd.execopts
A test/library/standard/Set/leaks/doubleStringAdd.future
A test/library/standard/Set/leaks/doubleStringAdd.good
M test/library/standard/Set/setOperatorOrderTest.chpl
M test/library/standard/Set/setOperatorOrderTest.good
M test/library/standard/Set/setOperatorOrderTest2.chpl
M test/library/standard/Set/setOperatorOrderTest2.good

Compare: https://github.com/chapel-lang/chapel/compare/9b7341589b0e...487404100a19