Questions & Answers

PNDA Build not happening for RELEASE 3.4 for Ubuntu 14.04

0 votes
asked Jul 4 by smaniramkrish (170 points)
Any known issue/tricks for PNDA build for Release 3.4.

If the 3.4 value is provided as argument to the pnda build script, the build script clone the various PNDA components from github of release 3.4 whereas some github repos don't have the 3.4 tag.

Hence the build is not successful. Is that my understanding is right

1 Answer

0 votes
answered Jul 4 by trsmith2 (3,160 points)
All the repositories have a release/3.4 tag. Can you provide some more detail about your error?
commented Jul 4 by trsmith2 (3,160 points)
Good. If you do run through this again be aware that release/3.4 used an older version of the JDK. You will want to use the JAVA_MIRROR env variable or pre-install the JDK required before running the build dependency installation script. You can get it from Oracle. We will be fixing this branch to work with the current version of the JDK in due course and release 3.5 is also imminent which doesn't have this issue in the first place.
commented Jul 4 by smaniramkrish (170 points)
Yes I did fix the JAVA Error. Now I am getting this below

root@ip-172-31-46-189:/home/ubuntu/pnda/build#  ./ RELEASE release/3.4
git: OK
Cloning into 'platform-deployment-manager'...
remote: Counting objects: 376, done.
remote: Total 376 (delta 0), reused 0 (delta 0), pack-reused 376
Receiving objects: 100% (376/376), 307.84 KiB | 0 bytes/s, done.
Resolving deltas: 100% (168/168), done.
Checking connectivity... done.
Note: checking out '27cdfb864574e75ddeba9e29d9cbcd59e9a4620d'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

Apache Maven 3.0.5: OK
Code quality: 9.77
ERROR: Failure: SyntaxError (invalid token (, line 162))
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/nose/", line 39, in runTest
    raise self.exc_val.with_traceback(self.tb)
  File "/usr/local/lib/python3.4/dist-packages/nose/", line 418, in loadTestsFromName
    addr.filename, addr.module)
  File "/usr/local/lib/python3.4/dist-packages/nose/", line 47, in importFromPath
    return self.importFromDir(dir_path, fqname)
  File "/usr/local/lib/python3.4/dist-packages/nose/", line 94, in importFromDir
    mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.4/", line 235, in load_module
    return load_source(name, filename, file)
  File "/usr/lib/python3.4/", line 171, in load_source
    module = methods.load()
  File "<frozen importlib._bootstrap>", line 1220, in load
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1467, in exec_module
  File "<frozen importlib._bootstrap>", line 1572, in get_code
  File "<frozen importlib._bootstrap>", line 1532, in source_to_code
Ran 19 tests in 0.045s

FAILED (errors=9)
Build error
Please determine the reason for the error, correct and re-run
commented Jul 4 by trsmith2 (3,160 points)
It looks like you might be using AWS. Which AMI are you using to do this build?
commented Jul 4 by smaniramkrish (170 points)
I am using this ami-d732f0b7
commented Jul 4 by trsmith2 (3,160 points)
That should be fine. I've just run through these steps with the same image in eu-west-1 and it worked without error.

My guess is that because you've had multiple attempts at this and some of the earlier attempts were using different versions, you've ended up installing the wrong build prerequisites. Try starting again with a clean machine.