From christian.tornqvist at oracle.com Tue Jun 5 06:29:19 2012 From: christian.tornqvist at oracle.com (Christian Tornqvist) Date: Tue, 05 Jun 2012 15:29:19 +0200 Subject: Accessing test root variable in Run tag Message-ID: <4FCE09AF.2030300@oracle.com> Hi, I'm trying to use jtreg for running tests which requires native libraries, so my idea was to put the native libraries in a subfolder to the test root and run it using something like this: @run main/othervm -Djava.library.path=$TESTSRC/native Test So basically I want to be able to use paths relative to the test root in my @run tag, how would I do that? :) Best regards, Christian From sadhak001 at gmail.com Wed Jun 20 23:31:57 2012 From: sadhak001 at gmail.com (Mani Sarkar) Date: Thu, 21 Jun 2012 07:31:57 +0100 Subject: JTRegs for OpenJDK Message-ID: Hi 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. Regards, Mani -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/2ee92db7/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: test.log Type: application/octet-stream Size: 7189 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/2ee92db7/test.log -------------- next part -------------- A non-text attachment was scrubbed... Name: test2.log Type: application/octet-stream Size: 7147 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/2ee92db7/test2.log -------------- next part -------------- A non-text attachment was scrubbed... Name: jdk8-env.sh Type: application/x-sh Size: 382 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/2ee92db7/jdk8-env.sh From weijun.wang at oracle.com Thu Jun 21 01:56:22 2012 From: weijun.wang at oracle.com (Weijun Wang) Date: Thu, 21 Jun 2012 16:56:22 +0800 Subject: JTRegs for OpenJDK In-Reply-To: References: Message-ID: <4FE2E1B6.8090609@oracle.com> Hi Mani Welcome to the OpenJDK! On 06/21/2012 02:31 PM, Mani Sarkar wrote: > Hi > > 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 -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 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 make ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 jdk_util 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 /home/openjdk/jtreg. It's OK to see a win32, those scripts are essentially the same across platforms. Good luck! -Max > > Regards, > Mani From sadhak001 at gmail.com Thu Jun 21 02:16:08 2012 From: sadhak001 at gmail.com (Mani Sarkar) Date: Thu, 21 Jun 2012 10:16:08 +0100 Subject: JTRegs for OpenJDK In-Reply-To: <4FE2E1B6.8090609@oracle.com> References: <4FE2E1B6.8090609@oracle.com> Message-ID: 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. Mani On 21 Jun 2012 09:56, "Weijun Wang" wrote: > Hi Mani > > Welcome to the OpenJDK! > > On 06/21/2012 02:31 PM, Mani Sarkar wrote: > >> Hi >> >> 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 > > -jdk:/home/openjdk/sources/**jdk8_tl/jdk/test/../build/**linux-amd64 > > 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 > > make ALT_OUTPUTDIR=/home/openjdk/**sources/jdk8_tl/build/linux-**amd64 > jdk_util > > 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 /home/openjdk/jtreg. > > It's OK to see a win32, those scripts are essentially the same across > platforms. > > Good luck! > > -Max > > >> Regards, >> Mani >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/6783b63d/attachment-0001.html From jonathan.gibbons at oracle.com Thu Jun 21 07:30:38 2012 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 21 Jun 2012 07:30:38 -0700 Subject: JTRegs for OpenJDK In-Reply-To: References: Message-ID: <4FE3300E.1090205@oracle.com> On 06/20/2012 11:31 PM, Mani Sarkar wrote: > Hi > > 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. > > Regards, > Mani Do not worry about the win32 issue. For historical reasons, there is a platform component in the pathname for the jtreg script, but the current reality is that the script is the same on all platforms, solaris, linux and win32. The makefile you are using arbitrarily chooses one, which happens to be win32. For general info on configuring jtreg, see http://openjdk.java.net/jtreg In particular, for info on running jtreg via the Makefiles, see http://openjdk.java.net/jtreg/#makefile Note that you need to set PRODUCT_HOME to the version of JDK to be tested. -- Jon From kelly.ohair at oracle.com Thu Jun 21 09:46:21 2012 From: kelly.ohair at oracle.com (Kelly O'Hair) Date: Thu, 21 Jun 2012 09:46:21 -0700 Subject: JTRegs for OpenJDK In-Reply-To: <4FE2E1B6.8090609@oracle.com> References: <4FE2E1B6.8090609@oracle.com> Message-ID: On Jun 21, 2012, at 1:56 AM, Weijun Wang wrote: > Hi Mani > > Welcome to the OpenJDK! > > On 06/21/2012 02:31 PM, Mani Sarkar wrote: >> Hi >> >> 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 > > -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 > > 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 > > make ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 jdk_util > > 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? It's tricky to know exactly where the built j2sdk-image area is. I would recommend using: cd test && make PRODUCT_HOME=/full/path/to/java_home jdk_util Not sure the top level test/Makefile will find the built image correctly, I tend to be explicit. > > As for test2.log, it shows JT_HOME=/home/openjdk/jtreg/linux/bin. It should be only /home/openjdk/jtreg. Correct JT_HOME is the base directory where jtreg is installed, not the bin directory. > > It's OK to see a win32, those scripts are essentially the same across platforms. Correct. It was easiest to just refer to that one script for all platforms in the Makefile. -kto > > Good luck! > > -Max > >> >> Regards, >> Mani From kelly.ohair at oracle.com Thu Jun 21 09:51:06 2012 From: kelly.ohair at oracle.com (Kelly O'Hair) Date: Thu, 21 Jun 2012 09:51:06 -0700 Subject: JTRegs for OpenJDK In-Reply-To: References: <4FE2E1B6.8090609@oracle.com> Message-ID: <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> 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. -kto 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. > > Mani > > On 21 Jun 2012 09:56, "Weijun Wang" wrote: > Hi Mani > > Welcome to the OpenJDK! > > On 06/21/2012 02:31 PM, Mani Sarkar wrote: > Hi > > 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 > > -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 > > 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 > > make ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 jdk_util > > 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 /home/openjdk/jtreg. > > It's OK to see a win32, those scripts are essentially the same across platforms. > > Good luck! > > -Max > > > Regards, > Mani -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/805dce85/attachment.html From sadhak001 at gmail.com Thu Jun 21 10:11:52 2012 From: sadhak001 at gmail.com (Mani Sarkar) Date: Thu, 21 Jun 2012 18:11:52 +0100 Subject: JTRegs for OpenJDK In-Reply-To: <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> References: <4FE2E1B6.8090609@oracle.com> <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> Message-ID: Thanks Kelly for the response, I do understand its not a top prio requirement. 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. Cheers, Mani On 21 Jun 2012 17:51, "Kelly O'Hair" 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. > > -kto > > 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. > > Mani > On 21 Jun 2012 09:56, "Weijun Wang" wrote: > >> Hi Mani >> >> Welcome to the OpenJDK! >> >> On 06/21/2012 02:31 PM, Mani Sarkar wrote: >> >>> Hi >>> >>> 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 >> >> -jdk:/home/openjdk/sources/**jdk8_tl/jdk/test/../build/**linux-amd64 >> >> 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 >> >> make ALT_OUTPUTDIR=/home/openjdk/**sources/jdk8_tl/build/linux-**amd64 >> jdk_util >> >> 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 /home/openjdk/jtreg. >> >> It's OK to see a win32, those scripts are essentially the same across >> platforms. >> >> Good luck! >> >> -Max >> >> >>> Regards, >>> Mani >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/7d777b73/attachment.html From kelly.ohair at oracle.com Thu Jun 21 10:37:05 2012 From: kelly.ohair at oracle.com (Kelly O'Hair) Date: Thu, 21 Jun 2012 10:37:05 -0700 Subject: JTRegs for OpenJDK In-Reply-To: References: <4FE2E1B6.8090609@oracle.com> <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> Message-ID: <0C945DA4-2FFE-4697-961C-CC614655190A@oracle.com> On Jun 21, 2012, at 10:11 AM, Mani Sarkar wrote: > Thanks Kelly for the response, I do understand its not a top prio requirement. > > 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. > > That would be great. -kto > Cheers, > Mani > > On 21 Jun 2012 17:51, "Kelly O'Hair" 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. > > -kto > > 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. >> >> Mani >> >> On 21 Jun 2012 09:56, "Weijun Wang" wrote: >> Hi Mani >> >> Welcome to the OpenJDK! >> >> On 06/21/2012 02:31 PM, Mani Sarkar wrote: >> Hi >> >> 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 >> >> -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 >> >> 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 >> >> make ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 jdk_util >> >> 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 /home/openjdk/jtreg. >> >> It's OK to see a win32, those scripts are essentially the same across platforms. >> >> Good luck! >> >> -Max >> >> >> Regards, >> Mani > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/85e39621/attachment-0001.html From jonathan.gibbons at oracle.com Thu Jun 21 11:24:11 2012 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 21 Jun 2012 11:24:11 -0700 Subject: JTRegs for OpenJDK In-Reply-To: References: <4FE2E1B6.8090609@oracle.com> <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> Message-ID: <4FE366CB.1040209@oracle.com> 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 online. -- Jon On 06/21/2012 10:11 AM, Mani Sarkar wrote: > > Thanks Kelly for the response, I do understand its not a top prio > requirement. > > 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. > > Cheers, > Mani > > On 21 Jun 2012 17:51, "Kelly O'Hair" > 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. > > -kto > > 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. >> >> Mani >> >> On 21 Jun 2012 09:56, "Weijun Wang" > > wrote: >> >> Hi Mani >> >> Welcome to the OpenJDK! >> >> On 06/21/2012 02:31 PM, Mani Sarkar wrote: >> >> Hi >> >> 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 >> >> -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 >> >> 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 >> >> make >> ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 >> jdk_util >> >> 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 >> /home/openjdk/jtreg. >> >> It's OK to see a win32, those scripts are essentially the >> same across platforms. >> >> Good luck! >> >> -Max >> >> >> Regards, >> Mani >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/324668af/attachment.html From sadhak001 at gmail.com Thu Jun 21 11:39:07 2012 From: sadhak001 at gmail.com (Mani Sarkar) Date: Thu, 21 Jun 2012 19:39:07 +0100 Subject: JTRegs for OpenJDK In-Reply-To: <4FE366CB.1040209@oracle.com> References: <4FE2E1B6.8090609@oracle.com> <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> <4FE366CB.1040209@oracle.com> Message-ID: That's a great start, I find the idea interesting. +1 nested logs, clicking, etc On 21 Jun 2012 19:24, "Jonathan Gibbons" 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 > online. > > -- Jon > > > > On 06/21/2012 10:11 AM, Mani Sarkar wrote: > > Thanks Kelly for the response, I do understand its not a top prio > requirement. > > 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. > > Cheers, > Mani > On 21 Jun 2012 17:51, "Kelly O'Hair" 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. >> >> -kto >> >> 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. >> >> Mani >> On 21 Jun 2012 09:56, "Weijun Wang" wrote: >> >>> Hi Mani >>> >>> Welcome to the OpenJDK! >>> >>> On 06/21/2012 02:31 PM, Mani Sarkar wrote: >>> >>>> Hi >>>> >>>> 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 >>> >>> -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 >>> >>> 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 >>> >>> make ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 >>> jdk_util >>> >>> 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 /home/openjdk/jtreg. >>> >>> It's OK to see a win32, those scripts are essentially the same across >>> platforms. >>> >>> Good luck! >>> >>> -Max >>> >>> >>>> Regards, >>>> Mani >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/a8c291ef/attachment.html From jonathan.gibbons at oracle.com Thu Jun 21 12:00:16 2012 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 21 Jun 2012 12:00:16 -0700 Subject: JTRegs for OpenJDK In-Reply-To: References: <4FE2E1B6.8090609@oracle.com> <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> <4FE366CB.1040209@oracle.com> Message-ID: <4FE36F40.20803@oracle.com> 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. -- Jon 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" > 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 > online. > > -- Jon > > > > On 06/21/2012 10:11 AM, Mani Sarkar wrote: >> >> Thanks Kelly for the response, I do understand its not a top prio >> requirement. >> >> 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. >> >> Cheers, >> Mani >> >> On 21 Jun 2012 17:51, "Kelly O'Hair" > > 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. >> >> -kto >> >> 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. >>> >>> Mani >>> >>> On 21 Jun 2012 09:56, "Weijun Wang" >> > wrote: >>> >>> Hi Mani >>> >>> Welcome to the OpenJDK! >>> >>> On 06/21/2012 02:31 PM, Mani Sarkar wrote: >>> >>> Hi >>> >>> 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 >>> >>> -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 >>> >>> 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 >>> >>> make >>> ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 >>> jdk_util >>> >>> 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 >>> /home/openjdk/jtreg. >>> >>> It's OK to see a win32, those scripts are essentially >>> the same across platforms. >>> >>> Good luck! >>> >>> -Max >>> >>> >>> Regards, >>> Mani >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20120621/591093e2/attachment.html From weijun.wang at oracle.com Thu Jun 21 18:34:09 2012 From: weijun.wang at oracle.com (Weijun Wang) Date: Fri, 22 Jun 2012 09:34:09 +0800 Subject: JTRegs for OpenJDK In-Reply-To: <4FE36F40.20803@oracle.com> References: <4FE2E1B6.8090609@oracle.com> <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> <4FE366CB.1040209@oracle.com> <4FE36F40.20803@oracle.com> Message-ID: <4FE3CB91.2010104@oracle.com> A recursive view on the OpenJDK build output is useful because of the characteristics of the makefiles. However, for the makefile in test, it looks not necessary. Here, the output mainly includes the header part which is how jtreg is called and then it's the result for each test. The jtreg command has some very long lines and maybe we can break it short with \. Otherwise, it's still quite readable. Thanks Max On 06/22/2012 03:00 AM, Jonathan Gibbons wrote: > 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. > > -- Jon > > 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" > > 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 online. >> >> -- Jon >> >> >> >> On 06/21/2012 10:11 AM, Mani Sarkar wrote: >>> >>> Thanks Kelly for the response, I do understand its not a top prio >>> requirement. >>> >>> 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. >>> >>> Cheers, >>> Mani >>> >>> On 21 Jun 2012 17:51, "Kelly O'Hair" >> > 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. >>> >>> -kto >>> >>> 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. >>>> >>>> Mani >>>> >>>> On 21 Jun 2012 09:56, "Weijun Wang" >>> > wrote: >>>> >>>> Hi Mani >>>> >>>> Welcome to the OpenJDK! >>>> >>>> On 06/21/2012 02:31 PM, Mani Sarkar wrote: >>>> >>>> Hi >>>> >>>> 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 >>>> >>>> -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 >>>> >>>> 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 >>>> >>>> make >>>> ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 >>>> jdk_util >>>> >>>> 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 >>>> /home/openjdk/jtreg. >>>> >>>> It's OK to see a win32, those scripts are essentially >>>> the same across platforms. >>>> >>>> Good luck! >>>> >>>> -Max >>>> >>>> >>>> Regards, >>>> Mani >>>> >>> >> > From weijun.wang at oracle.com Thu Jun 21 18:34:25 2012 From: weijun.wang at oracle.com (Weijun Wang) Date: Fri, 22 Jun 2012 09:34:25 +0800 Subject: JTRegs for OpenJDK In-Reply-To: <4FE36F40.20803@oracle.com> References: <4FE2E1B6.8090609@oracle.com> <2FC7ABCD-73F8-438C-A6AB-C27FA3835023@oracle.com> <4FE366CB.1040209@oracle.com> <4FE36F40.20803@oracle.com> Message-ID: <4FE3CBA1.6050507@oracle.com> A recursive view on the OpenJDK build output is useful because of the characteristics of the makefiles. However, for the makefile in test, it looks not necessary. Here, the output mainly includes the header part which is how jtreg is called and then it's the result for each test. The jtreg command has some very long lines and maybe we can break it short with \. Otherwise, it's still quite readable. Thanks Max On 06/22/2012 03:00 AM, Jonathan Gibbons wrote: > 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. > > -- Jon > > 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" > > 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 online. >> >> -- Jon >> >> >> >> On 06/21/2012 10:11 AM, Mani Sarkar wrote: >>> >>> Thanks Kelly for the response, I do understand its not a top prio >>> requirement. >>> >>> 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. >>> >>> Cheers, >>> Mani >>> >>> On 21 Jun 2012 17:51, "Kelly O'Hair" >> > 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. >>> >>> -kto >>> >>> 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. >>>> >>>> Mani >>>> >>>> On 21 Jun 2012 09:56, "Weijun Wang" >>> > wrote: >>>> >>>> Hi Mani >>>> >>>> Welcome to the OpenJDK! >>>> >>>> On 06/21/2012 02:31 PM, Mani Sarkar wrote: >>>> >>>> Hi >>>> >>>> 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 >>>> >>>> -jdk:/home/openjdk/sources/jdk8_tl/jdk/test/../build/linux-amd64 >>>> >>>> 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 >>>> >>>> make >>>> ALT_OUTPUTDIR=/home/openjdk/sources/jdk8_tl/build/linux-amd64 >>>> jdk_util >>>> >>>> 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 >>>> /home/openjdk/jtreg. >>>> >>>> It's OK to see a win32, those scripts are essentially >>>> the same across platforms. >>>> >>>> Good luck! >>>> >>>> -Max >>>> >>>> >>>> Regards, >>>> Mani >>>> >>> >> >