Troubleshooting

This section covers common issues when working with the SeaLights SBT plugin and how to resolve them.

Issue
Possible Cause
Resolution

JARs not found

Incorrect paths to SeaLights JARs

Verify sealightsBuildScannerJar and sealightsTestListenerJar are correct and accessible

Relative paths not working

Paths resolved from project root

Ensure relative paths (e.g., project/..) are valid from the root project directory

Tests are not instrumented

Tests are not running in forked JVM

Ensure fork := true is set for test tasks and not overridden later

No coverage reported

Test Listener not running or misconfigured

Verify Test Listener is correctly configured and tests are executed

Build succeeds but no data in SeaLights

Missing or incorrect Build Session ID

Ensure Build Scanner ran successfully before tests

testsonly mode

No previous scan exists

Run a full build or scanonly first to generate a Build Session ID

SeaLights disabled unexpectedly

sealightsDisabled flag enabled

Check sealightsDisabled := Some(true) or -DsealightsDisabled=true

Plugin tasks not executed

Incorrect SBT command or plugin not loaded

Verify plugin is added in project/plugins.sbt and run sbt tasks to confirm

CI builds behave differently

Environment differences (paths, permissions)

Verify JAR paths, config file location, and environment variables in CI

Connection issues to SeaLights

Network or proxy configuration

Ensure outbound connectivity and configure JVM proxy settings if needed

Debugging Tips

Enable Debug Logging

Run the Build Scanner with debug logs:

java -jar sl-build-scanner.jar -sbt -configfile ./sl-config.json -logLevel debug -workspacepath ./my-project

Verify Build Scanner Execution

Make sure the Build Scanner runs successfully before tests:

  • Check logs for Build Session ID generation

  • Ensure no errors during scan phase

Verify Test Execution Flow

Confirm that:

  • tests are actually executed

  • tests run in forked JVMs

  • Test Listener is attached

Validate Configuration

Double-check:

  • sl-config.json path

  • JAR locations

  • execution mode (scanonly, testsonly, full)

Last updated

Was this helpful?