-
Notifications
You must be signed in to change notification settings - Fork 732
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
Several test failures during the 'mvn package' process #1360
Comments
While looking at one of the sample snippets provided in my previous comment (20240913_formatTypeReferenceArray_IndividualTestFailure.txt), I did observe a difference in indentations between the expected vs actual result (even though my IDE did not point this out). As seen in the image, the closing bracket under the actual results is indented by 2 characters (column 3). Meanwhile the closing bracket under the expected results is under column 1. |
Bug description
When running the
mvn package
ormvn clean package
command, thepackage
process fails on the "Spring AI Core" module, due to several test failures in the "BeanOutputConverterTest" class.Note:
mvn clean package -DskipTests
).Environment
main
branch (currently commit5a35213
at the time of writing this), if this helps.Steps to reproduce
Option A:
mvn clean package
. Observe the test failuresOption B:
mvn clean
(this will return successful build logs)mvn package
(this will return the test failures)The main thing is running
mvn package
in some way, to produce the failures.Expected behavior
mvn package
without having to skip testsMinimal Complete Reproducible example
Other notes
formatTypeReferenceArray
test (located inspring-ai-core/src/test/java/org/springframework/ai/converter/BeanOutputConverterTest.java
), I got a failed result due to the following error:20240913_formatTypeReferenceArray_IndividualTestFailure.txt
The test failures seem bizarre, and there's no immediate reason that I can see as to why these issues are happening. But unfortunately its happening, hence this issue being filed. I am still actively investigating this issue as well, just in case this turns out being a silly "me" issue in some way.
The text was updated successfully, but these errors were encountered: