During the upgrade tests the seeding phase of the test uses a randomised container name which is then used as hostname for the instance config. Subsequently when we upgrade the instance, we reuse the config, but spin up a new container which has a new name. This causes the instance config to differ from actual hostname. While today we don't observe any failures in our suite, this is solely due to the minimal set of tests we are actively using in the suite. When we try to run tests such as those that e.g. interact with WebIDE we observe failures due to the hostname not matching the config. In order to best replicate a realistic upgrade scenario we should keep the container name consistent between runs. Changelog: changed
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4