Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / shazam/fork issues and pull requests

#139 - Ignored inheritance

Issue - State: open - Opened by krpiotrek over 6 years ago

#138 - Video file not found

Issue - State: open - Opened by hram over 6 years ago - 1 comment

#138 - Video file not found

Issue - State: open - Opened by hram over 6 years ago - 1 comment

#138 - Video file not found

Issue - State: open - Opened by hram over 6 years ago - 1 comment

#138 - Video file not found

Issue - State: open - Opened by hram over 6 years ago - 1 comment

#137 - NoTestCasesFoundException

Issue - State: closed - Opened by hram over 6 years ago - 9 comments

#137 - NoTestCasesFoundException

Issue - State: closed - Opened by hram over 6 years ago - 9 comments

#136 - Fork does not recognize my instrumentation APK

Issue - State: open - Opened by GXGOW over 6 years ago

#136 - Fork does not recognize my instrumentation APK

Issue - State: open - Opened by GXGOW over 6 years ago

#136 - Fork does not recognize my instrumentation APK

Issue - State: open - Opened by GXGOW over 6 years ago

#136 - Fork does not recognize my instrumentation APK

Issue - State: open - Opened by GXGOW over 6 years ago

#135 - Problems with 'com.android.tools.build:gradle:3.1.x'

Issue - State: closed - Opened by m-ruhl over 6 years ago - 2 comments

#135 - Problems with 'com.android.tools.build:gradle:3.1.x'

Issue - State: closed - Opened by m-ruhl over 6 years ago - 2 comments

#135 - Problems with 'com.android.tools.build:gradle:3.1.x'

Issue - State: closed - Opened by m-ruhl over 6 years ago - 2 comments

#134 - Fix running Parameterized tests without custom names

Pull Request - State: closed - Opened by TarCV over 6 years ago - 1 comment

#134 - Fix running Parameterized tests without custom names

Pull Request - State: closed - Opened by TarCV over 6 years ago - 1 comment

#134 - Fix running Parameterized tests without custom names

Pull Request - State: closed - Opened by TarCV over 6 years ago - 1 comment

#134 - Fix running Parameterized tests without custom names

Pull Request - State: closed - Opened by TarCV over 6 years ago - 1 comment

#134 - Fix running Parameterized tests without custom names

Pull Request - State: closed - Opened by TarCV over 6 years ago - 1 comment

#133 - Can't run Parameterized tests

Issue - State: open - Opened by TarCV over 6 years ago - 1 comment

#133 - Can't run Parameterized tests

Issue - State: open - Opened by TarCV over 6 years ago - 1 comment

#133 - Can't run Parameterized tests

Issue - State: open - Opened by TarCV over 6 years ago - 1 comment

#133 - Can't run Parameterized tests

Issue - State: open - Opened by TarCV over 6 years ago - 1 comment

#133 - Can't run Parameterized tests

Issue - State: open - Opened by TarCV over 6 years ago - 1 comment

#132 - Run gradle plugin with release version?

Issue - State: closed - Opened by Rackles over 6 years ago - 1 comment

#132 - Run gradle plugin with release version?

Issue - State: closed - Opened by Rackles over 6 years ago - 1 comment

#132 - Run gradle plugin with release version?

Issue - State: closed - Opened by Rackles over 6 years ago - 1 comment

#132 - Run gradle plugin with release version?

Issue - State: closed - Opened by Rackles over 6 years ago - 1 comment

#131 - Can't run Fork Standalone with multiple manually created pools

Issue - State: closed - Opened by Hanzo2000 over 6 years ago - 1 comment

#131 - Can't run Fork Standalone with multiple manually created pools

Issue - State: closed - Opened by Hanzo2000 over 6 years ago - 1 comment

#131 - Can't run Fork Standalone with multiple manually created pools

Issue - State: closed - Opened by Hanzo2000 over 6 years ago - 1 comment

#130 - Can't execute Fork twice or more in sequence

Issue - State: closed - Opened by Hanzo2000 almost 7 years ago - 1 comment
Labels: bug

#130 - Can't execute Fork twice or more in sequence

Issue - State: closed - Opened by Hanzo2000 almost 7 years ago - 1 comment
Labels: bug

