[rhq-project/rhq] ae3d37: [1139735] More i-test fallout, oracle only
by Jay Shaughnessy
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: ae3d37af4896bea2af151e82d24a43147643b46a
https://github.com/rhq-project/rhq/commit/ae3d37af4896bea2af151e82d24a431...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-10-16 (Thu, 16 Oct 2014)
Changed paths:
M modules/core/domain/src/test/java/org/rhq/core/domain/test/SetupBean.java
M modules/enterprise/server/itests-2/src/test/java/org/rhq/enterprise/server/test/StrippedDownStartupBean.java
M modules/enterprise/server/itests-2/src/test/java/org/rhq/enterprise/server/test/StrippedDownStartupBeanPreparation.java
Log Message:
-----------
[1139735] More i-test fallout, oracle only
Unlike Postgres, where DDL changes can be transactional, Oracle executes
DDL (like adding a column) like autocommit=true. As such, it can't happen
within an existing Tx, which is what we have by default in out itest
setup beans (@PostConstruct). Change things to execute the DDL outside
of an existing Tx.
9 years, 7 months
[rhq-project/rhq] 9e915a: [BZ 1138688] - [windows] unable to log in to JON f...
by Jiri Kremser
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: 9e915a46d700b5a26777cdc82d83eb8f44b28760
https://github.com/rhq-project/rhq/commit/9e915a46d700b5a26777cdc82d83eb8...
Author: Jirka Kremser <jkremser(a)redhat.com>
Date: 2014-10-16 (Thu, 16 Oct 2014)
Changed paths:
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/CoreGUI.java
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/LoginView.java
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/UserSessionManager.java
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/util/rpc/TrackingRequestCallback.java
Log Message:
-----------
[BZ 1138688] - [windows] unable to log in to JON from FF - adding some magic to make the logging in working on newer browsers. Basically, some waiting (20ms) needed to be added before the redirect. Because of the fact that /login and /Coregui.html both uses the same gwt module some logic was added to distinguish between them and prevent the UI from rendering when user is still on the /login page.
9 years, 7 months
[rhq-project/rhq] 2292c1: [1151441] fix i-test failures (2)
by Jay Shaughnessy
Branch: refs/heads/release/jon3.3.x
Home: https://github.com/rhq-project/rhq
Commit: 2292c1b731cb5f26da113631b0413e0dec999dec
https://github.com/rhq-project/rhq/commit/2292c1b731cb5f26da113631b0413e0...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-10-15 (Wed, 15 Oct 2014)
Changed paths:
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/cloud/instance/ServerManagerBean.java
Log Message:
-----------
[1151441] fix i-test failures (2)
The i-tests actually set/restore rhq.server.high-availability.name sysprop
in the before/after methods. This allows testng to jump around and execute
tests in different classes, in different orders, while the server name
remains correct for each test. Update the server name caching
mechanism to reset the cache when sysprop changes are detected. I don't
think this has any production use case, but it's required for testing,
doesn't cost much, and still keeps the original fix for this BZ intact.
(cherry picked from commit 98fb73759744eff1bfe2d9fb0696aecf383c9f93)
Signed-off-by: Jay Shaughnessy <jshaughn(a)redhat.com>
9 years, 7 months
[rhq-project/rhq] 98fb73: [1151441] fix i-test failures (2)
by Jay Shaughnessy
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: 98fb73759744eff1bfe2d9fb0696aecf383c9f93
https://github.com/rhq-project/rhq/commit/98fb73759744eff1bfe2d9fb0696aec...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-10-15 (Wed, 15 Oct 2014)
Changed paths:
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/cloud/instance/ServerManagerBean.java
Log Message:
-----------
[1151441] fix i-test failures (2)
The i-tests actually set/restore rhq.server.high-availability.name sysprop
in the before/after methods. This allows testng to jump around and execute
tests in different classes, in different orders, while the server name
remains correct for each test. Update the server name caching
mechanism to reset the cache when sysprop changes are detected. I don't
think this has any production use case, but it's required for testing,
doesn't cost much, and still keeps the original fix for this BZ intact.
9 years, 7 months
[rhq-project/rhq] b2c08d: [1139735] fix test failures
by Jay Shaughnessy
Branch: refs/heads/release/jon3.3.x
Home: https://github.com/rhq-project/rhq
Commit: b2c08d57fbc1b185a4b50408fc3e19b103e0818f
https://github.com/rhq-project/rhq/commit/b2c08d57fbc1b185a4b50408fc3e19b...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-10-15 (Wed, 15 Oct 2014)
Changed paths:
M modules/common/cassandra-installer/src/main/java/org/rhq/storage/installer/StorageInstaller.java
M modules/common/cassandra-installer/src/test/java/org/rhq/storage/installer/StorageInstallerTest.java
Log Message:
-----------
[1139735] fix test failures
Now that the storage installer needs to contact the DB to version-stamp the
rhq_storage_node table, the cassandra installer upgrade tests failed, because
they support no DB infrastructure. To get around this added an installer
option to ignore the version stamping. These options are not user-visible,
and who knows, maybe someday support will have a reason to use it.
(cherry picked from commit 9ad8a28735c9c9f0a64288f6ffda6973feede014)
Signed-off-by: Jay Shaughnessy <jshaughn(a)redhat.com>
Commit: 83c92f8ef2d0850e2e91237ddf5354d548fa5f40
https://github.com/rhq-project/rhq/commit/83c92f8ef2d0850e2e91237ddf5354d...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2014-10-15 (Wed, 15 Oct 2014)
Changed paths:
M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/cloud/instance/ServerManagerBean.java
Log Message:
-----------
[1151441] fix i-test failures
We can't cache the server name in the static block because i-tests don't
set rhq.server.high-availbility.name that early in the setup. It was fine
for production. So, now lazily cache the server name at the time
of the first request for server name.
(cherry picked from commit c033e22ac766a573d14a5a54ff73dc7704147483)
Signed-off-by: Jay Shaughnessy <jshaughn(a)redhat.com>
Compare: https://github.com/rhq-project/rhq/compare/abaf46b22a19...83c92f8ef2d0
9 years, 7 months