Stabilize service tests across Gradle working directories and relax flaky FilePoller benchmark#461
Merged
Merged
Conversation
YiğitProject ID: Tip Build commands execute in runtime containers during deployment |
Co-authored-by: tryigit <40565628+tryigit@users.noreply.github.com>
Co-authored-by: tryigit <40565628+tryigit@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Stabilize daemon resilience tests across Gradle working directories
Stabilize service tests across Gradle working directories and relax flaky FilePoller benchmark
Mar 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

The failing coverage here had two edges: service tests were resolving repo fixtures through brittle relative paths that changed with Gradle’s working directory, and the API 32 instrumentation benchmark was failing on slower emulators despite still using
FileObserverrather than the 5s polling fallback.Test fixture lookup
module/template/*by walking upward fromuser.diruntil the repo fixture is found.../module/template/...usage in daemon resilience and sepolicy tests.Daemon restart safety coverage
service.shlaunches./daemonand that the daemon wrapper targetsMainKt, so non-zero exits remain covered by the retry loop.exitProcessimport fromMain.ktto satisfy the safety gate cleanly.Instrumentation benchmark stability
FilePollerInstrumentationTestdetection timeout from1500msto2500ms.5000msfallback polling interval, so the test still distinguishesFileObserverbehavior from polling.Example of the fixture resolution change:
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
dl.google.com/usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.xml/javax.xml.namespace=ALL-UNNAMED --add-opens=java.base/java.time=ALL-UNNAMED -Xmx2048m -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.