class jp.ikedam.jenkins.plugins.scoringloadbalancer.ScoringLoadBalancer is missing its descriptor

19 views
Skip to first unread message

Michael Kriese

unread,
May 28, 2024, 3:37:43 AMMay 28
to Jenkins Developers
Hi,

I'm trying to migrate to jenkins v2.440.3 and now getting an errors in the tests

```
[ERROR] jp.ikedam.jenkins.plugins.scoringloadbalancer.rules.NodeLoadScoringRuleJenkinsTest.testBusyScoreForTaskset -- Time elapsed: 0.739 s <<< FAILURE!
java.lang.AssertionError: class jp.ikedam.jenkins.plugins.scoringloadbalancer.ScoringLoadBalancer is missing its descriptor
        at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1666)
        at jp.ikedam.jenkins.plugins.scoringloadbalancer.rules.NodeLoadScoringRuleJenkinsTest.setScoringRule(NodeLoadScoringRuleJenkinsTest.java:71)
        at jp.ikedam.jenkins.plugins.scoringloadbalancer.rules.NodeLoadScoringRuleJenkinsTest.testBusyScoreForTaskset(NodeLoadScoringRuleJenkinsTest.java:266)
        at java.base/java.lang.reflect.Method.invoke(Method.java:580)
        at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:656)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
        at java.base/java.lang.Thread.run(Thread.java:1583)
```


strangely it only happens locally on java (OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (build 21.0.3+9-LTS, mixed mode, sharing))

Here it throws:

Any ideas?

Winter, Markus

unread,
May 28, 2024, 3:46:49 AMMay 28
to jenkin...@googlegroups.com

Ho do you run Jenkins?

I sometimes also see this error but usually after doing a clean build it disappears

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/50d3674d-4044-4715-b545-40d14a0d17d6n%40googlegroups.com.

Michael Kriese

unread,
May 28, 2024, 3:47:01 AMMay 28
to Jenkins Developers
never mind. vscode was interfering with maven cli.
Reply all
Reply to author
Forward
0 new messages