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.

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

Trace collected for single test, but fails on all test #248

Open
algomaster99 opened this issue May 22, 2023 · 1 comment
Open

Trace collected for single test, but fails on all test #248

algomaster99 opened this issue May 22, 2023 · 1 comment
Labels
bug Something isn't working trace-collector

Comments

@algomaster99
Copy link
Member

For commit cdk/cdk@8469dd2, we generate non-empty trace for test org.openscience.cdk.structgen.maygen.MaygenTest::test_gettersAndSetters. However, when all tests are run, no trace is collected.

Command to reproduce:

java -jar main/target/collector-sahab-0.5.2-SNAPSHOT-jar-with-dependencies.jar -p /home/aman/testrepos/cdk -l  d5365ab -r 8469dd2f3f8d0361b4f3f05a6da9ad3098f41a87 -c tool/structgen/src/main/java/org/openscience/cdk/structgen/maygen/Maygen.java  --slug "cdk/cdk" --selected-tests org.openscience.cdk.structgen.maygen.MaygenTest::test_gettersAndSetters
@algomaster99 algomaster99 added bug Something isn't working trace-collector labels May 22, 2023
@algomaster99
Copy link
Member Author

algomaster99 commented May 22, 2023

mvn test runs on each module if all tests are executed. Whenever mvn test process shuts down, we output a trace. For multi-module project, this is WRONG because every time the trace is replaced and we lose information from previous modules.

This problem can be addressed when we output trace as line-delimited JSON for faster processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working trace-collector
Projects
None yet
Development

No branches or pull requests

1 participant