Skip to content

Actions: mobile-dev-inc/maestro

Actions

close inactive issues

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
close-inactive-issues.yaml
1,326 workflow runs
1,326 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Receiving the following error on running iOS Maestro tests on Expo Server: Error: Request for viewHierarchy failed, because of unknown reason, body: {"code":"internal","errorMessage":"Unable to perform work on main run loop, process main thread busy for 30.0s"} 29 ❌ Error: BlockingCoroutine is cancelling close inactive issues #151: Issue comment #1967 (comment) created by bartekpacia
August 28, 2024 23:19 9s
August 28, 2024 23:19 9s
Receiving the following error on running iOS Maestro tests on Expo Server: Error: Request for viewHierarchy failed, because of unknown reason, body: {"code":"internal","errorMessage":"Unable to perform work on main run loop, process main thread busy for 30.0s"} 29 ❌ Error: BlockingCoroutine is cancelling close inactive issues #150: Issue comment #1967 (comment) created by smehr123
August 28, 2024 23:14 12s
August 28, 2024 23:14 12s
Receiving the following error on running iOS Maestro tests on Expo Server: Error: Request for viewHierarchy failed, because of unknown reason, body: {"code":"internal","errorMessage":"Unable to perform work on main run loop, process main thread busy for 30.0s"} 29 ❌ Error: BlockingCoroutine is cancelling close inactive issues #149: Issue comment #1967 (comment) created by bartekpacia
August 28, 2024 22:36 13s
August 28, 2024 22:36 13s
Receiving the following error on running iOS Maestro tests on Expo Server: Error: Request for viewHierarchy failed, because of unknown reason, body: {"code":"internal","errorMessage":"Unable to perform work on main run loop, process main thread busy for 30.0s"} 29 ❌ Error: BlockingCoroutine is cancelling close inactive issues #148: Issue comment #1967 (comment) created by smehr123
August 28, 2024 22:33 9s
August 28, 2024 22:33 9s
Receiving the following error on running iOS Maestro tests on Expo Server: Error: Request for viewHierarchy failed, because of unknown reason, body: {"code":"internal","errorMessage":"Unable to perform work on main run loop, process main thread busy for 30.0s"} 29 ❌ Error: BlockingCoroutine is cancelling close inactive issues #147: Issue comment #1967 (comment) created by bartekpacia
August 28, 2024 22:21 13s
August 28, 2024 22:21 13s
Receiving the following error on running iOS Maestro tests on Expo Server: Error: Request for viewHierarchy failed, because of unknown reason, body: {"code":"internal","errorMessage":"Unable to perform work on main run loop, process main thread busy for 30.0s"} 29 ❌ Error: BlockingCoroutine is cancelling close inactive issues #146: Issue comment #1967 (comment) created by smehr123
August 28, 2024 22:16 10s
August 28, 2024 22:16 10s
Receiving the following error on running iOS Maestro tests on Expo Server: Error: Request for viewHierarchy failed, because of unknown reason, body: {"code":"internal","errorMessage":"Unable to perform work on main run loop, process main thread busy for 30.0s"} 29 ❌ Error: BlockingCoroutine is cancelling close inactive issues #145: Issue comment #1967 (comment) created by bartekpacia
August 28, 2024 21:41 8s
August 28, 2024 21:41 8s
close inactive issues close inactive issues #144: Scheduled
August 28, 2024 18:01 12s main
main
August 28, 2024 18:01 12s
close inactive issues close inactive issues #143: Scheduled
August 28, 2024 12:08 1m 5s main
main
August 28, 2024 12:08 1m 5s
close inactive issues close inactive issues #142: Scheduled
August 28, 2024 11:04 11s main
main
August 28, 2024 11:04 11s
close inactive issues close inactive issues #141: Scheduled
August 28, 2024 10:05 11s main
main
August 28, 2024 10:05 11s
close inactive issues close inactive issues #140: Scheduled
August 28, 2024 09:05 11s main
main
August 28, 2024 09:05 11s
close inactive issues close inactive issues #139: Scheduled
August 28, 2024 08:06 12s main
main
August 28, 2024 08:06 12s
close inactive issues close inactive issues #138: Scheduled
August 28, 2024 07:05 12s main
main
August 28, 2024 07:05 12s
test if e2e test actually works close inactive issues #137: Issue comment #1961 (comment) created by bartekpacia
August 28, 2024 06:10 15s
August 28, 2024 06:10 15s
Fix samples close inactive issues #136: Issue comment #1962 (comment) created by bartekpacia
August 28, 2024 06:09 11s
August 28, 2024 06:09 11s
close inactive issues close inactive issues #135: Scheduled
August 28, 2024 06:06 12s main
main
August 28, 2024 06:06 12s
close inactive issues close inactive issues #134: Scheduled
August 28, 2024 05:05 11s main
main
August 28, 2024 05:05 11s
close inactive issues close inactive issues #133: Scheduled
August 28, 2024 04:06 14s main
main
August 28, 2024 04:06 14s
close inactive issues close inactive issues #132: Scheduled
August 28, 2024 03:05 14s main
main
August 28, 2024 03:05 14s
close inactive issues close inactive issues #131: Scheduled
August 28, 2024 02:21 15s main
main
August 28, 2024 02:21 15s
Android exception while opening a deeplink - java.lang.NullPointerException: appName must not be null close inactive issues #130: Issue comment #1956 (comment) created by bartekpacia
August 28, 2024 01:46 13s
August 28, 2024 01:46 13s
close inactive issues close inactive issues #129: Scheduled
August 28, 2024 01:32 10s main
main
August 28, 2024 01:32 10s
close inactive issues close inactive issues #128: Scheduled
August 28, 2024 00:20 18s main
main
August 28, 2024 00:20 18s
close inactive issues close inactive issues #127: Scheduled
August 27, 2024 23:05 11s main
main
August 27, 2024 23:05 11s
ProTip! You can narrow down the results and go further in time using created:<2024-08-27 or the other filters available.