diff options
| author |  Axel Huebl <axel.huebl@plasma.ninja>
| 2021-02-18 20:15:52 -0800 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2021-02-18 20:15:52 -0800 |
| commit | 03650f39bbef3da49f2a4623da93d0b6b6ce11b7 (patch) | |
| tree | 0a12f15924fbc203e41bfa1dcbfd2f1cb660eb5b /Source/Diagnostics/FlushFormats/FlushFormatPlotfile.cpp | |
| parent | 04c5a487106127d5f4a24a5c6f6c1c5bc8153c3c (diff) | |
| download | WarpX-03650f39bbef3da49f2a4623da93d0b6b6ce11b7.tar.gz WarpX-03650f39bbef3da49f2a4623da93d0b6b6ce11b7.tar.zst WarpX-03650f39bbef3da49f2a4623da93d0b6b6ce11b7.zip | |
Tool: update AMReX dependency (#1710)
* Tool: update AMReX dependency
We currently pull the `development` branch of AMReX in CMake builds.
This is problematic in central workflows:
- checking out a release might not compile
- manual intervention is needed by users
- builds are not as reproducibile as they could be
- CI fails in a surprising wary in WarpX if a temporary bug is lands
in AMReX' `development`
Instead, we can bump the AMReX requirement periodically in a PR.
This migh be the case when we:
- need new features or bug fixes
- do a release
Manual updates guarantee that we see problems with updates from
AMReX in the moment they are introduced - during a PR that changes
the dependency to AMReX.
* Tool: update PICSAR dependency
See AMReX' updater description.
* Docs: Dependencies & Releases
Update and add workflows.
* PICSAR & AMReX: Bump Version to HEAD
Bump the PICSAR and AMReX versions to the latest head.
Executed with:
```
./Tools/Release/updateAMReX.py
./Tools/Release/updatePICSAR.py
```
* Python Tools: Cleanup
* Fix typos
Co-authored-by: Luca Fedeli <luca.fedeli@for.unipi.it>
Co-authored-by: Luca Fedeli <luca.fedeli@for.unipi.it>
Diffstat (limited to 'Source/Diagnostics/FlushFormats/FlushFormatPlotfile.cpp')
0 files changed, 0 insertions, 0 deletions