Skip to content
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

Jump to bottom

JitCI Not Detecting JUnit Test #32

Open
gmitch215 opened this issue Aug 15, 2022 · 4 comments
Open

JitCI Not Detecting JUnit Test #32

gmitch215 opened this issue Aug 15, 2022 · 4 comments

Comments

@gmitch215
Copy link

gmitch215 commented Aug 15, 2022 •
edited
Loading

Hello,
JitPack doesn't seem to be detecting the maven tests, even though they run successfully:
image
image

Is this normal? I couldn't find anything in settings about this.
@jitpack-io
Copy link
Member

Hi

Which repository was this for?

@gmitch215
Copy link
Author

gmitch215 commented Sep 5, 2022 •
edited
Loading

@jitpack-io
Team-Inceptus/Runcaria

I think this was tested with JUnit 5 (but I'm not sure), with the correct maven-surefire-plugin.

@gmitch215
Copy link
Author

I might've found something related to the issue @jitpack-io
image

@nbauma109
Copy link

I have the same error:

Corrupted channel by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /home/jitpack/build/jd-gui-duo/services/target/surefire-reports/2024-05-25T04-42-04_595-jvmRun1.dumpstream

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nbauma109 @jitpack-io @gmitch215