<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Am sorry I can't commit build resources, but am certainly willing to commit time to solving test problems. In a very general sense, I think our project (Ghidra) will effectively be a test platform for issues with the Java bindings to SWIG. </p>
<p><br>
</p>
<p>With regard to the set-up for testing, I have noticed differences in behavior between the "ninja check-lldb-xxx" suite-testing environment, the llvm-lit test sets, and actual lldb runs / individual tests. I believe (I should never say this out loud, but...)
the current code handles these environments correctly.</p>
<p><br>
</p>
<p>The Java scripting framework requires the ability to find two things: the Java install (and within it libjvm) and the SWIG.jar built from the JNI wrappers. If either LD_LIBRARY_PATH or JAVA_HOME is set in whichever environment is in use, the code should
be able to find libjvm. If CLASSPATH includes the SWIG.jar or we're running out of build, finding it should be handled. Libjvm is loaded dynamically, so the inclusion of my code "should" have no effect on environments without Java installed. </p>
<p><br>
</p>
<p>I was thinking I would also spend a couple of days isolating the swig logic in case supporting the Java interface becomes untenable for you. Am hoping I can pare it down so that our users could point-and-click at an existing lldb repo, without necessarily
having to build llvm/lldb.</p>
<p><br>
</p>
<p>Best, Dave</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Raphael Isemann via Phabricator <reviews@reviews.llvm.org><br>
<b>Sent:</b> Thursday, November 11, 2021 7:23:11 AM<br>
<b>To:</b> David Millar; anoronha@apple.com; fallkrum@yahoo.com; kkleine@redhat.com; medismail.bennani@gmail.com; jonas@devlieghere.com; tedwood@quicinc.com; jmolenda@apple.com; syaghmour@apple.com; jingham@apple.com; vsk@apple.com; boris.ulasevich@gmail.com;
lldb-commits@lists.llvm.org; h.imai.833@nitech.jp; bruce.mitchener@gmail.com; david.spickett@linaro.org; quic_sourabhs@quicinc.com; djordje.todorovic@syrmia.com; serhiy.redko@gmail.com; Liburd1994@outlook.com<br>
<b>Cc:</b> pavel@labath.sk; mgorny@gentoo.org<br>
<b>Subject:</b> [PATCH] D111409: proposed support for Java interface to Scripting Bridge</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">teemperor added a comment.<br>
<br>
In D111409#3124194 <<a href="https://reviews.llvm.org/D111409#3124194">https://reviews.llvm.org/D111409#3124194</a>>, @labath wrote:<br>
<br>
> In D111409#3124075 <<a href="https://reviews.llvm.org/D111409#3124075">https://reviews.llvm.org/D111409#3124075</a>>, @teemperor wrote:<br>
><br>
>>> Are you asking for dedicated physical resources for running nightly builds?<br>
>><br>
>> I don't think any of the current bots have a Java installation so I think it's either that or we get someone with a bot to setup the required Java installation.<br>
><br>
> I don't have a problem with installing the necessary packages on the bot I manage, but I cannot subscribe to tracking down any failures (or flaky tests!) for this configuration (and, in my experience, any new feature like this is going to have flaky tests).
Flaky tests (probably just one) are the reason that lua integration is not enabled on this bot.<br>
<br>
Sure, I think it should anyway not be up to any bot owner to track down flaky tests. And that nested_sessions lua test is anyway randomly failing everywhere from what I know.<br>
<br>
>> FWIW, if no one wants to host a bot for this then I won't mind testing this in own CI <<a href="https://ci.teemperor.de">https://ci.teemperor.de</a>>, but I am not using buildbot so we'll have to see if that is acceptable for the community (I could also
migrate it to buildbot, but the buildbot interface is just painful to use and I would prefer not to).<br>
><br>
> I would rather not proliferate test infrastructures.<br>
><br>
> I'm not sure which pain points are you referring to, but setting up a buildbot instance is a lot simpler these days than it used to be (in particular, you don't need to track down and install any outdated packages).<br>
<br>
It's not the setup, it's just that the lab.llvm.org interface is far less usable than Jenkins for tracking down regressions in tests (and Jenkins is already not great, so that says something). But that's just my personal preference and I agree that lab.llvm.org
should be the central place for infrastructure.<br>
<br>
Anyway, if @labath can run them on his fancy build bot then I would prefer that over having it on my bot (because I pay out of my own pocket and CPU cycles are $$$).<br>
<br>
<br>
Repository:<br>
rLLDB LLDB<br>
<br>
CHANGES SINCE LAST ACTION<br>
<a href="https://reviews.llvm.org/D111409/new/">https://reviews.llvm.org/D111409/new/</a><br>
<br>
<a href="https://reviews.llvm.org/D111409">https://reviews.llvm.org/D111409</a><br>
<br>
</div>
</span></font>
</body>
</html>