6:31 p.m.
You don't think there is any benefit from testing with the serialized (opaque) format
now, and then switching to the xml version when its ready?
I'm just thinking about shaking out any problems with the other beans in
conf/profile-repository.xml and deploy/profileservice-jboss-beans.xml.bak sooner rather
than later.
----- "Scott Stark" <sstark(a)redhat.com> wrote:
Completion of the xml persistence file format work Emanuel is
looking
at.
Charles Crouch wrote:
Whats preventing us doing this now?
https://jira.jboss.org/jira/browse/JBAS-5994 Switch to repository
based ProfileService as the default
Thanks
Charles
----- "Dimitris Andreadis" <dandread(a)redhat.com> wrote:
Just a reminder that Nov/21st is the code freeze date for AS5. We need
to complete asap any
pending updates that are not blocked by some critical issue in order
to reduce the "moving
parts", as they are likely to introduce regression in the testsuites.
Non blocker/critical
JIRA will need to be moved, as well.
https://jira.jboss.org/jira/browse/JBAS-5597
https://jira.jboss.org/jira/secure/IssueNavigator.jspa?mode=hide&requ...
Thanks
/Dimitris
_______________________________________________
jboss-development mailing list jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
9:17 p.m.
New subject: 2 weeks to AS5 code freeze
There would be benefit. I'll do a full testsuite run locally with it
enabled to see how it looks before committing it.
Charles Crouch wrote:
You don't think there is any benefit from testing with the
serialized (opaque) format now, and then switching to the xml version when its ready?
I'm just thinking about shaking out any problems with the other beans in
conf/profile-repository.xml and deploy/profileservice-jboss-beans.xml.bak sooner rather
than later.
----- "Scott Stark" <sstark(a)redhat.com> wrote:
> Completion of the xml persistence file format work Emanuel is looking
> at.
>
>
10:23 p.m.
New subject: 2 weeks to AS5 code freeze
The immediate problem that shows up is that hot deployment is not
working, so the tests don't run because the minimal configuration
requires this in order to shutdown. Its failure to shutdown causes the
testsuite run to fail because the naming ports are still active when the
all configuration is started.
https://jira.jboss.org/jira/browse/JBAS-6190
Charles Crouch wrote:
You don't think there is any benefit from testing with the
serialized (opaque) format now, and then switching to the xml version when its ready?
I'm just thinking about shaking out any problems with the other beans in
conf/profile-repository.xml and deploy/profileservice-jboss-beans.xml.bak sooner rather
than later.
----- "Scott Stark" <sstark(a)redhat.com> wrote:
> Completion of the xml persistence file format work Emanuel is looking
> at.
>
>
1:42 a.m.
New subject: 2 weeks to AS5 code freeze
It was just that the HDScanner bean was being deployed differently based
on the profile service implementation. Now the HDScanner bean is
deployed as deploy/profileservice-hdscanner-jboss-beans.xml in every
profile independent of which profile service implementation is used.
Scott Stark wrote:
The immediate problem that shows up is that hot deployment is not
working, so the tests don't run because the minimal configuration
requires this in order to shutdown. Its failure to shutdown causes the
testsuite run to fail because the naming ports are still active when
the all configuration is started.
https://jira.jboss.org/jira/browse/JBAS-6190
9:21 a.m.
New subject: 2 weeks to AS5 code freeze
I think this latest run also present this problem of the minimal config not shutting
down.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
I've verified that locally using the 'build jboss-minimal-tests', although
another manual
test I did deploying/undeploying 'shutdown.sar' seemed to work.
Scott Stark wrote:
It was just that the HDScanner bean was being deployed differently
based
on the profile service implementation. Now the HDScanner bean is
deployed as deploy/profileservice-hdscanner-jboss-beans.xml in every
profile independent of which profile service implementation is used.
Scott Stark wrote:
> The immediate problem that shows up is that hot deployment is not
> working, so the tests don't run because the minimal configuration
> requires this in order to shutdown. Its failure to shutdown causes the
> testsuite run to fail because the naming ports are still active when
> the all configuration is started.
>
> https://jira.jboss.org/jira/browse/JBAS-6190
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
9:31 a.m.
New subject: 2 weeks to AS5 code freeze
With a slightly increased deploy-wait timeout it's passing. Maybe with the new setup
the
timing of the test changed?
Scott, couldn't you pick up a sorter name? ;-)
profileservice-hdscanner-jboss-beans.xml
Dimitris Andreadis wrote:
I think this latest run also present this problem of the minimal
config
not shutting down.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
I've verified that locally using the 'build jboss-minimal-tests',
although another manual test I did deploying/undeploying 'shutdown.sar'
seemed to work.
Scott Stark wrote:
> It was just that the HDScanner bean was being deployed differently
> based on the profile service implementation. Now the HDScanner bean is
> deployed as deploy/profileservice-hdscanner-jboss-beans.xml in every
> profile independent of which profile service implementation is used.
>
> Scott Stark wrote:
>> The immediate problem that shows up is that hot deployment is not
>> working, so the tests don't run because the minimal configuration
>> requires this in order to shutdown. Its failure to shutdown causes
>> the testsuite run to fail because the naming ports are still active
>> when the all configuration is started.
>>
>> https://jira.jboss.org/jira/browse/JBAS-6190
>>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
10:26 a.m.
New subject: 2 weeks to AS5 code freeze
It could just be hdscanner-jboss-beans.xml
Dimitris Andreadis wrote:
With a slightly increased deploy-wait timeout it's passing. Maybe
with
the new setup the timing of the test changed?
Scott, couldn't you pick up a sorter name? ;-)
profileservice-hdscanner-jboss-beans.xml
12:45 p.m.
New subject: 2 weeks to AS5 code freeze
The full run with the profileservice with the repository as the default
ended up with 121 issues. A lot of these were the profileservice tests,
so something is conflicting with the setup that should be an easy fix.
Number of tests run: 3589
--------------------------------------------
Successful tests: 3468
Errors: 114
Failures: 7
--------------------------------------------
Dimitris Andreadis wrote:
With a slightly increased deploy-wait timeout it's passing. Maybe
with
the new setup the timing of the test changed?
Scott, couldn't you pick up a sorter name? ;-)
profileservice-hdscanner-jboss-beans.xml
Dimitris Andreadis wrote:
> I think this latest run also present this problem of the minimal
> config not shutting down.
>
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
>
> I've verified that locally using the 'build jboss-minimal-tests',
> although another manual test I did deploying/undeploying
> 'shutdown.sar' seemed to work.
>
> Scott Stark wrote:
>> It was just that the HDScanner bean was being deployed differently
>> based on the profile service implementation. Now the HDScanner bean
>> is deployed as deploy/profileservice-hdscanner-jboss-beans.xml in
>> every profile independent of which profile service implementation is
>> used.
>>
>> Scott Stark wrote:
>>> The immediate problem that shows up is that hot deployment is not
>>> working, so the tests don't run because the minimal configuration
>>> requires this in order to shutdown. Its failure to shutdown causes
>>> the testsuite run to fail because the naming ports are still active
>>> when the all configuration is started.
>>>
>>> https://jira.jboss.org/jira/browse/JBAS-6190
>>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
4:35 p.m.
New subject: 2 weeks to AS5 code freeze
With the fix to the profileservice config problem fixed, the errors look
to be the same as in the nightly runs:
Number of tests run: 3394
--------------------------------------------
Successful tests: 3382
Errors: 5
Failures: 7
--------------------------------------------
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
has 3391 tests run, 11 failures.
I'll look to commit this change tonight.
Scott Stark wrote:
The full run with the profileservice with the repository as the
default ended up with 121 issues. A lot of these were the
profileservice tests, so something is conflicting with the setup that
should be an easy fix.
Number of tests run: 3589
--------------------------------------------
Successful tests: 3468
Errors: 114
Failures: 7
--------------------------------------------
Dimitris Andreadis wrote:
> With a slightly increased deploy-wait timeout it's passing. Maybe
> with the new setup the timing of the test changed?
>
> Scott, couldn't you pick up a sorter name? ;-)
>
> profileservice-hdscanner-jboss-beans.xml
>
3:10 p.m.
New subject: 2 weeks to AS5 code freeze
It's been renamed.
Scott Stark wrote:
It could just be hdscanner-jboss-beans.xml
Dimitris Andreadis wrote:
> With a slightly increased deploy-wait timeout it's passing. Maybe with
> the new setup the timing of the test changed?
>
> Scott, couldn't you pick up a sorter name? ;-)
>
> profileservice-hdscanner-jboss-beans.xml
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
4:02 p.m.
New subject: Bug in ProfileServiceBootstrap
Hello,
sorry I'm completely new to JBoss, so I don't know where to post a
possible bug.
In the code I discovered the following:
ProfileServiceBootstrap.start(Server)
if(profileService == null)
throw new IllegalStateException("The ProfileService has not
been injected");
log.debug("Using ProfileService: " + profileService);
if(profileService == null) <<<<< I think this should be the
mainDeployer
throw new IllegalStateException("The MainDeployer has not been
injected");
Where can I post this (or is this here the right place)?
Cheers
Richard
PS: Is there a list for beginning JBoss AS developers (developing the
JBoss) this here seems quite for pros only.
5:15 p.m.
New subject: Bug in ProfileServiceBootstrap
I'll check this tomorrow.
Sent from my iPhone
On Nov 18, 2008, at 23:02, Richard Krutisch <richard.krutisch(a)gmx.net>
wrote:
Hello,
sorry I'm completely new to JBoss, so I don't know where to post a
possible bug.
In the code I discovered the following:
ProfileServiceBootstrap.start(Server)
if(profileService == null)
throw new IllegalStateException("The ProfileService has not
been injected");
log.debug("Using ProfileService: " + profileService);
if(profileService == null) <<<<< I think this should be the
mainDeployer
throw new IllegalStateException("The MainDeployer has not
been injected");
Where can I post this (or is this here the right place)?
Cheers
Richard
PS: Is there a list for beginning JBoss AS developers (developing
the JBoss) this here seems quite for pros only.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
6:24 p.m.
New subject: Bug in ProfileServiceBootstrap
Normally you would report issues in the JBAS jira:
https://jira.jboss.org/jira/browse/JBAS
but I have corrected this as you are obviously correct.
Thanks
Richard Krutisch wrote:
Hello,
sorry I'm completely new to JBoss, so I don't know where to post a
possible bug.
In the code I discovered the following:
ProfileServiceBootstrap.start(Server)
if(profileService == null)
throw new IllegalStateException("The ProfileService has not
been injected");
log.debug("Using ProfileService: " + profileService);
if(profileService == null) <<<<< I think this should be the
mainDeployer
throw new IllegalStateException("The MainDeployer has not been
injected");
Where can I post this (or is this here the right place)?
Cheers
Richard
PS: Is there a list for beginning JBoss AS developers (developing the
JBoss) this here seems quite for pros only.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5656
days inactive
5664
days old
jboss-development@lists.jboss.org
12 comments
5 participants
participants (5)
-
Ales Justin -
Charles Crouch -
Dimitris Andreadis -
Richard Krutisch -
Scott Stark