[JBoss JIRA] (JBTM-1409) Make the build less verbose - specifically the tests
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1409?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1409:
-------------------------------------
Will do, this was added to debug an issue I resolved just before Christmas. When redirected to file, if a deadlock occured the output was not flushed before the process had to be killed therefore there was no output to work from. I will reset this back to redirect to file now the deadlock is resolved.
> Make the build less verbose - specifically the tests
> ----------------------------------------------------
>
> Key: JBTM-1409
> URL: https://issues.jboss.org/browse/JBTM-1409
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Affects Versions: 5.0.0.M1
> Environment: Mac OS 10.7.5 with JDK 7 and 6.
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Priority: Minor
>
> Normally the build is fairly succinct around junit tests. However, when we hit jbossatx everything seems to become a lot more verbose than it needs to be. Consider making these tests silent (redirect error/output to a file, as happens with the other tests).
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running com.arjuna.ats.internal.jbossatx.jta.TestXAResourceRecordWrapperImpl
> Jan 1, 2013 9:32:58 PM com.arjuna.ats.arjuna.coordinator.TxControl <clinit>
> WARN: ARJUNA012130: Name of XA node not defined. Using Arjuna:54417
> Jan 1, 2013 9:32:59 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 54418
> Jan 1, 2013 9:32:59 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 54418
> Jan 1, 2013 9:32:59 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 54418 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> 1 == 1?
> 2 == 3?
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.536 sec
> Running com.arjuna.ats.jta.distributed.SimpleIsolatedServers
> Jan 1, 2013 9:32:59 PM com.arjuna.ats.jbossatx.jta.RecoveryManagerService create
> INFO: ARJUNA032010: JBossTS Recovery Service (tag: unknown) - JBoss Inc.
> Jan 1, 2013 9:32:59 PM com.arjuna.ats.internal.arjuna.recovery.RecActivatorLoader startRecoveryActivators
> INFO: ARJUNA012324: Start RecoveryActivators
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (JBTM-1410) Update README.md to include minimum build requirements
by Mark Little (JIRA)
Mark Little created JBTM-1410:
---------------------------------
Summary: Update README.md to include minimum build requirements
Key: JBTM-1410
URL: https://issues.jboss.org/browse/JBTM-1410
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System, Documentation
Affects Versions: 5.0.0.M1
Reporter: Mark Little
Assignee: Tom Jenkinson
Priority: Trivial
Narayana currently needs at least JDK 6 to build and eventually will probably need at least 7. There is no mention of this requirement in the README.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (JBTM-1409) Make the build less verbose - specifically the tests
by Mark Little (JIRA)
Mark Little created JBTM-1409:
---------------------------------
Summary: Make the build less verbose - specifically the tests
Key: JBTM-1409
URL: https://issues.jboss.org/browse/JBTM-1409
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System, Testing
Affects Versions: 5.0.0.M1
Environment: Mac OS 10.7.5 with JDK 7 and 6.
Reporter: Mark Little
Assignee: Tom Jenkinson
Priority: Minor
Normally the build is fairly succinct around junit tests. However, when we hit jbossatx everything seems to become a lot more verbose than it needs to be. Consider making these tests silent (redirect error/output to a file, as happens with the other tests).
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running com.arjuna.ats.internal.jbossatx.jta.TestXAResourceRecordWrapperImpl
Jan 1, 2013 9:32:58 PM com.arjuna.ats.arjuna.coordinator.TxControl <clinit>
WARN: ARJUNA012130: Name of XA node not defined. Using Arjuna:54417
Jan 1, 2013 9:32:59 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 54418
Jan 1, 2013 9:32:59 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 54418
Jan 1, 2013 9:32:59 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
INFO: ARJUNA012170: TransactionStatusManager started on port 54418 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
1 == 1?
2 == 3?
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.536 sec
Running com.arjuna.ats.jta.distributed.SimpleIsolatedServers
Jan 1, 2013 9:32:59 PM com.arjuna.ats.jbossatx.jta.RecoveryManagerService create
INFO: ARJUNA032010: JBossTS Recovery Service (tag: unknown) - JBoss Inc.
Jan 1, 2013 9:32:59 PM com.arjuna.ats.internal.arjuna.recovery.RecActivatorLoader startRecoveryActivators
INFO: ARJUNA012324: Start RecoveryActivators
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (JBTM-1405) idlj issue when building on Raspberry Pi
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1405?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1405:
-----------------------------------
This may be a JDK 7 issue, as it fails with the same error on Mac OS 10.7.5 using:
java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)
Here is it for completeness:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12:04.755s
[INFO] Finished at: Tue Jan 01 19:24:24 GMT 2013
[INFO] Final Memory: 48M/310M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test (surefire-idlj) on project jts: Execution surefire-idlj of goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test failed: java.lang.reflect.InvocationTargetException; nested exception is java.lang.reflect.InvocationTargetException: null: com/arjuna/ArjunaOTS/OTSAbstractRecordPOA: com.arjuna.ArjunaOTS.OTSAbstractRecordPOA -> [Help 1]
The current trunk builds fine on Mac OS 10.7.5 with:
java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-11M3909)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01-434, mixed mode)
> idlj issue when building on Raspberry Pi
> ----------------------------------------
>
> Key: JBTM-1405
> URL: https://issues.jboss.org/browse/JBTM-1405
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.3
> Environment: Raspberry Pi with stock distribution installed and openjdk 6.
> Reporter: Mark Little
> Assignee: Michael Musgrove
>
> Early in the build we get ...
> [INFO] Processing 3 grammar files to /home/pi/narayana/ArjunaJTS/idl/idlj/target/generated-sources/idl
> [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> And eventually this results in ...
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 4:03:24.556s
> [INFO] Finished at: Sat Dec 22 20:32:47 UTC 2012
> [INFO] Final Memory: 38M/105M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test (surefire-idlj) on project jts: Execution surefire-idlj of goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test failed: java.lang.reflect.InvocationTargetException; nested exception is java.lang.reflect.InvocationTargetException: null: org/omg/CosTransactions/ResourceOperations: org.omg.CosTransactions.ResourceOperations -> [Help 1]
> It would also be good if there was a build-time switch to disable using idlj. Building with the idlj option at the start (as mentioned in the README) would imply that this is the way to go and that building just using jts therefore only uses jacorb, but it seems that the jts rule builds with both orbs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months