[JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ]
Karel Piwko commented on ARQ-1583:
----------------------------------
Updated issue and bumped priority. The problem is that Droidium will not figure out emulator process is down and still waits for it's output.
> Emulator does not figure out process had died
> ---------------------------------------------
>
> Key: ARQ-1583
> URL: https://issues.…
[View More]jboss.org/browse/ARQ-1583
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Priority: Critical
>
> *When*:
> I let Droidium start emulator.
> *Given*:
> Emulator command fails, for instance when DISPLAY is not set.
> *Then*:
> Droidium waits up to emulator start time, then fails.
> *Expected*:
> Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong.
--
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
[View Less]
11 years, 4 months
[JBoss JIRA] (ARQ-1583) Emulator does not figure out that DISPLAY is not available
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ]
Karel Piwko updated ARQ-1583:
-----------------------------
Description:
*When*:
I let Droidium start emulator.
*Given*:
DISPLAY is not set.
*Then*:
Droidium waits up to emulator start time, then fails.
*Expected*:
Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong.
was:
*When*:
I …
[View More]let Droidium start emulator.
*Given*:
DISPLAY is not set.
*Then*:
Droidium waits up to emulator start time.
*Expected*:
Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong.
> Emulator does not figure out that DISPLAY is not available
> ----------------------------------------------------------
>
> Key: ARQ-1583
> URL: https://issues.jboss.org/browse/ARQ-1583
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
>
> *When*:
> I let Droidium start emulator.
> *Given*:
> DISPLAY is not set.
> *Then*:
> Droidium waits up to emulator start time, then fails.
> *Expected*:
> Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong.
--
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
[View Less]
11 years, 4 months
[JBoss JIRA] (ARQ-1583) Emulator does not figure out that DISPLAY is not available
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1583:
--------------------------------
Summary: Emulator does not figure out that DISPLAY is not available
Key: ARQ-1583
URL: https://issues.jboss.org/browse/ARQ-1583
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Droidium
Affects Versions: droidium_1.0.0.Alpha2
Reporter: Karel Piwko
*When*:
I let …
[View More]Droidium start emulator.
*Given*:
DISPLAY is not set.
*Then*:
Droidium waits up to emulator start time.
*Expected*:
Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong.
--
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
[View Less]
11 years, 4 months
[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1582?page=com.atlassian.jira.plugin.s... ]
Karel Piwko commented on ARQ-1582:
----------------------------------
One more note, keystore and androidDebugKey should be read from ANDROID_SDK_HOME as well.
> Honor ANDROID_SDK_HOME, deprecate generatedAvdPath
> --------------------------------------------------
>
> Key: ARQ-1582
> URL: https://issues.jboss.org/browse/ARQ-1582
> …
[View More]Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
>
> ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME.
> However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs.
> Droidium should be able to:
> * pass androidSdkHome in arquillian.xml with default = user.home
> * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd
> Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself.
--
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
[View Less]
11 years, 4 months
[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1582?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1582:
--------------------------------------
Assignee: Stefan Miklosovic
> Honor ANDROID_SDK_HOME, deprecate generatedAvdPath
> --------------------------------------------------
>
> Key: ARQ-1582
> URL: https://issues.jboss.org/browse/ARQ-1582
> Project: Arquillian
> Issue Type: Feature Request
&…
[View More]gt; Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> ANDROID_SDK_HOME represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME.
> However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs.
> Droidium should be able to:
> * pass androidSdkHome in arquillian.xml with default = user.home
> * honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd
> Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself.
--
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
[View Less]
11 years, 4 months
[JBoss JIRA] (ARQ-1582) Honor ANDROID_SDK_HOME, deprecate generatedAvdPath
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1582:
--------------------------------
Summary: Honor ANDROID_SDK_HOME, deprecate generatedAvdPath
Key: ARQ-1582
URL: https://issues.jboss.org/browse/ARQ-1582
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Droidium
Affects Versions: droidium_1.0.0.Alpha2
Reporter: Karel Piwko
ANDROID_SDK_HOME …
[View More]represents a top level directory that is used to store metadata of AVDs. By default, this directory equals $HOME.
However, various plugins and tools - such as Jenkins Android Plugin, allow to change ANDROID_SDK_HOME to better isolate jobs.
Droidium should be able to:
* pass androidSdkHome in arquillian.xml with default = user.home
* honor this directoryand create generated AVDs there - this will limit write access to single location - e.g. pattern would be ${androidSdkHome}/.android/${avdName}.avd
Then, *generatedAvdPath* can be dropped altogether - reasoning is that Android UI does not allow that neither and it does not make much sense to split metadata and AVD itself.
--
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
[View Less]
11 years, 4 months