Nabble - OpenJDK Quality Discussion

Re: Access to your testsuite

2009-05-14T08:07:56Z

Gayathri Soundar wrote:
> Hi ,
> Can you please let me know from and how I can access your unit and
> regression test suite?

Hi,

please take a look at http://openjdk.java.net/jtreg/ .

cheers,
dalibor topic
--
*******************************************************************
Dalibor Topic Tel: (+49 40) 23 646 738
Java F/OSS Ambassador AIM: robiladonaim
Sun Microsystems GmbH Mobile: (+49 177) 2664 192
Nagelsweg 55 http://openjdk.java.net
D-20097 Hamburg mailto:Dalibor.Topic@...
Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht München: HRB 161028
Geschäftsführer: Thomas Schröder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Häring

Access to your testsuite

2009-05-14T04:18:37Z

Hi ,
Can you please let me know from and how I can access your unit and regression test suite?

Thanks,
Gayathri

Re: futex_wait problem

2009-03-26T18:36:06Z

Hey, this is just to confirm that I figured that this is not java related issue, updates are found here:
http://forums.fedoraforum.org/showthread.php?p=1191574&posted=1#post1191574

if anybody have any idea or resolution please share it, thanks!

On Thu, Mar 26, 2009 at 11:58 PM, Amahdy <mrjava.javaman@...> wrote:

OK thanks for ur reply, I opened a thread and here is a link for future reference:
http://forums.fedoraforum.org/showthread.php?p=1191481

BUT, I have just a question, I don't know what's "jps" or "jstack" ... is it a java-based application? I can't make any java-based application to run including the java-cpl and the java-policy-tool ... I have removed all the OpenJDK stuff and reinstalled them without any result ... can u help me please?

On Thu, Mar 26, 2009 at 11:23 PM, Florian Weimer <fw@...> wrote:
* Amahdy:

> I'm running fedora 10, with OpenJDK 1.6, and developing with NetBeans 6.5,
> lately I got a problem with any java application, I can't run any java-based
> application and always receiving a "futex_wait" hanging on any java based
> application, I mean, when I run a java-based application I get a hanging
> interface and when i take a look at running process I see the java process
> is hanging in "futex_wait" FOR EVER and the application won't run ... I mean
> here by java-based application a application developed by me maybe, or any
> other like "netbeans" itself I cant run it, neither "logfactor5", nor any
> java application or applet for example ...

You should probably ask on a Fedora mailing list. You should also use
jps and jstack to get a stack dump from the stuck process.

Re: futex_wait problem

2009-03-26T14:58:51Z

OK thanks for ur reply, I opened a thread and here is a link for future reference:
http://forums.fedoraforum.org/showthread.php?p=1191481

BUT, I have just a question, I don't know what's "jps" or "jstack" ... is it a java-based application? I can't make any java-based application to run including the java-cpl and the java-policy-tool ... I have removed all the OpenJDK stuff and reinstalled them without any result ... can u help me please?

On Thu, Mar 26, 2009 at 11:23 PM, Florian Weimer <fw@...> wrote:

* Amahdy:

> I'm running fedora 10, with OpenJDK 1.6, and developing with NetBeans 6.5,
> lately I got a problem with any java application, I can't run any java-based
> application and always receiving a "futex_wait" hanging on any java based
> application, I mean, when I run a java-based application I get a hanging
> interface and when i take a look at running process I see the java process
> is hanging in "futex_wait" FOR EVER and the application won't run ... I mean
> here by java-based application a application developed by me maybe, or any
> other like "netbeans" itself I cant run it, neither "logfactor5", nor any
> java application or applet for example ...

You should probably ask on a Fedora mailing list. You should also use
jps and jstack to get a stack dump from the stuck process.

Re: futex_wait problem

2009-03-26T14:23:10Z

* Amahdy:

> I'm running fedora 10, with OpenJDK 1.6, and developing with NetBeans 6.5,
> lately I got a problem with any java application, I can't run any java-based
> application and always receiving a "futex_wait" hanging on any java based
> application, I mean, when I run a java-based application I get a hanging
> interface and when i take a look at running process I see the java process
> is hanging in "futex_wait" FOR EVER and the application won't run ... I mean
> here by java-based application a application developed by me maybe, or any
> other like "netbeans" itself I cant run it, neither "logfactor5", nor any
> java application or applet for example ...

