Looks like Build#1937 passed but Build#1938 failed again. The only change
in Build#1938 was for AMBARI-9911, which didn’t change anything in
ambari-web. 

Looks like an inconsistent repro of the unit test failure, though with a
higher probability.

Latest Broken Build:
https://builds.apache.org/job/Ambari-trunk-Commit/1938/
Successful Build: https://builds.apache.org/job/Ambari-trunk-Commit/1937/


    [exec] Trace: Entering db:getLoginName function
[exec]
[exec]  ✖ 2 of 5469 tests failed:
[exec]
[exec]  1) Ambari Web Unit tests
test/controllers/main/alerts/manage_alert_notifications_controller_test
App.ManageAlertNotificationsController #formatNotificationAPIObject()
should create object with properties from inputFields values:
[exec]  TypeError: 'undefined' is not a function (evaluating
'this.getUserPref(this.displayLengthKey()).complete(function () {
[exec] self.initFilters();
[exec] })') 
(file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-we
b/public/javascripts/app.js:150703)
[exec]
[exec] 
[exec]  2) Ambari Web Unit tests
test/controllers/main/alerts/manage_alert_notifications_controller_test
App.ManageAlertNotificationsController "after each" hook:
[exec]  TypeError: 'undefined' is not a function (evaluating
'$.ajax.restore()')
[exec] at 
file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web
/public/test/javascripts/test.js:9442
[exec] at 
file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web
/node_modules/mocha/mocha.js:4039
[exec] at next 
(file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-we
b/node_modules/mocha/mocha.js:4303)
[exec] at 
file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web
/node_modules/mocha/mocha.js:4307
[exec] at timeslice
(file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-we
b/node_modules/mocha/mocha.js:5279)
[exec] 
[exec]
[exec] Upgrade in INIT state
[exec] TRACE: Entering db:getid
[exec] npm ERR! Test failed. See above for more details.
[exec] npm ERR! not ok code 0
[INFO]             



Thanks
Jayush




On 3/3/15, 4:55 PM, "Jayush Luniya" <[email protected]> wrote:

>I second that. We need to be more proactive in keeping the branch clean.
>
>Regards
>Jayush
>
>
>On 3/3/15, 2:23 PM, "Alejandro Fernandez" <[email protected]>
>wrote:
>
>>Hi all,
>>
>>The builds on apache have been failing for quite some time due to errors
>>in Ambari Web.
>>https://builds.apache.org/job/Ambari-trunk-Commit/
>>
>>That error was first seen on build 1891 on Feb 27, and keeps reappearing
>>frequently. It may or may not be related to one of the Jiras that went in
>>on that build,
>>but I believe we need a process to keep trunk passing, otherwise, more
>>Jiras pile on and it becomes increasingly difficult to triage,
>>fix/revert.
>>
>>Feel free to reply with suggestions.
>>
>>If trunk is broken, I don't believe we should hold-off entirely on all
>>commits, but whoever is committing to the same project should investigate
>>at a minimum,
>>and decide to either file a Jira, revert the most likely commits after
>>consulting with the committers, or at least announce it to the community.
>>
>>Thoughts?
>>
>>Build
>>
>>Error
>>
>>1888<https://builds.apache.org/job/Ambari-trunk-Commit/1888/console>
>>
>>
>>Failed due to different error
>>
>>1891<https://builds.apache.org/job/Ambari-trunk-Commit/1891/consoleFull>
>>
>>
>>TypeError: 'undefined' is not an object (evaluating
>>'this.getUserPref(this.displayLengthKey()).complete')
>>
>>1892<https://builds.apache.org/job/Ambari-trunk-Commit/1892/consoleFull>
>>
>>1894<https://builds.apache.org/job/Ambari-trunk-Commit/1894/consoleFull>
>>
>>1895<https://builds.apache.org/job/Ambari-trunk-Commit/1895/consoleFull>
>>
>>1898<https://builds.apache.org/job/Ambari-trunk-Commit/1898/consoleFull>
>>
>>1915<https://builds.apache.org/job/Ambari-trunk-Commit/1915/console>
>>
>>1916<https://builds.apache.org/job/Ambari-trunk-Commit/1916/console>
>>
>>1919<https://builds.apache.org/job/Ambari-trunk-Commit/1919/console>
>>
>>1920<https://builds.apache.org/job/Ambari-trunk-Commit/1920/console>
>>
>>1921<https://builds.apache.org/job/Ambari-trunk-Commit/1921/console>
>>
>>...
>>
>>
>>
>>
>>1934<https://builds.apache.org/job/Ambari-trunk-Commit/1934/consoleFull>
>>
>>
>>TypeError: 'undefined' is not a function (evaluating
>>'this.getUserPref(this.displayLengthKey()).complete(function () {
>>
>>1935<https://builds.apache.org/job/Ambari-trunk-Commit/1935/consoleFull>
>>
>>
>>Changes in build 1891
>>
>>  1.  AMBARI-9830<https://issues.apache.org/jira/browse/AMBARI-9830>.
>>400-node cluster: Alerts cause Ambar Web lag with a lot of alerts
>>(onechiporenko) 
>>(detail<https://builds.apache.org/job/Ambari-trunk-Commit/1891/changes#de
>>t
>>ail0> / 
>>gitweb<http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=44a
>>a
>>e81097e2556531d9655c7b93d00086983a56>)
>>  2.  AMBARI-9832<https://issues.apache.org/jira/browse/AMBARI-9832>
>>JournalNode kerberos configs are missing when trying to enable HA.
>>(ababiichuk) 
>>(detail<https://builds.apache.org/job/Ambari-trunk-Commit/1891/changes#de
>>t
>>ail1> / 
>>gitweb<http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=74b
>>4
>>287f9d765fb3e6ec6d4064edf7693edb2a42>)
>>
>>
>>Thanks,
>>Alejandro
>

Reply via email to