CircleCI workflow is failing

[yardasol]

The CircleCI workflow is currently failing when building PyNE:

.
.
.
Scanning dependencies of target alphad
[ 35%] Building Fortran object src/CMakeFiles/alphad.dir/ensdf_processing/ALPHAD/alphad.f.o
/home/circleci/project/pyne/src/ensdf_processing/ALPHAD/alphad.f:941:49:

  923 |                CALL CNVU2S(hf(l),dhf(l),hfsav(ihf),LEN(hfsav(ihf)),     &
      |                                 2                
......
  941 |                         CALL CNVU2S(hf(l)-dhf(l),0.0,hfsav(ihf),        &
      |                                                 1
Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/REAL(4)).
/home/circleci/project/pyne/src/ensdf_processing/ALPHAD/alphad.f:949:49:

  923 |                CALL CNVU2S(hf(l),dhf(l),hfsav(ihf),LEN(hfsav(ihf)),     &
      |                                 2                
......
  949 |                         CALL CNVU2S(hf(l)+dhf(l),0.0,hfsav(ihf),        &
      |                                                 1
Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/REAL(4)).
/home/circleci/project/pyne/src/ensdf_processing/ALPHAD/alphad.f:960:42:

  923 |                CALL CNVU2S(hf(l),dhf(l),hfsav(ihf),LEN(hfsav(ihf)),     &
      |                                 2         
......
  960 |                         CALL CNVU2S(hf(l),0.0,hfsav(ihf),LEN(hfsav(ihf))&
      |                                          1
Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/REAL(4)).
/home/circleci/project/pyne/src/ensdf_processing/ALPHAD/alphad.f:1063:30:

  923 |                CALL CNVU2S(hf(l),dhf(l),hfsav(ihf),LEN(hfsav(ihf)),     &
      |                                 2
......
 1063 |             CALL CNVU2S(hf(l),0.0,outstr(5),10,doutst(5),0)
      |                              1
Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/REAL(4)).
make[2]: *** [src/CMakeFiles/alphad.dir/build.make:82: src/CMakeFiles/alphad.dir/ensdf_processing/ALPHAD/alphad.f.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:271: src/CMakeFiles/alphad.dir/all] Error 2
make: *** [Makefile:149: all] Error 2

--------------------

If you are having issues building pyne, please report your problem to [email protected] or look for help at http://pyne.io

--------------------
Traceback (most recent call last):
  File "/home/circleci/project/pyne/setup.py", line 481, in <module>
    main()
  File "/home/circleci/project/pyne/setup.py", line 464, in main
    main_safe(ns)
  File "/home/circleci/project/pyne/setup.py", line 456, in main_safe
    main_body(ns)
  File "/home/circleci/project/pyne/setup.py", line 438, in main_body
    rtn = subprocess.check_call(["make"] + ns.make_args, cwd=ns.build_dir)
  File "/usr/local/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['make']' returned non-zero exit status 2.

Exited with code exit status 1

CircleCI received exit code 1

Any ideas @abachma2 @munkm ?

[nsryan2]

This issue is now not passing with the install of PyNE. I'm assuming this was fixed by #143 and this has been caused by a change since then, but I'm going to reply here to preserve Amanda's documentation of the new deployment scheme.

Although some of the projects have used PyNE thoroughly, the only use of PyNE in the scripts is nucname in analysis.py and predicting_the_past_import.py. Would it make sense to use the version of nucname that's in cyclus? I've done this before when I was breaking my cyclus conda environment with PyNE, and could make the required changes to the scripts.

Excerpt at the bottom of the error.

  # PyNE Environment Settings

  export PATH="/home/circleci/.local/bin:${PATH}"
Traceback (most recent call last):
  File "/home/circleci/.local/bin/nuc_data_make", line 4, in <module>
    from pyne.dbgen.nuc_data_make import main
  File "/home/circleci/.local/lib/python3.10/site-packages/pyne/dbgen/nuc_data_make.py", line 4, in <module>
    from pyne.utils import QA_warn
  File "/home/circleci/.local/lib/python3.10/site-packages/pyne/utils.py", line 9, in <module>
    from progress.bar import Bar
ModuleNotFoundError: No module named 'progress'

Exited with code exit status 1

[abachma2]

This error should be easy to fix. progress is a python package, and it's used in the nuc_data_make part of building pyne. Install it via conda and it should all build. If you have more errors after that, you'll have to dig in more.