#130 - Can't execute Fork twice or more in sequence

Issue - State: closed - Opened by Hanzo2000 almost 7 years ago - 1 comment
Labels: bug

#130 - Can't execute Fork twice or more in sequence

Issue - State: closed - Opened by Hanzo2000 almost 7 years ago - 1 comment
Labels: bug

#130 - Can't execute Fork twice or more in sequence

Issue - State: closed - Opened by Hanzo2000 almost 7 years ago - 1 comment
Labels: bug

#130 - Can't execute Fork twice or more in sequence

Issue - State: closed - Opened by Hanzo2000 almost 7 years ago - 1 comment
Labels: bug

#129 - Upgrage the Gradle plugin to the stable 3.0.0 version

Pull Request - State: closed - Opened by VeskoI almost 7 years ago

#129 - Upgrage the Gradle plugin to the stable 3.0.0 version

Pull Request - State: closed - Opened by VeskoI almost 7 years ago

#129 - Upgrage the Gradle plugin to the stable 3.0.0 version

Pull Request - State: closed - Opened by VeskoI almost 7 years ago

#129 - Upgrage the Gradle plugin to the stable 3.0.0 version

Pull Request - State: closed - Opened by VeskoI almost 7 years ago

#129 - Upgrage the Gradle plugin to the stable 3.0.0 version

Pull Request - State: closed - Opened by VeskoI almost 7 years ago

#129 - Upgrage the Gradle plugin to the stable 3.0.0 version

Pull Request - State: closed - Opened by VeskoI almost 7 years ago

#129 - Upgrage the Gradle plugin to the stable 3.0.0 version

Pull Request - State: closed - Opened by VeskoI almost 7 years ago

#128 - Using filters with fork?

Issue - State: open - Opened by zsperske about 7 years ago - 2 comments
Labels: enhancement

#128 - Using filters with fork?

Issue - State: open - Opened by zsperske about 7 years ago - 2 comments
Labels: enhancement

#128 - Using filters with fork?

Issue - State: open - Opened by zsperske about 7 years ago - 2 comments
Labels: enhancement

#128 - Using filters with fork?

Issue - State: open - Opened by zsperske about 7 years ago - 2 comments
Labels: enhancement

#128 - Using filters with fork?

Issue - State: open - Opened by zsperske about 7 years ago - 2 comments
Labels: enhancement

#128 - Using filters with fork?

Issue - State: open - Opened by zsperske about 7 years ago - 2 comments
Labels: enhancement

#127 - Updating Gradle and Android Gradle Plugin

Pull Request - State: closed - Opened by jbaginski about 7 years ago - 1 comment

#127 - Updating Gradle and Android Gradle Plugin

Pull Request - State: closed - Opened by jbaginski about 7 years ago - 1 comment

#127 - Updating Gradle and Android Gradle Plugin

Pull Request - State: closed - Opened by jbaginski about 7 years ago - 1 comment

#127 - Updating Gradle and Android Gradle Plugin

Pull Request - State: closed - Opened by jbaginski about 7 years ago - 1 comment

#127 - Updating Gradle and Android Gradle Plugin

Pull Request - State: closed - Opened by jbaginski about 7 years ago - 1 comment

#126 - Optimised permissions manager

Pull Request - State: closed - Opened by jbaginski about 7 years ago - 1 comment
Labels: enhancement

#126 - Optimised permissions manager

Pull Request - State: closed - Opened by jbaginski about 7 years ago - 1 comment
Labels: enhancement

#126 - Optimised permissions manager

Pull Request - State: closed - Opened by jbaginski about 7 years ago - 1 comment
Labels: enhancement

#125 - Write arbitrary test metadata to JUnit reports

Pull Request - State: closed - Opened by veniosg about 7 years ago - 2 comments

#125 - Write arbitrary test metadata to JUnit reports

Pull Request - State: closed - Opened by veniosg about 7 years ago - 2 comments

#125 - Write arbitrary test metadata to JUnit reports

Pull Request - State: closed - Opened by veniosg about 7 years ago - 2 comments

#125 - Write arbitrary test metadata to JUnit reports

Pull Request - State: closed - Opened by veniosg about 7 years ago - 2 comments

