HotTests option causes 30 second timeout after build.gradle change

Open

#751 opened on May 16, 2022 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: groovy
Domain: build-system

Research direction

Reproduce the issue with LGP 3.3 using a demo-devmode project and gradle clean libertyDev --hotTests, then edit the build.gradle MicroProfile dependency as described. Trace the dependency-change handling and test-trigger path to determine whether a rebuild and test run should occur, and verify that the resulting behavior does not wait 30 seconds for an app update.

Written by the indexing model from the issue text.

Description

devMode low priority

Use LGP 3.3 and a project like demo-devmode. Start dev mode with:
gradle clean libertyDev --hotTests

After the server starts, edit the build.gradle and change the dependency providedCompile 'org.eclipse.microprofile:microprofile:4.1' to 3.3. Save the file.

Tests finished.
Tests will run automatically when changes are detected. You can also press the Enter key to run tests on demand.

CWWKM2010I: Searching for CWWKZ0003I: in /Users/paulg/WAS/devExperience/demo-devmode/build/wlp/usr/servers/defaultServer/logs/messages.log. This search will timeout after 30 seconds.
CWWKM2011E: Timed out searching for CWWKZ0003I: in /Users/paulg/WAS/devExperience/demo-devmode/build/wlp/usr/servers/defaultServer/logs/messages.log.

> Task :libertyDev
Running tests...

After the server starts dev mode runs the tests. After build.gradle is changed dev mode does not rebuild but it does attempt to run the tests. Dev mode times out waiting for an app update.

Should dev mode rebuild after a dependency is changed?
Should dev mode run the tests if no build was initiated?

Dominant language: Groovy
Stars: 52
Forks: 47
Avg merge: 1d 1h
Merged PRs (30d): 7

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.