Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2478

Failure to run python tests on Cen6 in build-and-test.sh

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.0, 1.7.1
    • Fix Version/s: 1.8.0, 1.7.2
    • Component/s: build, python
    • Labels:
      None

      Description

      We encountered a build failure on a Cen6 machine when running build-and-test.sh. The jenkins output reported on the python failure with the following logs:

      gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/data/somelongdirectorytoavoidrpathissues/src/kudu/src -I/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/src -I/usr/include/python2.6 -c kudu/client.cpp -o build/temp.linux-x86_64-2.6/kudu/client.o
      g++ -pthread -shared build/temp.linux-x86_64-2.6/kudu/client.o -L/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/lib/exported -L/usr/lib64 -Wl,-R/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/lib/exported -lkudu_client -lpython2.6 -o /data/somelongdirectorytoavoidrpathissues/src/kudu/python/kudu/client.so
      building 'kudu.errors' extension
      gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/data/somelongdirectorytoavoidrpathissues/src/kudu/src -I/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/src -I/usr/include/python2.6 -c kudu/errors.cpp -o build/temp.linux-x86_64-2.6/kudu/errors.o
      g++ -pthread -shared build/temp.linux-x86_64-2.6/kudu/errors.o -L/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/lib/exported -L/usr/lib64 -Wl,-R/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/lib/exported -lkudu_client -lpython2.6 -o /data/somelongdirectorytoavoidrpathissues/src/kudu/python/kudu/errors.so
      building 'kudu.schema' extension
      gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/data/somelongdirectorytoavoidrpathissues/src/kudu/src -I/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/src -I/usr/include/python2.6 -c kudu/schema.cpp -o build/temp.linux-x86_64-2.6/kudu/schema.o
      g++ -pthread -shared build/temp.linux-x86_64-2.6/kudu/schema.o -L/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/lib/exported -L/usr/lib64 -Wl,-R/data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/lib/exported -lkudu_client -lpython2.6 -o /data/somelongdirectorytoavoidrpathissues/src/kudu/python/kudu/schema.so
      /data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug

      Tests failed, making sure we have XML files for all tests.
      ------------------------------------------------------------
      JUnit report missing: generating fake JUnit report file from /data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/test-logs/client_examples-test.txt.gz and saving it to /data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/test-logs/client_examples-test.xml
      JUnit report missing: generating fake JUnit report file from /data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/test-logs/client_symbol-test.txt.gz and saving it to /data/somelongdirectorytoavoidrpathissues/src/kudu/build/debug/test-logs/client_symbol-test.xml

      ======================================================================
      Failure summary
      ======================================================================
      Python tests failed

       

      Surprisingly, there wasn't anything interesting in this other than the fact that nothing interesting was reported between the python build's completion and the failure summary. Only upon looking at python_client.log did we see the errors, which appear to indicate that we might be picking up the wrong version of a pytest library. I'm not an expert in Python build stuff, so I've posted the jenkins output and the client log here.

        Attachments

        1. python_client.log
          5 kB
          Andrew Wong
        2. jenkins.txt
          4.56 MB
          Andrew Wong

          Activity

            People

            • Assignee:
              adar Adar Dembo
              Reporter:
              andrew.wong Andrew Wong
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: