peartherapeutics / bitrise-aws-device-farm-runner

Custom Bitrise step to run tests on aws device farm
MIT License
10 stars 21 forks source link

I am getting the following infinate Loop message: Upload not yet processed; waiting. (Status=INITIALIZED) #50

Closed aksyuma closed 5 years ago

aksyuma commented 5 years ago

Step 1: I use (https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy) to upload my test package (e.g APPIUM_JAVA_TESTNG_PACKAGE) to Device Farm and this step executes successfully.

Step 2: I use (https://github.com/peartherapeutics/bitrise-aws-device-farm-runner) while specifying my Android apk local path + device farm pool arn + test name + project arn and I get an infinite loop of exception below:

$ bitrise run test

██████╗ ██╗████████╗██████╗ ██╗███████╗███████╗ ██╔══██╗██║╚══██╔══╝██╔══██╗██║██╔════╝██╔════╝ ██████╔╝██║ ██║ ██████╔╝██║███████╗█████╗ ██╔══██╗██║ ██║ ██╔══██╗██║╚════██║██╔══╝ ██████╔╝██║ ██║ ██║ ██║██║███████║███████╗ ╚═════╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝╚═╝╚══════╝╚══════╝

version: 1.26.0

INFO[13:56:50] bitrise runs in Secret Filtering mode INFO[13:56:50] Running workflow: test

Switching to workflow: test

+------------------------------------------------------------------------------+ (0) path::./ +------------------------------------------------------------------------------+ id: ./ version: collection: path toolkit: bash time: 2019-02-06T13:56:50+02:00 +------------------------------------------------------------------------------+

INFO[13:56:50] [OK] Step dependency (aws) installed, available. INFO[13:56:50] [OK] Step dependency (jq) installed, available.

REDACTED];34mConfigs:REDACTED]m

REDACTED];34mSetting up device farm run for platform '[REDACTED]'.REDACTED]m

fadookie commented 5 years ago

Did bitrise add those [REDACTED] things to the log? It makes it impossible to tell what the hell is going on.

I have a suspicion this is a misconfiguration on your end rather than a bug in the step, it's tricky to get everything set up correctly but I tried my best to explain it in the wiki and inline input documentation.

There are a couple ways we could try to work around this to get more diagnostic info. One - try downloading the raw log from bitrise.io and see if the [REDACTED] messages still show - if not please upload the entire thing here as a text attachment. (Having it copy-pasted into a github post also makes it really hard to read as the control characters don't get properly rendered as colors.)

As long as your AWS secrets/tokens are not displayed I don't think there's much harm in having the ARNs shown in public. Otherwise you could email them to me.

The other would be to install the bitrise CLI, download your bitrise.yml if you haven't already, and run the workflow locally. This takes some doing to set up but makes debugging much easier. You can make a new workflow which just runs this step and you can manually set all the inputs to mock values such as downloading apk/ipa files from bitrise.io and having it just try to upload those from local file paths.

If you need help with getting the bitrise CLI set up please ask Bitrise support. But I am happy to help try to figure out what's going on here with AWS. However don't expect too much, I don't work for bitrise and I am basically just doing this in my spare time.

elashpear commented 5 years ago

Closing due to inactivity