Skip to content

Conversation

@penalosa
Copy link
Contributor

One of the Wrangler E2E tests is checking to see if inspector messages >1MB can be succesfully sent (a regression test for a bug introduced during phase 1 of the start dev worker work). However, since we don't really want to actually log a 1MB message during tests, we had been mocking the output of console.log()/console.info(). In Vitest v3, the way we'd done this seems to have been causing an infinite loop, so instead I've replaced the mock implementation with an empty function. We don't really care about any console output in the specific test, so that shouldn't cause any issues.


  • Tests
    • TODO (before merge)
    • Tests included
    • Tests not necessary because:
  • Wrangler E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
    • I don't know
    • Required
    • Not required because:
  • Public documentation
    • TODO (before merge)
    • Cloudflare docs PR(s):
    • Documentation not necessary because: internal testing change

@penalosa penalosa requested a review from a team as a code owner February 17, 2025 12:05
@changeset-bot
Copy link

changeset-bot bot commented Feb 17, 2025

⚠️ No Changeset found

Latest commit: be9595b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@workers-devprod workers-devprod added the e2e Run wrangler + vite-plugin e2e tests on a PR label Feb 17, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Feb 17, 2025

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-wrangler-8163

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/8163/npm-package-wrangler-8163

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-wrangler-8163 dev path/to/script.js
Additional artifacts:

cloudflare-workers-bindings-extension:

wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-workers-bindings-extension-8163 -O ./cloudflare-workers-bindings-extension.0.0.0-v9e5c4e441.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-v9e5c4e441.vsix

create-cloudflare:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-create-cloudflare-8163 --no-auto-update

@cloudflare/kv-asset-handler:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-kv-asset-handler-8163

miniflare:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-miniflare-8163

@cloudflare/pages-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-pages-shared-8163

@cloudflare/unenv-preset:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-unenv-preset-8163

@cloudflare/vite-plugin:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-vite-plugin-8163

@cloudflare/vitest-pool-workers:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-vitest-pool-workers-8163

@cloudflare/workers-editor-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-workers-editor-shared-8163

@cloudflare/workers-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-workers-shared-8163

@cloudflare/workflows-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13371164498/npm-package-cloudflare-workflows-shared-8163

Note that these links will no longer work once the GitHub Actions artifact expires.


[email protected] includes the following runtime dependencies:

Package Constraint Resolved
miniflare workspace:* 3.20250204.1
workerd 1.20250204.0 1.20250204.0
workerd --version 1.20250204.0 2025-02-04

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

Copy link
Contributor

@petebacondarwin petebacondarwin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of e2e tests failed but are probably classic flakes.
But there is a linting error to resolve: https://github.com/cloudflare/workers-sdk/actions/runs/13369830840/job/37335707533?pr=8163#step:5:941

import type { DevToolsEvent } from "../src/api";

const OPTIONS = [{ remote: false }, { remote: true }] as const;
const OPTIONS = [{ remote: true }, { remote: false }] as const;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this change? I think it was originally the other way round to get a fast fail.

@penalosa penalosa merged commit 139b5ec into main Feb 17, 2025
29 checks passed
@penalosa penalosa deleted the penalosa/fix-e2e-vitest-v3 branch February 17, 2025 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

e2e Run wrangler + vite-plugin e2e tests on a PR no-changeset-required

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants