Skip to content

remove compat test #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mansona wants to merge 1 commit into from
Closed

remove compat test #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 0 additions & 15 deletions tests/default.test.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,21 +10,6 @@
flags: [],
fixturePath: join(import.meta.dirname, 'fixture'),
},
{
name: 'compat (v1 addon support)',
// @glimmer/component >= 2.0.0 is a v2 addon, which we don't need when testing "compat mode"
// this test is "compat mode"
// compat mode forces us to use v1 addon infra, ember-cli, etc
flags: [
/* none, default */
],
packageJson: {
devDependencies: {
'@glimmer/component': '^1.1.2',
},
},
fixturePath: join(import.meta.dirname, 'fixture'),
},
{
name: 'typescript',
flags: ['--typescript'],
Expand Down Expand Up @@ -137,7 +122,7 @@
`,
);

let testResult = await project.execa('pnpm', [

Check failure on line 125 in tests/default.test.mjs

View workflow job for this annotation

GitHub Actions / Test

tests/default.test.mjs > basic functionality > defaults > successfully runs tests in dev mode 

ExecaError: Command failed with exit code 1: pnpm testem --file testem-dev.js ci

not ok 1 Chrome 139.0 - [undefined ms] - Global error: Uncaught Error: Cannot call `setComponentTemplate` multiple times on the same class (`@glimmer/component/template-only`) at http://localhost:7357/node_modules/.vite/deps/chunk-FNYHRVNV.js?v=e8efa5b3, line 1271
    ---
        browser log: |
            {"type":"info","text":"[vite] Direct websocket connection fallback. Check out https://vite.dev/config/server-options.html#server-hmr to remove the previous connection error."}
            {"type":"warn","text":"DEPRECATION: Using WarpDrive with EmberJS requires configuring it to use Ember's reactivity system.\nPreviously this was provided by installing the package '@ember-data/tracking', but this package is now deprecated.\n\nTo resolve this deprecation, follow these steps:\n- remove \"@ember-data/tracking\" and (if needed) \"@ember-data-types/tracking\" from your project in both your package.json and tsconfig.json\n- add \"@warp-drive/ember\" to your project in both your package.json and tsconfig.json\n- add the following import to your app.js file:\n\n\t```\n\timport '@warp-drive/ember/install';\n\t```\n\n- mark this deprecation as resolved in your project by adding the following to your WarpDrive config in ember-cli-build.js:\n\n\t```\n\tconst { setConfig } = await import(\"@warp-drive/build-config\");\n\tsetConfig(app, __dirname, {\n\t  deprecations: {\n\t    DEPRECATE_TRACKING_PACKAGE: false,\n\t  },\n\t});\n\t```\n\nFor more information, see the Package Unification RFC: https://rfcs.emberjs.com/id/1075-warp-drive-package-unification/ [deprecation id: warp-drive.deprecate-tracking-package] This will be removed in warp-drive 6.0.0. See https://deprecations.emberjs.com/id/warp-drive.deprecate-tracking-package for more details.\n        at logDeprecationStackTrace (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:285:19)\n        at HANDLERS.<computed> (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:228:7)\n        at raiseOnDeprecation (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:310:7)\n        at HANDLERS.<computed> (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:228:7)\n        at http://localhost:7357/node_modules/.vite/deps/chunk-H2U77DZ2.js?v=e8efa5b3:713:10\n        at HANDLERS.<computed> (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:228:7)\n        at handleDeprecationWorkflow (http://localhost:7357/node_modules/.vite/deps/ember-cli-deprecation-workflow.js?v=ed903eda:59:7)\n        at http://localhost:7357/node_modules/.vite/deps/ember-cli-deprecation-workflow.js?v=ed903eda:11:47\n        at HANDLERS.<computed> (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:228:7)"}
            {"type":"warn","text":"DEPRECATION: You are relying on ember-data auto-magically installing the store service. Use `export { default } from 'ember-data/store';` in app/services/store.js instead [deprecation id: ember-data:deprecate-legacy-imports] This will be removed in ember-data 6.0.\n        at logDeprecationStackTrace (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:285:19)\n        at HANDLERS.<computed> (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:228:7)\n        at raiseOnDeprecation (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:310:7)\n        at HANDLERS.<computed> (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:228:7)\n        at http://localhost:7357/node_modules/.vite/deps/chunk-H2U77DZ2.js?v=e8efa5b3:713:10\n        at HANDLERS.<computed> (http://localhost:7357/node_modules/.vite/deps/chunk-VPCMFPHL.js?v=e8efa5b3:228:7)\n        at handleDeprecationWorkflow (http://localhost:7357/node_modules/.vite/deps/ember-cli-deprecation-workflow.js?v=ed903eda:59:7)\n        at http://localhost:7357/node_modules/.vite/deps/ember-cli-deprecation-workflow.js?v=ed903eda:11:
'testem',
'--file',
'testem-dev.js',
Expand Down
Loading