daml/compatibility/bazel_tools/client_server
Moritz Kiefer 9212069db4
Randomize postgres ports in compatibility tests (#5880)
While the tests are exclusive and I’ve kept them exclusive for
resource usage, the hardcoded port numbers can still cause issues if
for whatever reason you have a postgres instance running outside of
Bazel. This could happen because you simply have a local postgres
instance for testing other things or, what seems to have happened on
CI, due to a leftover postgres instance from a previous test.

While we should do something about the latter, this at least gets us
into a situation where the node isn’t completely broken at this point.

changelog_begin
changelog_end
2020-05-07 09:46:06 +02:00
..
with-postgres Randomize postgres ports in compatibility tests (#5880) 2020-05-07 09:46:06 +02:00
BUILD Add basic Sandbox data continuity tests (#5826) 2020-05-05 14:46:58 +02:00
Main.hs Fix ./fmt.sh check (#5718) 2020-04-24 12:04:14 +00:00