[
https://issues.apache.org/jira/browse/SLING-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3167.
-
Resolution: Fixed
Job Logging
---
Key: SLING-3167
[
https://issues.apache.org/jira/browse/SLING-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796487#comment-13796487
]
Stefan Egli commented on SLING-3174:
[~rombert], are you referring to adding actions
[
https://issues.apache.org/jira/browse/SLING-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3172.
-
Resolution: Fixed
I've dropped the name from the api for now, internally we use a uuid
[
https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796522#comment-13796522
]
Carsten Ziegeler commented on SLING-3169:
-
Thanks for the feedback
[
https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-3169:
Summary: Job state and related enumerations (was: Naming of Job related
enumerations)
Felix Meschberger created SLING-3179:
Summary: Implement solution to the Authentication Handler
Credential Validation Problem
Key: SLING-3179
URL: https://issues.apache.org/jira/browse/SLING-3179
[
https://issues.apache.org/jira/browse/SLING-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796529#comment-13796529
]
Felix Meschberger commented on SLING-2762:
--
Linking to the generic issue
[
https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796541#comment-13796541
]
Stefan Seifert commented on SLING-3169:
---
good solution for the ResultBuilder
[
https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796544#comment-13796544
]
Carsten Ziegeler commented on SLING-3169:
-
I could imagine the following enum:
[
https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796544#comment-13796544
]
Carsten Ziegeler edited comment on SLING-3169 at 10/16/13 8:24 AM:
[
https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796555#comment-13796555
]
Stefan Seifert commented on SLING-3169:
---
from a job admin GUI perspective if find
See https://builds.apache.org/job/sling-trunk-1.6/1978/changes
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.it/1978/
See https://builds.apache.org/job/sling-trunk-1.6/1979/changes
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.it/1979/
Hi,
the tests run fine on my machine - it seems that in your case the loop
waits forever to get 10 finished jobs in the history.
Do you see any exception in the log output?
Carsten
2013/10/15 Stefan Seifert sseif...@pro-vision.de
running win7 64bit, java 1.7.0_17, maven 3.0.5
any idea why
Robert Munteanu created SLING-3180:
--
Summary: Failed deployment should fail the build by default
Key: SLING-3180
URL: https://issues.apache.org/jira/browse/SLING-3180
Project: Sling
Issue
strange. i tried to isolate the problem by disabling all integration tests by
added junit @Ignore annotation to them.
the HistoryTest IT runs then fine.
i startet adding/removing more integration tests and sometims it succeeds,
sometimes not. perhaps a racing condition, or a cleanup issue of the
See https://builds.apache.org/job/sling-trunk-1.7/347/
--
[...truncated 298 lines...]
Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT
/repos/asf/!svn/vcc/default failed
at
[
https://issues.apache.org/jira/browse/SLING-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3170.
-
Resolution: Fixed
Ok, I'Ve added the remove event notification Thanks :)
Complex Job
Bertrand Delacretaz created SLING-3181:
--
Summary: Use the *IT.java name pattern to separate between unit
and integration tests
Key: SLING-3181
URL: https://issues.apache.org/jira/browse/SLING-3181
On Tue, Oct 15, 2013 at 10:30 PM, Stefan Seifert sseif...@pro-vision.de wrote:
...running win7 64bit, java 1.7.0_17, maven 3.0.5
any idea why this integration tests for sling event module fails when
building with mvn clean install?
i assume they run on other platforms?...
Yes, they work for
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/1981/
--
[...truncated 600 lines...]
T E S T S
---
Running org.apache.sling.launchpad.testing.TestAll
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/1981/
See https://builds.apache.org/job/sling-trunk-1.6/1981/changes
Changes:
[cziegeler] SLING-3170 : Complex Job Result Structures
[cziegeler] SLING-3170 : Complex Job Result Structures
--
[...truncated 36582 lines...]
Tests run: 2, Failures: 0, Errors: 0,
[
https://issues.apache.org/jira/browse/SLING-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796796#comment-13796796
]
Bertrand Delacretaz commented on SLING-2769:
The
See https://builds.apache.org/job/sling-trunk-1.7/348/changes
Yes, it seems to hang at that point as it doesn't get any jobs - I guess
the difference between windows and other machines is the order in which
test cases are executed. So it must be some previous test which does not
clean up correctly. Can you please find out from the logs which tests are
run
i was able to reproduce it in 2 of 3 tries with only two integration tests
activated:
- ClassloadingTest
- HistoryTest
running historytest or ClassloadingTest standalone worked.
running both (i assume ClassloadingTest did run first) did not work in 2 of 3
tries.
stefan
-Original
On Wed, Oct 16, 2013 at 5:55 PM, Stefan Seifert sseif...@pro-vision.de wrote:
i was able to reproduce it in 2 of 3 tries with only two integration tests
activated:
- ClassloadingTest
- HistoryTest
running historytest or ClassloadingTest standalone worked.
running both (i assume
[
https://issues.apache.org/jira/browse/SLING-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796860#comment-13796860
]
Julian Reschke commented on SLING-3175:
---
Here's a test that demonstrates the Java
[
https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3169.
-
Resolution: Fixed
I've added the above mentioned enum and implemented it
Job state and
I just added an additional ine to the Classloading test removing stale
jobs, but I don't think that's the problem :( Apart from that I can't see
anything spurious in the test
Carsten
2013/10/16 Robert Munteanu rob...@lmn.ro
On Wed, Oct 16, 2013 at 5:55 PM, Stefan Seifert
See https://builds.apache.org/job/sling-trunk-1.7/349/
--
[...truncated 286 lines...]
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
Carsten Ziegeler created SLING-3182:
---
Summary: Filter out invalid alias values
Key: SLING-3182
URL: https://issues.apache.org/jira/browse/SLING-3182
Project: Sling
Issue Type: Improvement
Carsten Ziegeler created SLING-3183:
---
Summary: Add a configuration flag to disable sling vanity path
handling
Key: SLING-3183
URL: https://issues.apache.org/jira/browse/SLING-3183
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3183.
-
Resolution: Fixed
Added the flag in rev 1532814
(And also moved metatype information
See https://builds.apache.org/job/sling-trunk-1.6/1982/changes
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/1982/
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/1982/
[
https://issues.apache.org/jira/browse/SLING-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3182.
-
Resolution: Fixed
Filter out invalid alias values
---
[
https://issues.apache.org/jira/browse/SLING-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796992#comment-13796992
]
Carsten Ziegeler commented on SLING-3182:
-
Invalid aliases are ignored. An alias
See https://builds.apache.org/job/sling-trunk-1.7/350/changes
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/1983/
See https://builds.apache.org/job/sling-trunk-1.6/1983/changes
Carsten Ziegeler created SLING-3184:
---
Summary: Create a job consumer to clean up the history
Key: SLING-3184
URL: https://issues.apache.org/jira/browse/SLING-3184
Project: Sling
Issue
46 matches
Mail list logo
