Build failed, why?

1

Hello,
My app (it.andreafontana.hideout) was approved for publication roughly 15 hours ago, but it still returns a 404 on the Flathub website and the build page at https://flathub.org/builds/cae5120e-3b30-43c1-befb-b8d8a0afc5ed shows Build Failed.

However, looking at the actual logs I can’t find any real failure but I don’t get why Job 268655 refers to another app id.

2

I triggered another build. It switched to green “commited” status and then “build failed” after ~40minutes.

This time logs seem fine, but it still give build failed.

3

Seems to be some sort of bug. I will look into it.

1 Like
4 
     ------------------------------------------------
     check_name    | flathub-hooks
     build_id      | 268912
     job_id        | 514320
     status        | 3
     status_reason | One or more validations failed.
     results       | {"diagnostics":[{"refstring":"app/it.andreafontana.hideout/aarch64/stable","is_warning":false,"category":"flatpak_builder_lint","data":{"stdou
     t":{"errors":["appid-url-not-reachable"],"info":["appid-url-not-reachable: Tried https://andreafontana.it"],"message":"See https://docs.flathub.org/linter for
      details and exceptions"},"stderr":""}},{"refstring":"app/it.andreafontana.hideout/x86_64/stable","is_warning":false,"category":"flatpak_builder_lint","data":
     {"stdout":{"errors":["appid-url-not-reachable"],"info":["appid-url-not-reachable: Tried https://andreafontana.it"],"message":"See
     https://docs.flathub.org/linter for details and exceptions"},"stderr":""}}]}

Server-side check fails.

master:~$ curl https://andreafontana.it
curl: (60) SSL: no alternative certificate subject name matches target host name 'andreafontana.it'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above
5

Could you please try: curl -Iv https://andreafontana.it --insecure from that server?

(I see the right/valid certificate here, it was pushed some days ago)

6

Ah, I think I get it now. Those Flathub machines are using IPv6, while the test ones use IPv4. I see the domain is misconfigured for IPv6 (it points to a different host); I’ll try to fix the AAAA record now.

7

Thanks. We should likely force it to use IPv4 as it’s what CI runners do.

8

Just add -4 curl -4 …. and you’re done. Anyway I’m trying to fix AAAA record, but it seems something goes wrong.

9

Ok DNS propagated. Can you trigger a build/upload or something like that @barthalion?

10

Works fine now, it will be picked up for publishing in about 30 minutes: Flathub build status of it.andreafontana.hideout

11

No way, failed again.

12

If it is failed on the same point, probably hits a DNS cache.

13

OK @barthalion I removed the AAAA record from the host and initiated a new build. The publishing succeeded this time :tada: . However, I’d recommend addressing the discrepancy between the machines to avoid future issues.

14

Yeah, as I said, I will handle that – it’s not necessarily on the top of the list right now, though. Thank you for your patience!

1 Like
15

This topic was automatically closed after 2 days. New replies are no longer allowed.