You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pip is not giving us more ease-of-installation than it is costing, and pip 10 broke our builds. We are already wrapping CMake with setuptools, so maintaining pip / setup.py as the primary install method is neither sensible nor worthwhile. We may still want a thinner setup.py wrapper for readthedocs builds or something, but we should not use it for dependency resolution, compiler selection, etc. All that is really required is to use the setuptools Python package in a CMake script to locate the preferred installation directory for a given python environment.
The text was updated successfully, but these errors were encountered:
Refactoring of SYCL compiler flags in dea311a (!2841) caused
the `-fsycl-device-code-split=per_kernel` flag to be only used during
the compilation, not linking. As a result, the flag did not have any effect,
and all the kernels were JITed every time, significantly increasing
the initialization time.
Today's nightly: https://gitlab.com/gromacs/gromacs/-/jobs/2817361699
```
1/84 Test #1: GmxapiExternalInterfaceTests .............. Passed 23.85 sec
26/84 Test #26: EwaldUnitTests ............................***Timeout 30.06 sec
64/84 Test #64: MdrunTestsOneRank ......................... Passed 77.39 sec
```
After this MR: https://gitlab.com/gromacs/gromacs/-/jobs/2819696665
```
1/84 Test #1: GmxapiExternalInterfaceTests .............. Passed 2.81 sec
26/84 Test #26: EwaldUnitTests ............................ Passed 6.86 sec
64/84 Test #64: MdrunTestsOneRank ......................... Passed 2.23 sec
```
Fixes #4551
Closes #4551
Pip is not giving us more ease-of-installation than it is costing, and pip 10 broke our builds. We are already wrapping CMake with setuptools, so maintaining pip / setup.py as the primary install method is neither sensible nor worthwhile. We may still want a thinner setup.py wrapper for readthedocs builds or something, but we should not use it for dependency resolution, compiler selection, etc. All that is really required is to use the setuptools Python package in a CMake script to locate the preferred installation directory for a given python environment.
The text was updated successfully, but these errors were encountered: