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
Skipped tests when parallelExecution is false #2054
Comments
Maybe I'm reading your github actions incorrect but just in case I'm not I'm going to post it here anyways. I'm not that familiar with github actions and your testing flow. Looking a test report before 1.2.4 I can see that every report has at least one passed test https://github.com/7mind/izumi/actions/runs/6739072294/job/18320219110 This is not the case for the latest build |
- Make path comparisons less strict - Regression was caused by some classpath elements containing trailing / non-deterministically - Print a diagnostic message if test class filtering occured
- Make path comparisons less strict - Regression was caused by some classpath elements containing trailing `/` non-deterministically - Print a diagnostic message if test class filtering occured
@felix-hedenstrom Fixed in NB: distage-teskit ignores |
I've encountered an issue where when I run distage test kit some tests are skipped in
1.2.4
. I did not manage to reproduce the issue in1.2.3
If we look at this example
and run it using
sbt test
whenparallelExecution in ThisBuild := false
I getwith the notable part being
Total number of tests run: 1
even though it detected both suites. If I setparallelExecution in ThisBuild := true
I get what I would expect
I have observed similar issues in a larger real project with parallelExecution as both true and false but it is hard to reproduce it in a reasonably small example.
The text was updated successfully, but these errors were encountered: