You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@texera.apache.org by "sshiv012 (via GitHub)" <gi...@apache.org> on 2026/09/10 23:58:48 UTC
[I] Vitest JUnit reports are not gitignored in the frontend [texera]
sshiv012 opened a new issue, #8490:
URL: https://github.com/apache/texera/issues/8490
### Task Summary
The junit reporters in `frontend/vitest.config.ts` and `frontend/vitest.browser.config.ts` write `frontend/junit.xml` and `frontend/junit-browser.xml` on every test run. Neither path is listed in `frontend/.gitignore`, so both are left untracked after running the suite and can be committed by accident.
```
frontend/vitest.config.ts:28 reporters: ["default", ["junit", { outputFile: "junit.xml" }]],
frontend/vitest.browser.config.ts:58 reporters: ["default", ["junit", { outputFile: "junit-browser.xml" }]],
```
Expected: both are ignored, as `/coverage` already is.
### Task Type
- [x] Refactor / Cleanup
- [ ] DevOps / Deployment / CI
- [ ] Testing / QA
- [ ] Documentation
- [ ] Performance
- [ ] Other
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Vitest JUnit reports are not gitignored in the frontend [texera]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #8490:
URL: https://github.com/apache/texera/issues/8490#issuecomment-5627162154
<!-- texera:template-compliance -->
👋 Thanks for opening this issue, @sshiv012!
It looks like the issue description doesn't quite follow our template yet:
- This issue doesn't appear to use one of our templates (Bug, Feature, or Task). Please open it using a template so the required details are captured.
Filling out the template helps reviewers understand and triage your contribution faster. Please edit the description to complete it. This message will disappear automatically once the template is followed.
You can find the template prompts by editing the description, or see [CONTRIBUTING.md](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) for the full contribution flow.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Vitest JUnit reports are not gitignored in the frontend [texera]
Posted by "sshiv012 (via GitHub)" <gi...@apache.org>.
sshiv012 commented on issue #8490:
URL: https://github.com/apache/texera/issues/8490#issuecomment-5627433473
Here was my flow, it was by Angular tests (Vitest runner). I am not sure if this is a common practice though,
cd <repo>/frontend
yarn install
./node_modules/.bin/ng test --watch=false --include='**/console-frame.component.spec.ts' i.e runs the vi test
git status --short
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Vitest JUnit reports are not gitignored in the frontend [texera]
Posted by "parshimers (via GitHub)" <gi...@apache.org>.
parshimers commented on issue #8490:
URL: https://github.com/apache/texera/issues/8490#issuecomment-5627269266
How do these normally get triggered, through sbt or some other tool? I never noticed these files being generated, maybe that's how this slipped by.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Vitest JUnit reports are not gitignored in the frontend [texera]
Posted by "mengw15 (via GitHub)" <gi...@apache.org>.
mengw15 closed issue #8490: Vitest JUnit reports are not gitignored in the frontend
URL: https://github.com/apache/texera/issues/8490
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Vitest JUnit reports are not gitignored in the frontend [texera]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #8490:
URL: https://github.com/apache/texera/issues/8490#issuecomment-5627162017
<!-- texera:welcome-first-time-contributor -->
👋 Thanks for your first contribution to Texera, @sshiv012!
If you're looking for a good place to start, browse issues labeled [`starter-task`](https://github.com/apache/texera/issues?q=is%3Aissue+is%3Aopen+label%3Astarter-task); they're scoped to be approachable for newcomers.
You can drive common housekeeping yourself by commenting one of these commands on its own line:
- **Issues.** Comment `/take` to assign an open issue to yourself, or `/untake` to release it. You can find unclaimed work with the search filter `is:issue is:open no:assignee`.
- **Sub-issues.** To link issues into a parent/child hierarchy, comment `/sub-issue #5166 #5222` on the parent to attach those children (or `/unsub-issue #5166 #5222` to detach them). From a child issue, comment `/parent-issue #5166` to set its parent, or `/unparent-issue` to clear it (the current parent is detected automatically). References may be written as `#5166` or as a bare `5166`; cross-repository references are not supported.
- **Pull requests (author only).** Comment `/request-review @user` to request a review from someone, or `/unrequest-review @user` to withdraw that request.
Each command must match exactly: `/take this` will not work, only `/take` does. For the full contribution flow, see [CONTRIBUTING.md](https://github.com/apache/texera/blob/main/CONTRIBUTING.md).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org