Configure CI to run tests sequentially to avoid rate limiting

- Set max-parallel: 1 for test matrix to run tests one at a time
- Add 30-second delay before tests to space out API calls
- Update pytest config for shorter traceback output
- This should prevent the 429 rate limit errors from Alpaca API

The Alpaca API has rate limits that get exceeded when running
100+ tests in parallel across multiple Python versions. Running
sequentially will take longer but should be more reliable.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: TexasCoding

.github/workflows/ci.yml

@@ -33,6 +33,7 @@ jobs:
   test:
     runs-on: ubuntu-latest
     strategy:
+      max-parallel: 1  # Run tests sequentially to avoid rate limiting
       matrix:
         python-version: ['3.10', '3.11', '3.12']
 
@@ -48,6 +49,11 @@ jobs:
     - name: Install dependencies
       run: uv sync --all-extras --dev
 
+    - name: Add delay to avoid rate limiting
+      run: |
+        echo "Waiting 30 seconds to avoid API rate limiting..."
+        sleep 30
+
     - name: Run tests with coverage
       env:
         ALPACA_API_KEY: ${{ secrets.ALPACA_API_KEY }}

.github/workflows/test-package.yaml

@@ -13,7 +13,7 @@ jobs:
     build:
       runs-on: ${{ matrix.os }}
       strategy:
-        max-parallel: 1
+        max-parallel: 1  # Run sequentially to avoid rate limiting
         fail-fast: false
         matrix:
           python-version: ["3.12"]

pyproject.toml

@@ -152,6 +152,7 @@ addopts = [
     "--cov-report=term-missing",
     "--cov-report=html",
     "--cov-report=xml",
+    "--tb=short",  # Shorter traceback format
 ]
 markers = [
     "slow: marks tests as slow (deselect with '-m \"not slow\"')",