Edoardo Zoni

@lucafedeli88 > I think that having a vote in the Technical Committee is the best strategy. Sure, discussions about formatting style are usually not the most exciting ones, but I...

@JustinRayAngus If you click on the three dots `...` next to the failing check in the summary of CI checks at the bottom of the PR page, it brings you...

@JustinRayAngus Do the backtraces in the "Logs" step (after "Test") of the CI pipeline tell us anything about where the erroneous arithmetic operation is occurring? I think we compile with...

@JustinRayAngus Also note that this is not specific to your PR, see, e.g., https://dev.azure.com/BLAST-WarpX/WarpX/_build/results?buildId=1212&view=results.

From our CDash dashboard, it seems like it started failing occasionally sometime towards the end of July:

Hi @rl3418, would it be possible to attach here the full input file you are using, so we can have a full picture of all parameters and try to reproduce?

Thanks for the input file, @rl3418. Looking at the one shared in https://github.com/BLAST-WarpX/warpx/issues/5915#issuecomment-2944028021, I noticed a couple of things first: - `warpx.do_dive_cleaning` is set twice, first to `1` and then...

I got an email notification that auto-merge was enabled here, so I just want to mention that I think the signature of the function `add_warpx_test` to add CI tests in...

Based on the fact that it seems like you have scanned over the number of guard cells quite thoroughly with no evident improvements, this makes me think of a number...

Thank you, @grobertdautun! We just merged in `development` a big updated of the physical constants as well as an update of the Ubuntu version used in our CI Azure pipelines,...