Unexpected caching behavior in turbo test: broken test results get cached and shown on revert #11016
Unanswered
arthurgubaidullin
asked this question in
Help
Unexpected caching behavior in turbo test: broken test results get cached and shown on revert
#11016
Replies: 1 comment 3 replies
-
|
Can you share your |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Yep, sure. Here is the relevant part of the lib-template/package.json and the root turbo.json configuration: lib-template {
"name": "@lol/lib-template",
"type": "module",
"main": "dist/index.js",
"types": "dist/index.d.ts",
"scripts": {
"prebuild": "rm -rf dist node_modules/.tmp/tsconfig.build.tsbuildinfo",
"build": "tsc -p tsconfig.build.json",
"test": "vitest . --run",
"lint": "eslint ."
},
"dependencies": {},
"devDependencies": {
"@lol/tsconfig": "*",
"typescript": "^5.9.3",
"vitest": "^4.0.3"
},
"private": true,
"files": [
"dist"
]
}
{
"$schema": "https://turborepo.com/schema.json",
"tasks": {
"build": {
"dependsOn": ["^build"],
"outputs": ["dist/**"]
},
"test": {
"dependsOn": ["build"]
},
"lint": {
"dependsOn": ["build"]
},
"dev": {
"dependsOn": ["^build"],
"persistent": true,
"cache": false
}
}
}Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
This is what the execution result looks like: $ turbo test --filter @lol/lib-templateturbo 2.5.8
• Packages in scope: @lol/lib-template
• Running test in 1 packages
• Remote caching disabled
@lol/lib-template:build: cache hit (outputs already on disk), replaying logs adc7df28afaca2f3
@lol/lib-template:build:
@lol/lib-template:build:
@lol/lib-template:build: > prebuild
@lol/lib-template:build: > rm -rf dist node_modules/.tmp/tsconfig.build.tsbuildinfo
@lol/lib-template:build:
@lol/lib-template:build: > build
@lol/lib-template:build: > tsc -p tsconfig.build.json
@lol/lib-template:build:
@lol/lib-template:test: cache hit (outputs already on disk), replaying logs 21d27bc8524ad2a9
@lol/lib-template:test:
@lol/lib-template:test:
@lol/lib-template:test: > test
@lol/lib-template:test: > vitest . --run
@lol/lib-template:test:
@lol/lib-template:test: RUN v4.0.3 /workspaces/lol/lib-template
@lol/lib-template:test:
@lol/lib-template:test: ❯ src/index.test.ts (1 test | 1 failed) 4ms
@lol/lib-template:test: × increment(1) === 2 4ms
@lol/lib-template:test:
@lol/lib-template:test: ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
@lol/lib-template:test:
@lol/lib-template:test: FAIL src/index.test.ts > increment(1) === 2
@lol/lib-template:test: AssertionError: expected 2 to strictly equal 22
@lol/lib-template:test:
@lol/lib-template:test: - Expected
@lol/lib-template:test: + Received
@lol/lib-template:test:
@lol/lib-template:test: - 22
@lol/lib-template:test: + 2
@lol/lib-template:test:
@lol/lib-template:test: ❯ src/index.test.ts:4:24
@lol/lib-template:test: 2|
@lol/lib-template:test: 3| it("increment(1) === 2", () => {
@lol/lib-template:test: 4| expect(increment(1)).toStrictEqual(22);
@lol/lib-template:test: | ^
@lol/lib-template:test: 5| });
@lol/lib-template:test: 6|
@lol/lib-template:test:
@lol/lib-template:test: ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯
@lol/lib-template:test:
@lol/lib-template:test:
@lol/lib-template:test: Test Files 1 failed (1)
@lol/lib-template:test: Tests 1 failed (1)
@lol/lib-template:test: Start at 16:42:57
@lol/lib-template:test: Duration 197ms (transform 25ms, setup 0ms, collect 32ms, tests 4ms, environment 0ms, prepare 8ms)
@lol/lib-template:test:
npm error Lifecycle script `test` failed with error:
npm error code 1
npm error path /workspaces/lol/lib-template
npm error workspace @lol/lib-template
npm error location /workspaces/lol/lib-template
npm error command failed
npm error command sh -c vitest . --run
Tasks: 2 successful, 2 total
Cached: 2 cached, 2 total
Time: 20ms >>> FULL TURBO |
Beta Was this translation helpful? Give feedback.
-
|
Hmm. There's certainly something wrong here but it's hard to tell without a full reproduction. Please open an issue with a complete reproduction so we can look. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Is there a recommended way to configure turborepo or clear the cache to prevent broken test results from being cached and displayed after a revert?
Any guidance or suggestions for correct setup would be greatly appreciated.
Additional information
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions