[
https://issues.apache.org/jira/browse/LUCENE-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526081#comment-17526081
]
Robert Muir commented on LUCENE-10528:
--------------------------------------
I would prefer autodetecting, since it would make CI and local configs easier.
e.g. to enable testing luke on pull requests:
{noformat}
diff --git a/.github/workflows/gradle-precommit.yml
b/.github/workflows/gradle-precommit.yml
index c065eb005da..746e5ff7495 100644
--- a/.github/workflows/gradle-precommit.yml
+++ b/.github/workflows/gradle-precommit.yml
@@ -86,6 +86,9 @@ jobs:
${{ runner.os }}-gradle-precommit-
${{ runner.os }}-gradle-
+ - name: Install virtual X server
+ run: sudo apt-get install xvfb
+
- name: Initialize gradle settings
run: ./gradlew localSettings --max-workers 2
{noformat}
> TestScripts.testLukeCanBeLaunched creates X Window when running the tests
> -------------------------------------------------------------------------
>
> Key: LUCENE-10528
> URL: https://issues.apache.org/jira/browse/LUCENE-10528
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Major
>
> When running the tests, this one causes my entire desktop to "flicker" when
> it creates some kind of X-Window very quickly and then destroys it. I use
> tiling window manager, so whole desktop gets rearranged for a split second,
> and I'd rather it not happen :)
> I first tried adding -Djava.awt.headless=true to both org.gradle.jvmargs and
> tests.jvmargs in my .gradle/gradle.properties. doesn't work, as the test
> doesnt use these when launching luke.
> I next tried hacking the test by adding this to the ProcessBuilderThingy, but
> it didn't help either:
> {noformat}
> .envvar("LAUNCH_OPTS", "-Djava.awt.headless=true")
> {noformat}
> One way I can work around it, is to unset {{DISPLAY}} env var so that it
> won't create this window. test still passes:
> {noformat}
> $ unset DISPLAY
> $ ./gradlew :lucene:distribution.tests:test
> ... (no window gets created)
> {noformat}
> So maybe as a workaround, we can just not pass DISPLAY environment variable
> through to this test?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