You should probably ask on a Fedora mailing list. You should also use
jps and jstack to get a stack dump from the stuck process.

futex_wait problem

2009-03-26T12:34:10Z

Hey there!
I'm running fedora 10, with OpenJDK 1.6, and developing with NetBeans 6.5, lately I got a problem with any java application, I can't run any java-based application and always receiving a "futex_wait" hanging on any java based application, I mean, when I run a java-based application I get a hanging interface and when i take a look at running process I see the java process is hanging in "futex_wait" FOR EVER and the application won't run ... I mean here by java-based application a application developed by me maybe, or any other like "netbeans" itself I cant run it, neither "logfactor5", nor any java application or applet for example ...

what I did lately in the system before that appears was installaing "fedora eclipse", and updated the system, I removed all the eclipse stuff and the problem still there, please help me to fix it and/or fix the bug ... Thanks!

ping (Was: Re: mailing list for test results)

2009-03-02T08:41:58Z

Dalibor Topic wrote:

> Hi everyone,
>
> as the uptake of OpenJDK in GNU/Linux distributions, and in other
> exciting places grows, there is an increasing need to have a
> central place to post test results from jtreg and other test suite
> runs, and have them archived for later mining, comparison, etc.
>
> Other similarly scoped free software projects like the GNU compiler
> collection use mailing lists for that purpose, in gcc's case that's
> 'gcc-regression' - a moderate volume list where regression results
> for the GCC compilers are posted.
>
> It would be great if the Quality Group could provide a similar
> regression test results mailing list, where people (automatically)
> building OpenJDK 6/7 and running jtreg could post their results to.
>
> For the background of this request, please see the thread at the
> distro-pkg-dev mailing list, starting at
> http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2009-February/004925.html
>
> cheers,
> dalibor topic

--
*******************************************************************
Dalibor Topic Tel: (+49 40) 23 646 738
Java F/OSS Ambassador AIM: robiladonaim
Sun Microsystems GmbH Mobile: (+49 177) 2664 192
Nagelsweg 55 http://openjdk.java.net
D-20097 Hamburg mailto:Dalibor.Topic@...
Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht München: HRB 161028
Geschäftsführer: Thomas Schröder, Wolfgang Engels, Dr. Roland Bömer
Vorsitzender des Aufsichtsrates: Martin Häring

mailing list for test results

2009-02-27T04:52:34Z

Hi everyone,

as the uptake of OpenJDK in GNU/Linux distributions, and in other
exciting places grows, there is an increasing need to have a
central place to post test results from jtreg and other test suite
runs, and have them archived for later mining, comparison, etc.

Other similarly scoped free software projects like the GNU compiler
collection use mailing lists for that purpose, in gcc's case that's
'gcc-regression' - a moderate volume list where regression results
for the GCC compilers are posted.

It would be great if the Quality Group could provide a similar
regression test results mailing list, where people (automatically)
building OpenJDK 6/7 and running jtreg could post their results to.

For the background of this request, please see the thread at the
distro-pkg-dev mailing list, starting at
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2009-February/004925.html

cheers,
dalibor topic
--
*******************************************************************
Dalibor Topic Tel: (+49 40) 23 646 738
Java F/OSS Ambassador AIM: robiladonaim
Sun Microsystems GmbH Mobile: (+49 177) 2664 192
Nagelsweg 55 http://openjdk.java.net
D-20097 Hamburg mailto:Dalibor.Topic@...
Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht München: HRB 161028
Geschäftsführer: Thomas Schröder, Wolfgang Engels, Dr. Roland Bömer
Vorsitzender des Aufsichtsrates: Martin Häring

FREE Online Test at www.yfrindia.com

2008-09-03T12:15:51Z

http://www.yfrindia.com/
Take FREE online TEST, read FREE articles, download FREE presentation, use FREE source code, useful links, competition updates, free ONLINE TEST TESTS,
http://www.yfrindia.com/resources/Tests
free APTITUDE TEST, English Test, Computer Test, Mechanical Test, Electronics Test, Electrical Test, GATE preparation, CAT preparation, Job preparation, resume.
http://www.yfrindia.com/

FREE Online Test at www.yfrindia.com

2008-09-03T12:15:49Z

