-
Bug
-
Resolution: Unresolved
-
Minor
-
None
There seems to be a set of problematic tests that fail on OSX at least from time to time (not always). The most common symptom is in an API test (not part of the ATH) where Jenkins returns a 403 instead of a 200:
Results : Failed tests: BranchContainerImplTest.testBranchOrdering:57 expected:<200> but was:<403> MultiBranchTest.createUserFavouriteMultibranchBranchTest:664 expected:<200> but was:<403> MultiBranchTest.createUserFavouriteMultibranchTopLevelTest:589 expected:<200> but was:<403> MultiBranchTest.parameterizedBranchTest:876 expected:<[SUCCESS]> but was:<[UNKNOWN]> PipelineNodeTest.nodesWithPartialParallels:645 expected:<3> but was:<0> Tests in error: CredentialApiTest.createSshCredentialUsingDefaultSshOnMasterInUserStore:250 » Runtime CredentialApiTest.createSshCredentialUsingDirectSshInUserStore:213 » Runtime c... CredentialApiTest.createUsingUsernamePasswordInUserStore:186 » Runtime com.mas... MultiBranchTest.favoritedFromClassicTest:739 » Runtime com.mashape.unirest.htt... PipelineNodeTest.nodesTest:695->Object.wait:502->Object.wait:-2 » Interrupted
There have also been failures around credential api.
One theory is that there is some race condition in loading of settings or classes that influence this in some environments. IN any case, this is annoying and needs to be investigated.
Raised by teilo and michaelneale
hey vivek - any ideas why unit tests will sometimes be 403? when 200 is expected? if you run the full set of unit tests locally do you see sporadic failures?