You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reproduce, push either commit to Github and then check the result from Github Actions.
Note:
The project uses Vitest and contains only one minimal tests for troubleshooting:
import{describe,expect,it}from'vitest';describe('sitemap.ts',()=>{it('should run tests',()=>{expect(1+1).toBe(2);});});
I've tried various tweaks to Vitest's configuration and changing the install command was what fixed it on Github Actions. In all tweaks attempted, tests ran successfully locally.
What is the expected behavior?
The tests should run equally well irrespective of whether bun install or npm install is used within ci.yml
What version of Bun is running?
oven-sh/setup-bun@v1 (1.0.10+d85bd49d8)
What platform is your computer?
Ubuntu on Github Actions
What steps can reproduce the bug?
.github/workflows/ci.yml
usesbun install
; vitest always fails.You can view the job output from this commit here: https://github.com/jasongitmail/super-sitemap/actions/runs/6789375785/job/18456422682
bun install
tonpm install
.You can view the job output from this commit here: https://github.com/jasongitmail/super-sitemap/actions/runs/6789414175/job/18456545519
Note:
What is the expected behavior?
The tests should run equally well irrespective of whether
bun install
ornpm install
is used within ci.ymlWhat do you see instead?
Error: No test suite found in file /home/runner/work/super-sitemap/super-sitemap/src/lib/sitemap.test.ts
You can view the error on Github Actions at: https://github.com/jasongitmail/super-sitemap/actions/runs/6789375785/job/18456422682
But the file does exist--the job step before the tests runs uses
cat
to output the contents of the tests file successfully.Additional information
bun install
is used. The issue only occurs on Github Actions.bun run --bun vitest
because I know that does not work yet.The text was updated successfully, but these errors were encountered: