superfly/flyctl-actions@1.1 false failure

My most recent GitHub Actions deployment of my Phoenix app “failed” on the Run superfly/flyctl-actions@1.1 step. However I can’t see any errors in the logs and the deployment has actually succeeded.

Has anyone else experienced false negatives on their deployments?

Below is all of the yellow & red text in the logs of this deployment step.

7 WARN no config file found at /github/home/.fly/config.yml
775 debconf: delaying package configuration, since apt-utils is not installed
3144 warning: ^^^ is deprecated. It is typically used as xor but it has the wrong precedence, use Bitwise.bxor/2 instead
3217 warning: System.stacktrace/0 is deprecated. Use __STACKTRACE__ instead
3352 debconf: delaying package configuration, since apt-utils is not installed
3438 + basename rafo
3439 + basename rafo
3440 + ln -nfs /app/rafo/bin/rafo /app/entry

Yes, this is happening to me too in my GitHub Action.

==> Creating release
--> release v3 created

--> You can detach the terminal anytime without stopping the deployment
==> Release command detected: npx prisma migrate deploy

--> This release will not be available until the release command succeeds.
	 Starting instance
	 Configuring virtual machine
	 Pulling container image
	 Unpacking image
	 Preparing kernel init
	 Configuring firecracker
	 Starting virtual machine
	 Starting init (commit: 7943db6)...
	 Preparing to run: ` npx prisma migrate deploy` as root
	 2022/01/01 13:33:07 listening on [fdaa:0:4288:a7b:20dc:a930:f1cb:2]:22 (DNS: [fdaa::3]:53)
	 Prisma schema loaded from prisma/schema.prisma
	 Datasource "db": PostgreSQL database "falling_firefly_703", schema "public" at "top2.nearest.of.myapp-postgres.internal:5432"
	 3 migrations found in prisma/migrations
	 No pending migrations to apply.
	 npm notice Changelog: <>
	 npm notice
	 Main child exited normally with code: 0
	 Starting clean up.

The deploy job succeeds, but GitHub reports the job as a failure. There are no warnings/errors in the logs for me, however. Output simply stops after Starting clean up. (as you can see above).

Thanks for the reports. Do you both have a release command set? Can you post your fly.toml?

I was able to reproduce this. We’ll push a fix shortly.

Release v0.0.276 should fix this problem.

1 Like

Thanks! I’ll try it later. Yes btw I do have a release command set to npx prisma migrate deploy.

Yes I can confirm this update fixed it! Thanks again.

Brilliant thanks @joshua, triggered a redeploy of that action and it succeeded this time :slight_smile: