On Tuesday, May 14, 2024 at 9:48:32 AM UTC+9 Matthias Koeppe wrote:
On Sunday, May 12, 2024 at 6:50:05 PM UTC-7 Travis Scrimshaw wrote:
That model is not how we have worked as a community, nor do I think it is a
productive way to run a smaller developer community such as ours.
I'm not sure w
> I don't think such permissions are needed to authorise CI runs. AFAIK,
any member of "triage" can do the latter - unless this recently changed.
As a member of the triage team, I confirm that *I don't have the rights *to
manually authorize CI runs, but the CI checks run automatically when I pus
On Wednesday, May 15, 2024 at 5:36:06 AM UTC-7 David Ayotte wrote:
When you are not part of the triage team, the CI checks does not run
automatically and someone with "write" permission needs to activate them.
A correction: It is only CI checks for "first-time contributors" that
require approv
As the title says. Most PRs I see end up with this initial build failure:
Run export MAKE="make -j2 --output-sync=recurse" SAGE_NUM_THREADS=4
+ cd /sage
+ export 'MAKE=make -j2 --output-sync=recurse' SAGE_NUM_THREADS=4
+ MAKE='make -j2 --output-sync=recurse'
+ SAGE_NUM_THREADS=4
+ ./sage -t -
Also, it has sometimes happened the CI is not correctly pulling in the
changed files. This occurred specifically for a py -> pyx file change.
Best,
Travis
On Thursday, May 16, 2024 at 10:01:45 AM UTC+9 Travis Scrimshaw wrote:
> As the title says. Most PRs I see end up with this initial build fa
Yes, various parts of the CI are broken.
Fixes for the CI ready for review:
- "Makefile, .ci/write-dockerfile.sh: Update for src/pyproject.toml after
#36982" (https://github.com/sagemath/sage/pull/37926)
- "Update conda-lock files, rename macOS conda-lock files to match CI
Conda" (https://github