Re: jtreg testing integrated

2008-05-22T08:12:07Z

[+quality-discuss, jdk7-gk]

On Thu, May 22, 2008 at 7:27 AM, Mark Wielaard <mark@...> wrote:

> Hi Martin,
>
> On Tue, 2008-05-20 at 06:00 -0700, Martin Buchholz wrote:
>> On Tue, May 20, 2008 at 2:32 AM, Mark Wielaard <mark@...> wrote:
>> >> I like a policy of "Read my lips; no new test failures" but OpenJDK
>> >> is not quite there; we get test failure creep when changes in
>> >> one component break another component's tests.
>> >
>> > Yes, that would be idea. At least for openjdk6/icedtea we seem to be
>> > pretty close actually. It will be more challenging for openjdk7. I
>> > haven't quite figured out all the dynamics around "workspace
>> > integration". But I assume we can get the master tree to zero fail and
>> > then demand that any integration cycle doesn't introduce regressions.
>>
>> There are too many tests to require team integrators to run
>> them all on each integration cycle.
>
> I am not sure. It does take about 3 hours to run all the included tests
> (and I assume that when we add more tests or integrate things like mauve
> it will rise).

Not all the regression tests are open source yet, and not all the
test suites available are open source (and some are likely to be
permanently encumbered). And we should be adding more
static analysis tools to the testing process.

It sure would be nice to run all tests with -server and -client,
and with different GCs, and on 32 and 64-bit platforms,
with Java assertions enabled and disabled,
with C++ assertions enabled and disabled.

Soon a "full" testing cycle looks like it might take a week.

But I do hope people, not just integrators, will run them
> regularly. Especially when they are working on/integrating larger
> patches. And we can always fall back on autobuilders so we have a full
> report at least soon after something bad happens so there is some chance
> to revert a change relatively quickly.

Much of the world works on this model -
commit to trunk, wait for trouble, revert.
It's certainly much cheaper, and gets feedback quicker,
but creates fear among developers ("Notoriously careless
developer X just did a commit. I think I'll wait for a week
before pulling")

>> For a few years I've advocated
>> adding another level to the tree of workspaces. My model is to
>> rename the current MASTER workspace to PURGATORY, and
>> add a "golden MASTER".
>> The idea is that once a week or so all tests are run exhaustively,
>> and when it is confirmed that there are no new test failures,
>> the tested code from PURGATORY is promoted to MASTER.
>
> This is fascinating. Intuitively I would call for less levels instead of
> more because that makes issues show up earlier. It is one of the things
> I haven't really wrapped my head around. The proliferation of separate
> branches/workspaces. One main master tree where all work goes into by
> default and only have separate (ad hoc) branches/workspaces for larger
> work items that might be destabilizing seems an easier model to work
> with.

It's certainly more work for the integrators. But for the developers
my model is simple and comfortable. Youir integrator will give you
a workspace to commit changes to.
Commit there whenever you feel like. Go on to the next coding task.
Your changes will take a while to percolate into MASTER,
but what do you care?
When you sync, you pull in changes from MASTER, which are
*guaranteed* to not break any of your tests. If you want specific
changes quickly, pull from PURGATORY or a less-tested team
workspace.

If you have a project where you need to share your work
with other developers immediately,
no problem - just create a project-specific shared workspace
that all project team members can commit to directly.
Decide on a level of testing the team is comfortable with -
including none at all.

Developers in my model are more productive partly because
they don't have to be afraid of breaking other developers.
They can do enough testing for 95% confidence
(which for many changes might mean no testing at all)
then commit. The system will push back buggy changes
automatically.

Too many times I've suffered because tests in library land
have been broken by changes in hotspot. Nevertheless,
the JDK MASTER is remarkably stable for a project with so
many developers, largely because of the gradual integration
process, with changes going into MASTER only after being
tested by integrators. JDK developers don't go around chatting
about "build weather" - is the build broken today? AGAIN?

This development model doesn't work as well for most
open source projects, because they have fewer, smarter, and more
dedicated developers, so there is less need.
Also, it's hard to find good integrators. Most people (like myself)
end up doing it as a part-time job. But just like source code
control systems have gotten sexy, perhaps someday
"code integration and testing systems" will become sexy,
and everyone will want to write one.

Martin