[AMBARI-7828] TestActionScheduler fails occasionally on builds.a.o stating expected:<ABORTED> but was:<PENDING>

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.7.0
• Component/s: ambari-server, test
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 17/Oct/14 10:37
• Updated: 24/Oct/14 10:40
• Resolved: 24/Oct/14 09:52

Description

For example https://builds.apache.org/job/Ambari-trunk-test-patch/77//artifact/patch-work/testrun_ambari-server.txt

This does not happen always.

Running org.apache.ambari.server.controller.AmbariManagementControllerImplTest
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.127 sec
Running org.apache.ambari.server.actionmanager.TestActionManager
Tests run: 4, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 13.445 sec
Running org.apache.ambari.server.actionmanager.TestActionScheduler
Tests run: 19, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 3.492 sec <<< FAILURE!
Running org.apache.ambari.server.actionmanager.TestActionDBAccessorImpl

...

Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.484 sec

Results :

Failed tests:   testOpFailedEventRaisedForAbortedHostRole(org.apache.ambari.server.actionmanager.TestActionScheduler): expected:<ABORTED> but was:<PENDING>

Tests run: 2076, Failures: 1, Errors: 0, Skipped: 16

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 24:05 min
[INFO] Finished at: 2014-10-02T23:54:20+00:00
[INFO] Final Memory: 20M/294M
[INFO] ------------------------------------------------------------------------

Issue Links

• is duplicated by: AMBARI-7735 Fix issues caused by unit tests relying on asynchronus ops in TestActionScheduler
• links to: review request