[Design of JBoss internal QA (Test Suite)] - Server-side Testsuite Logging
by rachmatowicz＠jboss.com
Dear All
We have run into problems again with OOMEs appearing in the AS server logs during the running of the testsuite. One problem with debuggging such problems is that the only correspondence between the client side test log and the server side log is the time at which debug statements were written, making it possible but difficult to use the server side logs for debugging.
I would like to propose adding steps to the constructor (resp. destructor) of JBossTestCase to write information concerning the current test suite/test case to the server log:
- an easily identifiable banner line containing the package-qualified name of the test case
- the amount of available heap space before the test (resp after the test)
This would make the server side logs easier to read for people trying to debug client side failures and errors.
This could be achieved by modifying the constructor and destructor of JBossTestCase to make calls to appropriate MBeans (MemoryMXMBean, Log4J MBean) to get the available memory, as well as write to the server log itself.
Any comments as to whether this is adviseable or not?
The feature could be set up as a debugging feature, so that it was not active by default,
but given that it would only be used with the testsuite, this may not lead to a great saving.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042006#4042006
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042006
16 years, 5 months
[Design of JBoss Build System] - Re: Snapshots
by pgier
"pgier" wrote : "adrian(a)jboss.org" wrote :
| |
| | But I also got an error about not configuring the repository.jboss.com
| |
| | I thought the idea was that the new snapshots don't get updated there?
| |
| | | [INFO] ------------------------------------------------------------------------
| | | [ERROR] BUILD ERROR
| | | [INFO] ------------------------------------------------------------------------
| | | [INFO] One or more required plugin parameters are invalid/missing for 'jboss-deploy:jboss-deploy'
| | |
| | | [0] inside the definition for plugin: 'jboss-deploy-maven-plugin'specify the following:
| | |
| | | <configuration>
| | | ...
| | | <jbossDeployRoot>VALUE</jbossDeployRoot>
| | | </configuration>
| | |
| | | -OR-
| | |
| | | on the command line, specify: '-Djboss.repository.root=VALUE'
| | |
|
| These messages are coming from the jboss-deploy-maven plugin. By default jboss-test will deploy to both the maven repository, and the non-maven (jboss build) repository.
|
| The maven snapshot deployment seemed to work ok for you. The error message was letting you know that if you want to deploy to the non-maven repository you will have to set the location of where to deploy the stuff to. I'll update the wiki and the error messages to make this less confusing.
|
| The wagon version is just the plugin that let's deployment happen over webdav. You can ignore that.
Just thinking some more about this issue. Maybe the plugin can prompt the user to either ignore the non-jboss deployment, or specify a deployment directory if it's not already set.
Would that be helpful?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041997#4041997
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041997
16 years, 5 months
[Design of JBoss Build System] - Re: Snapshots
by pgier
"adrian(a)jboss.org" wrote : Also I'd prefer to do a proper release, but this page is useless for undertanding this.
| http://wiki.jboss.org/wiki/Wiki.jsp?page=Maven
|
| We need a "repository deploy" procedure, which should be a checklist,
| including manual checks like:
|
| * the version policy (how do you decide what the next version is)
| * move the pom.xml onto the next release/snapshot when finished?
| * tagging (how the maven version relates to SVN tags)
| * a release cannot depend on snapshots (how to resolve when it does)
| * all tests must pass (QA approved release?).
| * all JIRA issues should be closed
| * JIRA needs updating to move along the released project
| * Notifying product support about the new release (where relevant)
| * Agreement from project lead
| * etc.
|
| The current page does not even describe what is automated.
|
| Ideally this should be a simple page with links to the details.
There is this page:
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseProcess
Which you can get to from the main maven page under the heading "Releasing software with maven". Maybe this link should be more prominent?
But it is missing some of the things that you described above. I will add the above info this week.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041996#4041996
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041996
16 years, 5 months
[Design of JBoss Build System] - Re: Snapshots
by pgier
"adrian(a)jboss.org" wrote :
|
| But I also got an error about not configuring the repository.jboss.com
|
| I thought the idea was that the new snapshots don't get updated there?
|
| | [INFO] ------------------------------------------------------------------------
| | [ERROR] BUILD ERROR
| | [INFO] ------------------------------------------------------------------------
| | [INFO] One or more required plugin parameters are invalid/missing for 'jboss-deploy:jboss-deploy'
| |
| | [0] inside the definition for plugin: 'jboss-deploy-maven-plugin'specify the following:
| |
| | <configuration>
| | ...
| | <jbossDeployRoot>VALUE</jbossDeployRoot>
| | </configuration>
| |
| | -OR-
| |
| | on the command line, specify: '-Djboss.repository.root=VALUE'
| |
These messages are coming from the jboss-deploy-maven plugin. By default jboss-test will deploy to both the maven repository, and the non-maven (jboss build) repository.
The maven snapshot deployment seemed to work ok for you. The error message was letting you know that if you want to deploy to the non-maven repository you will have to set the location of where to deploy the stuff to. I'll update the wiki and the error messages to make this less confusing.
The wagon version is just the plugin that let's deployment happen over webdav. You can ignore that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041995#4041995
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041995
16 years, 5 months