#125 - Write arbitrary test metadata to JUnit reports

Pull Request - State: closed - Opened by veniosg about 7 years ago - 2 comments

#125 - Write arbitrary test metadata to JUnit reports

Pull Request - State: closed - Opened by veniosg about 7 years ago - 2 comments

#125 - Write arbitrary test metadata to JUnit reports

Pull Request - State: closed - Opened by veniosg about 7 years ago - 2 comments

#124 - Adds granular revoking of runtime permissions

Pull Request - State: closed - Opened by fpezzato about 7 years ago - 1 comment

#124 - Adds granular revoking of runtime permissions

Pull Request - State: closed - Opened by fpezzato about 7 years ago - 1 comment

#124 - Adds granular revoking of runtime permissions

Pull Request - State: closed - Opened by fpezzato about 7 years ago - 1 comment

#124 - Adds granular revoking of runtime permissions

Pull Request - State: closed - Opened by fpezzato about 7 years ago - 1 comment

#124 - Adds granular revoking of runtime permissions

Pull Request - State: closed - Opened by fpezzato about 7 years ago - 1 comment

#123 - Allow arbitrary metadata to be reported in JUnit XML

Issue - State: closed - Opened by iordanis about 7 years ago

#123 - Allow arbitrary metadata to be reported in JUnit XML

Issue - State: closed - Opened by iordanis about 7 years ago

#123 - Allow arbitrary metadata to be reported in JUnit XML

Issue - State: closed - Opened by iordanis about 7 years ago

#123 - Allow arbitrary metadata to be reported in JUnit XML

Issue - State: closed - Opened by iordanis about 7 years ago

#123 - Allow arbitrary metadata to be reported in JUnit XML

Issue - State: closed - Opened by iordanis about 7 years ago

#123 - Allow arbitrary metadata to be reported in JUnit XML

Issue - State: closed - Opened by iordanis about 7 years ago

#123 - Allow arbitrary metadata to be reported in JUnit XML

Issue - State: closed - Opened by iordanis about 7 years ago

#122 - Simplify test class pattern configuration

Issue - State: closed - Opened by iordanis about 7 years ago - 1 comment

#122 - Simplify test class pattern configuration

Issue - State: closed - Opened by iordanis about 7 years ago - 1 comment

#122 - Simplify test class pattern configuration

Issue - State: closed - Opened by iordanis about 7 years ago - 1 comment

#120 - Mark test class to be run wholly on one emulator?

Issue - State: closed - Opened by zsperske about 7 years ago - 3 comments

#120 - Mark test class to be run wholly on one emulator?

Issue - State: closed - Opened by zsperske about 7 years ago - 3 comments

#120 - Mark test class to be run wholly on one emulator?

Issue - State: closed - Opened by zsperske about 7 years ago - 3 comments

#119 - Properly terminate ADB in Fork if all tests passed

Pull Request - State: closed - Opened by Badya about 7 years ago - 10 comments

#119 - Properly terminate ADB in Fork if all tests passed

Pull Request - State: closed - Opened by Badya about 7 years ago - 10 comments

#119 - Properly terminate ADB in Fork if all tests passed

Pull Request - State: closed - Opened by Badya about 7 years ago - 10 comments

#119 - Properly terminate ADB in Fork if all tests passed

Pull Request - State: closed - Opened by Badya about 7 years ago - 10 comments

#119 - Properly terminate ADB in Fork if all tests passed

Pull Request - State: closed - Opened by Badya about 7 years ago - 10 comments

#119 - Properly terminate ADB in Fork if all tests passed

Pull Request - State: closed - Opened by Badya about 7 years ago - 10 comments

#115 - Update documentation of Flakiness Reporter

Issue - State: open - Opened by iordanis over 7 years ago

#115 - Update documentation of Flakiness Reporter

Issue - State: open - Opened by iordanis over 7 years ago

#115 - Update documentation of Flakiness Reporter

Issue - State: open - Opened by iordanis over 7 years ago

#115 - Update documentation of Flakiness Reporter

Issue - State: open - Opened by iordanis over 7 years ago

#115 - Update documentation of Flakiness Reporter

Issue - State: open - Opened by iordanis over 7 years ago