[JBoss JIRA] (ARQ-1841) Spacelift can not deal with background process invocation
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1841?page=com.atlassian.jira.plugin.s... ]
Karel Piwko commented on ARQ-1841:
----------------------------------
[~smikloso] thinking about this problem, if you know this is happening, you might want not to call await() and set process to run as daemon. This should make the behavior the same as Runtime#exec(String)
> Spacelift can not deal with background process invocation
> ---------------------------------------------------------
>
> Key: ARQ-1841
> URL: https://issues.jboss.org/browse/ARQ-1841
> Project: Arquillian
> Issue Type: Bug
> Components: Extension - Spacelift
> Affects Versions: spacelift_1.0.0.Alpha2
> Reporter: Stefan Miklosovic
>
> Let's have this simple script:
> {code:title=run_agent_bg.sh|borderStyle=solid}
> #!/bin/sh
> curpath=`dirname $0`
> nohup ${curpath}/run_agent.sh $@ > /dev/null & 2>&1
> {code}
> I execute it like this:
> {code:title=App.java|borderStyle=solid}
> public class App {
> public static void main(String[] args) throws IOException {
> Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory());
> System.out.println("before");
> Tasks.prepare(CommandTool.class)
> .programName("/bin/bash")
> .parameters("-c", "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh")
> .execute().await();
>
> System.out.println("after");
> }
> }
> {code}
> So it effectively does this:
> {code}
> /bin/bash -c "/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh"
> {code}
> However it never reaches "after" output, that process in the script is started but Spacelift does not send it to the background and it still waits untill it is finished which never happen.
> Executing that script directly like following does the job:
> {code:title=App.java|borderStyle=solid}
> public class App {
> public static void main(String[] args) throws IOException {
> Tasks.setDefaultExecutionServiceFactory(new DefaultExecutionServiceFactory());
> System.out.println("before");
> Runtime.getRuntime().exec("/tmp/ngrinder-agent/ngrinder-agent/run_agent_bg.sh");
>
> System.out.println("after");
> }
> }
> {code}
> Started process survives JVM termination.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ARQGRA-468) Cannot use relative @Location when using "standalone" JUnit integration
by Christoffer Bromberg (JIRA)
Christoffer Bromberg created ARQGRA-468:
-------------------------------------------
Summary: Cannot use relative @Location when using "standalone" JUnit integration
Key: ARQGRA-468
URL: https://issues.jboss.org/browse/ARQGRA-468
Project: Arquillian Graphene
Issue Type: Bug
Components: configuration
Affects Versions: 2.1.0.Alpha2
Reporter: Christoffer Bromberg
Priority: Minor
As per https://issues.jboss.org/browse/ARQGRA-374 one can use the arquillian.xml to specify a "contextRoot" for page objects that use a relative URL.
This feature does not work if you use the "Standalone Mode" as described here: https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options
After I switched to the "container" dependency it works as expected.
I don't use the deployment and container management feature of Arquillian and still the "container" dependency works without any hassle. So either the
{code}
<!-- Arquillian JUnit Standalone -->
<dependency>
<groupId>org.jboss.arquillian.junit</groupId>
<artifactId>arquillian-junit-standalone</artifactId>
<scope>test</scope>
</dependency>
{code}
dependency should also include the correct classes (e.g. URLResourceProvider) or maybe the "Standalone" integration option is not (or no longer) needed.
So the workaround for me was to use the arquillian-junit-container dependency.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ARQ-1919) Android SDK with no images fails while testing on physical device
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1919?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1919.
----------------------------------
> Android SDK with no images fails while testing on physical device
> -----------------------------------------------------------------
>
> Key: ARQ-1919
> URL: https://issues.jboss.org/browse/ARQ-1919
> Project: Arquillian
> Issue Type: Bug
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha6
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Fix For: droidium_1.0.0.Final
>
>
> When you want to test on a physical device, there is not any need to have system images installed. This issue is rarely hit in practice, however when using Droidium in CI environment, testing on physical device and not requiring system images to be even installed is major performance improvement.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years