Skip to content
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

:plugins:repository-azure:qa:microsoft-azure-storage failures #44740

Closed
jkakavas opened this issue Jul 23, 2019 · 6 comments
Closed

:plugins:repository-azure:qa:microsoft-azure-storage failures #44740

jkakavas opened this issue Jul 23, 2019 · 6 comments
Assignees
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@jkakavas
Copy link
Member

Log: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.2+multijob+third-party-tests-azure-sas/12/console
Build Scans: https://gradle.com/s/qxqjd3rfra63m

Failure:

Caused by: groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method org.elasticsearch.gradle.testclusters.ElasticsearchCluster#keystore.
08:04:45 Cannot resolve which method to invoke for [class java.lang.String, null] due to overlapping prototypes between:
08:04:45 	[class java.lang.String, interface java.util.function.Supplier]
08:04:45 	[class java.lang.String, interface org.elasticsearch.gradle.FileSupplier]
08:04:45 	at org.gradle.internal.metaobject.BeanDynamicObject$MetaClassAdapter.lookupMethod(BeanDynamicObject.java:511)
08:04:45 	at org.gradle.internal.metaobject.BeanDynamicObject$MetaClassAdapter.invokeMethod(BeanDynamicObject.java:477)
08:04:45 	at org.gradle.internal.metaobject.BeanDynamicObject.tryInvokeMethod(BeanDynamicObject.java:191)
08:04:45 	at org.gradle.internal.metaobject.ConfigureDelegate.invokeMethod(ConfigureDelegate.java:56)
08:04:45 	at build_c9he317tplhsqc5g0tilqiuzk$_run_closure4.doCall(/var/lib/jenkins/workspace/elastic+elasticsearch+7.2+multijob+third-party-tests-azure-sas/plugins/repository-azure/qa/microsoft-azure-storage/build.gradle:66)
08:04:45 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08:04:45 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
08:04:45 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
08:04:45 	at org.gradle.util.ClosureBackedAction.execute(ClosureBackedAction.java:70)
08:04:45 	at org.gradle.util.ConfigureUtil.configureTarget(ConfigureUtil.java:154)
08:04:45 	at org.gradle.util.ConfigureUtil.configure(ConfigureUtil.java:105)
08:04:45 	at org.gradle.api.internal.DefaultNamedDomainObjectCollection$ContainerElementsDynamicObject.tryInvokeMethod(DefaultNamedDomainObjectCollection.java:527)
08:04:45 	at org.gradle.internal.metaobject.BeanDynamicObject$MetaClassAdapter.invokeMethod(BeanDynamicObject.java:499)
08:04:45 	at org.gradle.internal.metaobject.BeanDynamicObject.tryInvokeMethod(BeanDynamicObject.java:191)
08:04:45 	at org.gradle.internal.metaobject.CompositeDynamicObject.tryInvokeMethod(CompositeDynamicObject.java:98)
08:04:45 	at org.gradle.internal.extensibility.MixInClosurePropertiesAsMethodsDynamicObject.tryInvokeMethod(MixInClosurePropertiesAsMethodsDynamicObject.java:33)
08:04:45 	at org.gradle.internal.metaobject.AbstractDynamicObject.invokeMethod(AbstractDynamicObject.java:160)
08:04:45 	at org.gradle.api.internal.FactoryNamedDomainObjectContainer_Decorated.invokeMethod(Unknown Source)
08:04:45 	at build_c9he317tplhsqc5g0tilqiuzk.run(/var/lib/jenkins/workspace/elastic+elasticsearch+7.2+multijob+third-party-tests-azure-sas/plugins/repository-azure/qa/microsoft-azure-storage/build.gradle:63)
08:04:45 	at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:90)

Probably related to the changes in #43782 so I'm assigning @mark-vieira to take a look

@jkakavas jkakavas added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Jul 23, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@mark-vieira
Copy link
Contributor

@original-brownbear is this CI job even compatible with 7.2? It seems that job was added in conjunction with #42982 which I don't think is applicable to that branch. Perhaps we should disable that job for 7.2?

@original-brownbear
Copy link
Member

@mark-vieira right sorry for missing that ... 7.2 doesn't support SAS tokens so yea we should not run that job.

@mark-vieira
Copy link
Contributor

There doesn't seem to be an easy way to omit a job definition based on branch with JJB. Simplest thing might be to make the job a noop based on the branch. We don't seem to have the conditional build step plugin installed so perhaps just modifying the runbld-gradle-build-third-party-build-azure-sas builder to check the branch and do nothing if it's not applicable?

@original-brownbear
Copy link
Member

@mark-vieira that's fine with me if it's fine with you, we won't ever need this in 7.2 so whatever works for you works for me:)

@mark-vieira
Copy link
Contributor

This has been fixed by https://github.com/elastic/infra/pull/13260.

@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants