JTRegs for OpenJDK
jonathan.gibbons at oracle.com
Thu Jun 21 12:00:16 PDT 2012
Once you build the code to analyze a make log, you can provide alternate
ways to view the info.
1. Use a tree of html files as I described.
2. Write a Java utility that hides the tree of HTML files, so that you
can just go
% make-browse make.log
and have it analyse the text on the fly.
On 06/21/2012 11:39 AM, Mani Sarkar wrote:
> That's a great start, I find the idea interesting.
> +1 nested logs, clicking, etc
> On 21 Jun 2012 19:24, "Jonathan Gibbons" <jonathan.gibbons at oracle.com
> <mailto:jonathan.gibbons at oracle.com>> wrote:
> In a previous job, I wrote a script to convert a make log into
> series of HTML files, such that recursive makes were detected, so
> that if one make file invoked another, the output from the child
> make was moved to separate file and then replaced in the parent
> log by a link. The result is a tree of Makefiles that you can
> easily browse through. It's easy to add in additional features
> to compress long command lines that expand when you click on them,
> etc. Was it useful back then: yes, very. Would it be useful
> now? Maybe not so much, especially with the new makefiles coming
> -- Jon
> On 06/21/2012 10:11 AM, Mani Sarkar wrote:
>> Thanks Kelly for the response, I do understand its not a top prio
>> Maybe I might be a able to help you out there with some utility
>> program . ;) don't want to make any promises but when I get
>> around it ill post a.copy of the program to the list.
>> On 21 Jun 2012 17:51, "Kelly O'Hair" <kelly.ohair at oracle.com
>> <mailto:kelly.ohair at oracle.com>> wrote:
>> These messages are just echos of the commands being run, if
>> you have a suggested change to make them
>> somehow more readable, I'm sure we would consider it. But
>> it's not a high item on my priority list. Sorry.
>> When some of this original makefile logic was written, jtreg
>> was pretty basic, and it has changed since then,
>> such that we might be able to simplify some of this makefile
>> shell logic.
>> On Jun 21, 2012, at 2:16 AM, Mani Sarkar wrote:
>>> Thanks ill take a look at it.
>>> I do have a suggestion though if there could be tabs, spaces
>>> and some sort of indentation added to the messages and logs
>>> the makes and scripts display. I love the fact that they are
>>> so verbose just a bit of tweak will help us able to read
>>> these msgs easily .
>>> Thanks again.
>>> On 21 Jun 2012 09:56, "Weijun Wang" <weijun.wang at oracle.com
>>> <mailto:weijun.wang at oracle.com>> wrote:
>>> Hi Mani
>>> Welcome to the OpenJDK!
>>> On 06/21/2012 02:31 PM, Mani Sarkar wrote:
>>> I have been configuring and testing the JTRegs with
>>> OpenJDK on Ubuntu
>>> 12.04 and attached are couple of log files with errors.
>>> Can someone help me out understand where the config
>>> for the JTRegs is
>>> going wrong, or is it a different problem altogether.
>>> One of them mentions win32 in the log, while I'm
>>> using linux. I have
>>> attached .sh file that updates the environment along
>>> with this message.
>>> test1.log has
>>> so it's using the build inside jdk8_tl/jdk. I guess you
>>> directly call make in jdk8_tl and your build is also
>>> there. I read the Makefile a little and seems you can
>>> try again your test with
>>> Please do not set the ALT_OUTPUTDIR variable permanent
>>> as it might interfere with your build.
>>> *Kelly*: Is it true that launching a test from the top
>>> directory cannot use the control build?
>>> As for test2.log, it shows
>>> JT_HOME=/home/openjdk/jtreg/linux/bin. It should be only
>>> It's OK to see a win32, those scripts are essentially
>>> the same across platforms.
>>> Good luck!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jtreg-use