Need help resolving a gradlew build issue - one test passes in CI but fails locally

[JadeCheah]

Hi, I’m seeing a test failure locally on the latest master branch that doesn’t occur in CI.
My local master is fully synced with the upstream repo. I haven’t made any changes to the codebase. Running ./gradlew clean build results in this one test failure.

Command:

./gradlew clean build

Testcase faild:

generateReposReport_isOnlyTextRefreshedTrueButInvalidPath_throwsIoException

Error:

org.opentest4j.AssertionFailedError: Expected java.io.IOException to be thrown, but nothing was thrown.

Environment:

• macOS 14.6

• Java 17.0.11 (Zulu build)

Things I’ve tried:

• ./gradlew clean

• Verified no local changes with git status and git diff

• Ensured that the test data/resources were untouched

Still not sure why this is failing locally when it passes on CI.

Would appreciate any help or suggestions. Thanks a lot!

[CYX22222003]

I also face a similar issue. This may be because you have accidentally changed the default templateZip.zip when you are doing experiment. This may cause the exception to not be thrown.

I suggest you to delete all the build files in frontend and backend, .gradle folder, as well as the tempered template zip file. Then, rerun gradle build or test.

Hope this can resolve the issue

[CYX22222003]

In the test case, the summaryJsonPath shouldn't exist and an IO exception is expected to thrown. You may try to check the details of the summaryJsonPath for generateReposReport methods by using logger.info to find out where this JSON file is coming from.

[JadeCheah]

I tried adding the following logging in generateReposReport to trace the summary.json path:

logger.info("Checking summaryJsonPath: " + summaryJsonPath.toAbsolutePath());
logger.info("Exists? " + Files.exists(summaryJsonPath));
if (!Files.exists(summaryJsonPath)) {
    throw new IOException("summary.json does not exist in the output folder. Aborting report generation.");
}

From the logs, I found that summary.json is being read from:
RepoSense/build/resources/test/ReportGeneratorTest/test_assets/summary.json

[CYX22222003]

That's great. If you browse the directory, you will find zip files then you accidentally generated when you are learning the codebase. Locate and remove all traces of these zip files using tools like grep

[JadeCheah]

Thanks for that! The issue is resolved. The root cause was a stray summary.json in frontend/public/ that had been accidentally generated and was .gitignored. While deleting zip files didn’t solve it, the suggestion to check for accidentally generated files was extremely helpful and led me to investigate more into the ignored files. Deleting the summary.json fixed the test. Once again, really appreciate the help!