Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weld709 #22

Closed
wants to merge 1 commit into from
Closed

Weld709 #22

wants to merge 1 commit into from

Conversation

mbogoevici
Copy link
Contributor

move tests from EARs to WARs and allow them to execute on JBAS trunk (with hierarchical deployments)

All EAR deployments converted to WARs. EARs are not necessary for testing right now, and ARQ-307 currently prevents those tests from running in JBoss AS when using a hierarchical deployment model.
@pmuir
Copy link
Contributor

pmuir commented Oct 10, 2010

Running with this patch rebased onto master I still see 4 errors in arquillian-tests

testCreateSFSB(org.jboss.weld.tests.enterprise.lifecycle.EnterpriseBeanLifecycleTest)      

testAfterTransactionCompletionObserver(org.jboss.weld.tests.event.observer.transactional.TransactionalObserversTest)

testAfterTransactionSuccessObserver(org.jboss.weld.tests.event.observer.transactional.TransactionalObserversTest)

testAfterTransactionFailureObserver(org.jboss.weld.tests.event.observer.transactional.TransactionalObserversTest)

@pmuir
Copy link
Contributor

pmuir commented Oct 10, 2010

What build of AS should I be running with?

@mbogoevici
Copy link
Contributor Author

I tried it against both the weld-integration-snapshot (either the last or the second-last revision, depending whether the patch for jboss-interceptor 2 is pulled into weld-core or not) or trunk - when I used cherry pick on top of the 1.1.0.Batch1 branch. Either case, it makes sense only when used against a branch of JBAS that uses hierarchical deployments (although that shouldn't make a difference, just that in a flat deployment scenario there's no benefit in doing this). Is it possible that we hit a case where those tests are failing for another cause - i.e do those tests succeed without applying the patch, or they don't run before applying the patch and now that they run we start seeing errors?

Let me know what your test config is and I'll try to reproduce this locally.

@pmuir
Copy link
Contributor

pmuir commented Oct 11, 2010

master of Weld, with patch rebased on top, running without hierarchical deployments. All tests were passing before I applied the patch (though if you altered any test groups or ignores then that would change things).

Will try to run against the penultimate rev of weld-integration-snapshot now.

@pmuir
Copy link
Contributor

pmuir commented Oct 11, 2010

Whatever I do I can't get these three tests to pass now:

Tests in error:
org.jboss.weld.tests.proxy.privateconstructor.ProxyConstructorTest
org.jboss.weld.tests.proxy.weld56.ProxyTest
org.jboss.weld.tests.proxy.weld56.ProxyTest

Steps:

  1. create a branch from master
  2. merge in weld709, weld-683 and jbas-weld-shared-update
  3. rebase against master
  4. run mvn install
  5. build jboss as from https://svn.jboss.org/repos/jbossas/branches/weld-snapshot-integration@108504
  6. run mvn clean verify -Dincontainer, pointing to the jboss as just built

@pmuir
Copy link
Contributor

pmuir commented Oct 11, 2010

Error is
DEPLOYMENTS IN ERROR:
Deployment "vfs:///Users/pmuir/workspace/weld/core/tests-arquillian/test.war_WeldBootstrapBean" is in error due to the following reason(s): org.jboss.weld.exceptions.UnproxyableResolutionException: WELD-001435 Normal scoped bean class org.jboss.weld.tests.proxy.weld56.Foo is not proxyable because it has no no-args constructor.,

@pmuir
Copy link
Contributor

pmuir commented Oct 11, 2010

I think the problem is likely I'm not pulling in enough things or sth. Can you write exactly what I need to do to get everything up to where it needs to be? E.g. do I need to pull in API updates too?

@pmuir
Copy link
Contributor

pmuir commented Oct 11, 2010

This is merged in.

I added a commit to exclude the proxy tests, and also a commit to exclode CDITCK-182.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants