-
-
Notifications
You must be signed in to change notification settings - Fork 83
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.
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
Failed jars branch 20241014 #1146
Conversation
sootup.java.bytecode.frontend/src/test/resources/jar_failure.json
Outdated
Show resolved
Hide resolved
...ava.bytecode.frontend/src/test/java/sootup/java/bytecode/frontend/inputlocation/FixJars.java
Outdated
Show resolved
Hide resolved
...ava.bytecode.frontend/src/test/java/sootup/java/bytecode/frontend/inputlocation/FixJars.java
Outdated
Show resolved
Hide resolved
} | ||
|
||
@Test | ||
public void executeaudiofileRCjar() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this test. We only want to keep the isolated test version around. But also still keep the Maven coordinates of the original Jar around (maybe as a comment).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I @disable this test? This test case fails locally but the pipeline is green, that's why I asked in the group.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you investigate why this fails? Maybe due to the resolution of the artifact from Maven Central which might be cached on your machine or the pipeline?
} | ||
|
||
@Test | ||
public void executeaudiofileRCjar() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you investigate why this fails? Maybe due to the resolution of the artifact from Maven Central which might be cached on your machine or the pipeline?
No description provided.