ram/rsz: disable tests that are non-deterministic in bazel

[openroad-ci]

No description provided.

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[maliberty]

@hongted FYI

[hongted]

Note: report_buffers tests should be fixed by #8699

[hongted]

Unless addressed by another PR.

//src/rsz/test:repair_tie11_hier-tcl_test
//src/rsz/test:repair_tie12_hier-tcl_test
//src/rsz/test:resize_slack2-tcl_test

are also non-determnistic.

[maliberty]

@rovinski @braydenlouie the ram unit test gives different results in bazel than cmake so something is non-deterministic in the code. Please take a look.

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[hongted]

ram test difference is due to Bazel using libc++ by default vs libstdc++.

Can be confirmed by testing with system libstdc++ via edit to MODULE.bazel per #8610

[rovinski]

@maliberty so anything actionable for us or no?

[maliberty]

@rovinski yes, figure out why the test gives different results with bazel vs cmake and re-enable it with a fix.

[rovinski]

@hongted said above that it's due to linking different libc versions.

The new RAM test runs several other tools, including DRT, GRT, and PDN, which are all on the list in #8610. It probably follows that those are the source of the problem.

If you want we could just add a separate test which is only the ram tool? I can't see how that one would vary because there is no sorting or anything I can see that would cause different behavior.