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
Release tests fail because bwc artifacts are not generated #28653
Comments
yea that was apparently only a partial fix. These should be testing against those snapshot versions, but bwc was changed to "pretend" those were releases, so it looks like i just missed a spot to unpretend. As you can see from the rpm etc generation, its not appending -SNAPSHOT to these artifacts, as it should be. So another fix on top of #28641 will be incoming to further fix this bug that it uncovered :) |
Its due to the build.snapshot being propagated into the snapshot build of the checkout. I need to chat w @rjernst to see if this is valid. I suspect it should not be passing this down since they are not releases.
|
@hub-cap The mechanism for passing the elasticsearch/distribution/bwc/build.gradle Line 142 in e0bea70
|
elasticsearch/distribution/bwc/build.gradle Line 141 in 798066a
ya and it used to be hardcoded to true @jasontedor |
Ill keep an eye on this and reopen if it continues to fail. itll be a while tho |
The release tests are failing on CI with the following error (this specific output was taken from https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+release-tests/471/console but there are other build runs failing too on master and 6.x) :
@hub-cap could these failures be related to your bwc changes in the build last week?
The text was updated successfully, but these errors were encountered: