Im running java CI github action and during the run local ip address is being changed dynamically. Don’t know is it good or bad, but those dynamic local ip addresses result in failed connection attempts in java tests. For example:
10.1.0.54, 10.1.0.36, 10.1.0.48, 10.1.0.185, 10.1.0.138 those are the local ip addresses which my java program resolve during test execution, i.e as you can see they’re different, and from the log it’s clear that they’re not connectable. Here’s link to the job.
Good news is that sometimes CI action doesn’t run into situation described above, i.e local ip address is stable and not changing dynamically, and everything works fine. In the following job you will see that local ip address is always being resolved to 10.1.0.4. Here’s the link for this successful job.