Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Jenkins JIRA by Jack Yang, 1 year ago
unexpected build status; build log was: ------ Started by user SYSTEM [EnvInject] - Loading node environment variables. Building in workspace C:\Users\JAY\AppData\Local\Temp\hudson8327239648471849149test\workspace\MultiTop Run condition [Always
via Jenkins JIRA by Jack Yang, 1 year ago
unexpected build status; build log was: ------ Started by user SYSTEM [EnvInject] - Loading node environment variables. Building in workspace C:\Users\JAY\AppData\Local\Temp\hudson8327239648471849149test\workspace\MultiTop Run condition [Always
via ZK-Tracker by hawk, 1 year ago
via ZK-Tracker by hawk, 2 years ago
via Stack Overflow by JaneGoodall
, 2 years ago
Expected: <5> but: was <3>
via ociweb.com by Unknown author, 2 years ago
So it goes Expected: (a string starting with "Started" and a string ending with "well." and a string containing "Another") but: a string containing "Another" was "Started well, did One thing, Ended well."
java.lang.AssertionError: unexpected build status; build log was:
------
Started by user SYSTEM
[EnvInject] - Loading node environment variables.
Building in workspace C:\Users\JAY\AppData\Local\Temp\hudson8327239648471849149test\workspace\MultiTop
Run condition [Always] enabling prebuild for step [BuilderChain]
Starting build job ha:AAAAix+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMhgKWHg0s/KT9J3K0pN1QcAK+uO8I8AAAA=Free.
Starting build job ha:AAAAjB+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMhgLWHg1s/KT9J3K0pNNdIHAORerQiQAAAAFree2.
Finished Build : ha:AAAAjh+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMhgKmHg1c/KT9J3K0pN1TfU1wcAuGNOIpIAAAA=#1 of Job : ha:AAAAix+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMhgKWHg0s/KT9J3K0pN1QcAK+uO8I8AAAA=Free with status : ha:AAAAkB+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMhgL2EQ0c/KT9J3K0pN1TfU14fqAQBkUe5fmQAAAA==FAILURE
Finished Build : ha:AAAAjx+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMhgKmHg08/KT9J3K0pNNdI31NcHAJUwOJOTAAAA#1 of Job : ha:AAAAjB+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMhgLWHg1s/KT9J3K0pNNdIHAORerQiQAAAAFree2 with status : ha:AAAAkR+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMhgL2EQ1c/KT9J3K0pNNdI31NeHagIAeTfXxpoAAAA=FAILURE
Build step 'MultiJob Phase' marked build as failure
Warning: ‘Access Control for Builds’ in global security configuration is empty, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE

------

Expected: is <SUCCESS>
     but: was <FAILURE>	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)	at org.junit.Assert.assertThat(Assert.java:865)	at org.jvnet.hudson.test.JenkinsRule.assertBuildStatus(JenkinsRule.java:1054)	at com.tikal.jenkins.plugins.multijob.test.ConditionalPhaseTest.testConditionalPhase(ConditionalPhaseTest.java:75)