From https://open-bitbucket.nrao.edu/scm/casa/casa-data
   113ffb7..42b9b5c  master     -> origin/master
Downloading geodetic/IERSpredict/table.dat (3.3 KB)
Downloading geodetic/IERSpredict/table.f0 (230 KB)
Downloading geodetic/IERSpredict/table.lock (325 B)
fatal: could not read Username for 'https://open-bitbucket.nrao.edu': No such device or address
Error response from daemon: No such container: wheel-container-test
Error response from daemon: No such container: wheel-container-test
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 6002k  100 6002k    0     0  24.5M      0 --:--:-- --:--:-- --:--:-- 24.8M
[14359] Failed to execute script 'atlutil' due to unhandled exception!
Traceback (most recent call last):
  File "atlutil.py", line 200, in <module>
  File "atlutil.py", line 165, in has_fix_version
  File "json/__init__.py", line 354, in loads
  File "json/decoder.py", line 339, in decode
  File "json/decoder.py", line 357, in raw_decode
json.decoder.JSONDecodeError: Expecting value: line 12 column 1 (char 11)
Already on 'master'
--------------------------------------------------------------------------
prterun has exited due to process rank 0 with PID 3597 on node 2e3fbf11f30e exiting
improperly. There are three reasons this could occur:

1. this process did not call "init" before exiting, but others in the
job did. This can cause a job to hang indefinitely while it waits for
all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"

3. this process called "MPI_Abort" or "prte_abort" and the mca
parameter prte_create_session_dirs is set to false. In this case, the
run-time cannot detect that the abort call was an abnormal
termination. Hence, the only error message you will receive is this
one.

This may have caused other processes in the application to be
terminated by signals sent by prterun (as reported here).

You can avoid this message by specifying -quiet on the prterun command
line.
--------------------------------------------------------------------------