-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Re-enable plugin and upgrade bats tests #51565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
While the tests remained in place, the execution of these tests were lost when creating the DistroTestPlugin. This commit restores executing them.
Pinging @elastic/es-core-infra (:Core/Infra/Packaging) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment regarding making this a bit less fragile. Otherwise LGTM.
We replace the System.out and System.err objects with redirects to our log file, but never ensure they are closed. This commit closes each stream just before replacing it.
Can we get this finished off and merged? It's causing a lot of build failues that need triaged. |
The oss and default bats tests were removed, but these references to them remained, causing gradle failures when trying to run packaging tests. While the upgrade and plugins bats tests should still be tested, that is being handled in #51565. This commit removes the outdated references. closes #51974
The oss and default bats tests were removed, but these references to them remained, causing gradle failures when trying to run packaging tests. While the upgrade and plugins bats tests should still be tested, that is being handled in #51565. This commit removes the outdated references. closes #51974
@pugnascotia I have been working getting these tests working all week. Unfortunately there were many things broken over the months since they were accidentally disabled. There is still one remaining failure that happens on certain versions with the upgrade tests, which I am still looking into. I pushed 37210c4 to fix #51974, which I did not realize was an issue. |
The packaging tests start elasticsearch in various ways. All of these currently expect it is started asynchronously, yet some tests expect it will fail to start and want to check the error output. This commit adds a daemonize flag to the utility methods to start elasticsearch for such cases, so that when the start method returns, all the error output should already be available since the process will have exited. relates elastic#51716
While the tests remained in place, the execution of these tests were lost when creating the DistroTestPlugin. This commit restores executing them.
While the tests remained in place, the execution of these tests were
lost when creating the DistroTestPlugin. This commit restores executing
them.