Bigtop
  1. Bigtop
  2. BIGTOP-804

org.apache.bigtop.itest.pmanager.PackageManagerTest.testLookupGcc fails on some systems

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.6.0
    • Component/s: None
    • Labels:
      None

      Description

      I noticed from the Jenkins runs at https://builds.apache.org/job/Bigtop-trunk-iTest/
      that the job passes for the ubuntu2 slave, but not for others.

      The failure:
      https://builds.apache.org/job/Bigtop-trunk-iTest/org.apache.bigtop.itest$itest-common/583/testReport/org.apache.bigtop.itest.pmanager/PackageManagerTest/testLookupGcc/

      is

      java.lang.NullPointerException: Cannot invoke method length() on null object
      at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
      at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
      at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
      at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32)
      at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
      at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
      at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
      at org.apache.bigtop.itest.pmanager.PackageManagerTest.testLookupGcc(PackageManagerTest.groovy:45)

      which seems to be due to the fact that on some systems, the 'gcc' package lack the metadata field "description".
      Not sure why this is the case for the other ubuntu slaves on Jenkins but not on ubuntu2.

      void testLookupGcc()

      { List<PackageInstance> pkgs = pmgr.lookup("gcc"); assertFalse("gcc non found in repository", pkgs.size() == 0); assertFalse("can not get description for the gcc package", pkgs.get(0).getMeta()["description"].length() == 0); }

        Activity

        Hide
        Johnny Zhang added a comment -

        as we ping the job to ubuntu2 slave, it turns green. https://builds.apache.org/job/Bigtop-trunk-iTest/org.apache.bigtop.itest$itest-common/601/

        We will see if we need to change the code in the future to make it more flexible. We can reopen the jira then.

        Show
        Johnny Zhang added a comment - as we ping the job to ubuntu2 slave, it turns green. https://builds.apache.org/job/Bigtop-trunk-iTest/org.apache.bigtop.itest$itest-common/601/ We will see if we need to change the code in the future to make it more flexible. We can reopen the jira then.
        Hide
        Johnny Zhang added a comment -

        The job all pass before #367, and they all run on 'ubuntu2'. I think slave 'ubuntu3' is a new added slave and have gcc pkg problem. From the code, it seems it because package 'gcc' on ubuntu3 doesn't have field "description". Since cannot login to the slave, cannot verify that.

        Show
        Johnny Zhang added a comment - The job all pass before #367, and they all run on 'ubuntu2'. I think slave 'ubuntu3' is a new added slave and have gcc pkg problem. From the code, it seems it because package 'gcc' on ubuntu3 doesn't have field "description". Since cannot login to the slave, cannot verify that.

          People

          • Assignee:
            Johnny Zhang
            Reporter:
            Jolly Chen
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development