basedpl 0.1.75__tar.gz → 0.1.78__tar.gz

{basedpl-0.1.75 → basedpl-0.1.78}/.github/workflows/ci.yml

@@ -18,7 +18,7 @@ jobs:
     runs-on: ${{ matrix.os }}
     env:
       # The Python-free `bpl` goes in the wheel, through `cargo stage`, and in the GitHub release.
-      STAGE_BPL: cargo stage --profile dist && mkdir -p bin && cp wheel/scripts/bpl bin/${{ matrix.binary }}
+      STAGE_BPL: cargo stage --profile dist --no-default-features && mkdir -p bin && cp wheel/scripts/bpl bin/${{ matrix.binary }}
     steps:
       - uses: actions/checkout@v7
       - uses: dtolnay/rust-toolchain@stable
@@ -27,17 +27,15 @@ jobs:
         with:
           python-version: '3.12'
       - if: runner.os != 'Linux'
-        run: pip install 'fastws-cli>=0.0.25' && ${{ env.STAGE_BPL }}
+        run: pip install 'fastws-cli>=0.0.29' && ${{ env.STAGE_BPL }}
       - uses: PyO3/maturin-action@v1
         with:
           args: --profile dist --no-default-features --compression-level 9 --out dist -i python3.11 -i python3.12 -i python3.13
           manylinux: auto
           # This runs inside the manylinux container, whose old glibc lets the binary run on older Linux distributions.
-          before-script-linux: export PATH="/opt/python/cp311-cp311/bin:$PATH" && python3.11 -m pip install 'fastws-cli>=0.0.25' && ${{ env.STAGE_BPL }}
-      # The release build's own costs, for comparison with CI's. `basedpl.bpltests.logged_costs` reads this log. Timing never fails the release.
+          before-script-linux: export PATH="/opt/python/cp311-cp311/bin:$PATH" && python3.11 -m pip install 'fastws-cli>=0.0.29' && ${{ env.STAGE_BPL }}
       - name: Time the release build
         continue-on-error: true
-        timeout-minutes: 20
         run: bin/${{ matrix.binary }} --costs tests/speed
       - uses: actions/upload-artifact@v7
         with:

basedpl-0.1.78/.github/workflows/speed.yml

@@ -0,0 +1,40 @@
+name: Speed
+
+on: workflow_dispatch
+
+permissions:
+  contents: read
+
+jobs:
+  native:
+    runs-on: ubicloud-standard-4-ubuntu-2604
+    steps:
+      - uses: actions/checkout@v7
+      - uses: dtolnay/rust-toolchain@stable
+      - uses: actions/setup-python@v7
+        with:
+          python-version: '3.12'
+      # This job times the `bpl` that releases ship, which `cargo stage --profile dist --no-default-features` builds, as the `Release` workflow does. `bpl --costs` prints every case's cost and budget for `basedpl.bpltests.logged_costs`. A case over its budget doesn't fail it. The job builds without a cache. The `Test` workflow's caches hold only test-profile builds.
+      - run: pip install 'fastws-cli>=0.0.29' && cargo stage --profile dist --no-default-features
+      - run: wheel/scripts/bpl --costs tests/speed
+      # `bpl-tests thread_scaling` times a large product, a 512×512 SVD and Hermitian eigendecomposition, a stack of QR decompositions and a large elementwise function on one thread and on as many threads as the runner has physical cores, up to 4. It fails when a case reaches less than half its expected gain. Speed budgets are single-thread measurements, so this is the check of multithreaded speed. It comes last, so that a failure here still leaves every cost logged. `lscpu` shows whether the VM reports which vCPUs share a physical core, which is how `thread_scaling` counts cores on Linux.
+      - run: lscpu
+      - run: pip install -e . && bpl-tests thread_scaling --bpl wheel/scripts/bpl
+
+  wasm:
+    runs-on: ubicloud-standard-4-ubuntu-2604
+    steps:
+      - uses: actions/checkout@v7
+      - uses: dtolnay/rust-toolchain@stable
+        with:
+          targets: wasm32-unknown-unknown
+      # These wasm costs come from the V8 of the Node that `.node-version` pins, as in the `Test` workflow's `wasm` job.
+      - uses: actions/setup-node@v7
+        with:
+          node-version-file: .node-version
+      - run: cargo generate-lockfile
+      - uses: Swatinem/rust-cache@v2
+        with:
+          shared-key: wasm
+      - run: cargo wasm --strip
+      - run: BASEDPL_COSTS=1 node --no-liftoff tests/wasm-speed.mjs

{basedpl-0.1.75 → basedpl-0.1.78}/.github/workflows/test.yml

@@ -9,9 +9,10 @@ permissions:
   contents: read
 
 # In each job, every test step after the first runs even when an earlier step fails, to report every test's result in one run.
+# A build step that runs past 10 minutes has stalled. These builds normally take about 3.
 jobs:
   test:
-    runs-on: ubicloud-standard-4
+    runs-on: ubicloud-standard-4-ubuntu-2604
     steps:
       - uses: actions/checkout@v7
       # `tests/highlighting.mjs` reads the TextMate grammar through `shiki`, which `package.json` pins.
@@ -41,12 +42,16 @@ jobs:
         if: ${{ !cancelled() }}
 
   wasm:
-    runs-on: ubicloud-standard-4
+    runs-on: ubicloud-standard-4-ubuntu-2604
     steps:
       - uses: actions/checkout@v7
       - uses: dtolnay/rust-toolchain@stable
         with:
           targets: wasm32-unknown-unknown
+      # V8's frame sizes decide the recursion test's margin. Each Node major keeps one V8 version. `.node-version` pins the major that both wasm jobs use.
+      - uses: actions/setup-node@v7
+        with:
+          node-version-file: .node-version
       - run: cargo generate-lockfile
       # The `Speed` workflow's `wasm` job restores this cache, by its `shared-key`.
       - uses: Swatinem/rust-cache@v2

basedpl-0.1.78/.node-version

@@ -0,0 +1 @@
+26

{basedpl-0.1.75 → basedpl-0.1.78}/CONTRIBUTING.md

@@ -27,7 +27,7 @@ ship-rs-build
 
 After Rust changes, run `cargo test` for the Rust tests, then `cargo develop` to install what `cargo test` built: the extension, and the native `bpl` command in your environment. Both use one compilation of each crate. `cargo develop` comes from `fastws-cli`, one of the development tools. Run `pip install -e '.[dev]'` again only when the package metadata changes. Use `cargo fastfmt`, not `cargo fmt`.
 
-Before a release, run `python scripts/prep.py` from the repository root. It writes the syntax highlighters' glyph lists and the macOS keyboard layout bundle. It then runs nbdev's `prepare` to export, test and clean the notebooks and render this README.
+Before a release, run `bpl-tests prerelease` from the repository root. Among its steps, it writes the syntax highlighters' glyph lists and the macOS keyboard layout bundle, saves the notebooks' outputs, and runs nbdev's `prepare` to export, test and clean the notebooks and render the README. DEV.md's "Release" section lists every step.
 
 ## Did you find a bug?