"builds.sr.ht" <builds@sr.ht> writes:
> worg-publish #1201941: FAILED in 5m34s>> https://builds.sr.ht/~bzg/job/1201941>> ✓ install ✓ upload ✗ check
I am trying to see what exactly went wrong, but sr.ht is not letting me
see the complete log for some reason.
I am getting
{"errors":[{"message":"Authentication error: Authorization header is required. Expected 'Authorization: Bearer [token]'"}]}
Any idea what is going on?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Hi Ihor,
Ihor Radchenko <yantar92@posteo.net> writes:
> "builds.sr.ht" <builds@sr.ht> writes:>>> worg-publish #1201941: FAILED in 5m34s>>>> https://builds.sr.ht/~bzg/job/1201941>>>> ✓ install ✓ upload ✗ check >> I am trying to see what exactly went wrong, but sr.ht is not letting me> see the complete log for some reason.>> I am getting> {"errors":[{"message":"Authentication error: Authorization header is> required. Expected 'Authorization: Bearer [token]'"}]}>> Any idea what is going on?
Can you give more details on how you are triggering this build?
--
Bastien Guerry
Bastien Guerry <bzg@gnu.org> writes:
>>> https://builds.sr.ht/~bzg/job/1201941>>> ...>> I am getting>> {"errors":[{"message":"Authentication error: Authorization header is>> required. Expected 'Authorization: Bearer [token]'"}]}>>>> Any idea what is going on?>> Can you give more details on how you are triggering this build?
I did not trigger this build. AFAIU, because commits from non-paid
accounts do not trigger the builds, we set up a cron job to rebuild worg
regularly.
The error I am seeing is when I tried to read the full logs upon seeing
the build failure email. The exact URL where I am getting the error is
https://builds.sr.ht/query/log/1201941/check/log
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Ihor Radchenko <yantar92@posteo.net> writes:
> The error I am seeing is when I tried to read the full logs upon seeing> the build failure email. The exact URL where I am getting the error is> https://builds.sr.ht/query/log/1201941/check/log
Yes, because only authenticated users can access this.
I'm sending the log privately now.
--
Bastien Guerry
Bastien Guerry <bzg@gnu.org> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:>>> The error I am seeing is when I tried to read the full logs upon seeing>> the build failure email. The exact URL where I am getting the error is>> https://builds.sr.ht/query/log/1201941/check/log>> Yes, because only authenticated users can access this.>> I'm sending the log privately now.
Thanks!
It was not obvious at all from the error page that the problem is that I
am not logged in. After logging in, I am able to access the logs.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Ihor Radchenko <yantar92@posteo.net> writes:
> It was not obvious at all from the error page that the problem is that I> am not logged in. After logging in, I am able to access the logs.
Great, thanks for confirming.
--
Bastien Guerry