The tudat-feedstock from tudat-team

tudat-feedstock's People

Contributors

Stargazers

Watchers

tudat-feedstock's Issues

No testing done on macOS arm

As described below @DominicDirkx, testing was disabled for the azure pipelines build.

https://conda-forge.org/blog/posts/2020-10-29-macos-arm64/

SPICE(FILENAMETOOLONG) in host environment with placeholder naming

================================================================================
Toolkit version: N0066
 
SPICE(FILENAMETOOLONG) --
 
Input file name </home/ggarrett/miniconda3/conda-bld/tudat_1592845536964/_h_env
_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold
_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold
_placehold_placehold_placehold_pl/resource/spice_kernels/pck00010.tpc> has
length 291 characters. The limit on the length of file names stored by FURNSH
is 255 characters.
 
A traceback follows.  The name of the highest level module is first.
furnsh_c --> FURNSH
 
Oh, by the way:  The SPICELIB error handling actions are USER-TAILORABLE.  You
can choose whether the Toolkit aborts or continues when errors occur, which
error messages to output, and where to send the output.  Please read the ERROR
"Required Reading" file, or see the routines ERRACT, ERRDEV, and ERRPRT.
 
================================================================================

By convention, conda build has historically used its placeholder naming. It's causing tests to break when loading kernels into spice, due to the 255 character limit with furnsh_c.

Following tests failing:

    - test_aerodynamics_AerodynamicMomentAndAerodynamicForce
    - test_aerodynamics_ControlSurfaceIncrements
    - test_aerodynamics_AerodynamicCoefficientsFromFile
    - test_aerodynamics_WindModel
    - test_spice_SpiceInterface
    - test_simulation_EnvironmentModelSetup
    - test_simulation_AccelerationModelSetup

Package conflicts with windows release

Currently there are issues regarding conflicts in packages with visual studio for the windows compilation. Windows has been removed temporarily while we move to this new deployment method as there is currently no testers for the 3.0 release that are using windows. Priority for this will be bumped up if windows users, who wish to test and contribute to suggestions, make themselves known on this issue. Check the CI history for appveyor builds for the conflict errors.

Recommend Projects