Comment by ~timotheecour on ~sircmpwn/builds.sr.ht
the behavior seems worse now that it was before: in https://github.com/nim-lang/Nim/pull/17315, https://builds.sr.ht/~araq/job/454778 resulted in a (flaky) error, but after I restarted it (and the test succeeded, see https://builds.sr.ht/~timotheecour/job/454810), the status badge in github still shows as failed
Ticket created by ~timotheecour on ~sircmpwn/builds.sr.ht
example: see https://builds.sr.ht/~araq/job/362990
[#362990] 2020/12/09 02:33:32 Booting image openbsd/latest (default) on port 22767 [#362990] 2020/12/09 02:33:32 Waiting for guest to settle [#362990] 2020/12/09 02:33:52 Sending tasks [#362990] 2020/12/09 02:33:52 Sending build environment [#362990] 2020/12/09 02:33:52 Installing packages Warning: Permanently added '[localhost]:22767' (ECDSA) to the list of known hosts. https://cdn.openbsd.org/pub/OpenBSD/6.8/packages-stable/amd64/: ftp: Error retrieving https://cdn.openbsd.org/pub/OpenBSD/6.8/packages-stable/amd64/: 503 Service Unavailable https://cdn.openbsd.org/pub/OpenBSD/6.8/packages/amd64/: ftp: Error retrieving https://cdn.openbsd.org/pub/OpenBSD/6.8/packages/amd64/: 503 Service Unavailable https://cdn.openbsd.org/pub/OpenBSD/6.8/packages/amd64/: empty Can't find gmake Can't find sqlite3 Can't find node Can't find boehm-gc Can't find pcre Can't find sfml Can't find sdl2 Can't find libffi
refs: https://github.com/timotheecour/Nim/issues/442
sourcehut is failing on multiple unrelated PR's, even after restarting.
Comment by ~timotheecour on ~sircmpwn/builds.sr.ht
Comment by ~timotheecour on ~sircmpwn/builds.sr.ht
EDIT: I'm now not sure forks ever worked, the olds builds I'm seeming in https://builds.sr.ht/ are all mentioned as "resubmission" so were perhaps only triggered via clicking on "resubmit build" in the original repo where I initiated a PR. The issue remains that forks should work without having to send a PR to original repo. So those
not fork
checks (there since 2018) could indeed be worth looking into to check if this would fix this
Comment by ~timotheecour on ~sircmpwn/builds.sr.ht
I'm not a maintainer of Nim, I'm just trying to get builds.sr.ht CI to work with my nim fork like it used to so that I can debug a CI failure on openbsd for a nim PR, but this is leading me to an unexpectedly complex rabbit hole.
Comment by ~timotheecour on ~sircmpwn/builds.sr.ht
here's the suggested
git format-patch master
output since you don't want to open that link.From 62207187fc56b1c9b850bb08575fe4d147fb60ad Mon Sep 17 00:00:00 2001 From: Timothee Cour <timothee.cour2@gmail.com> Date: Tue, 5 May 2020 19:02:08 -0700 Subject: [PATCH] grant access to public repos --- dispatchsrht/tasks/github/common.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dispatchsrht/tasks/github/common.py b/dispatchsrht/tasks/github/common.py index 5673d57..dcc8616 100644 --- a/dispatchsrht/tasks/github/common.py +++ b/dispatchsrht/tasks/github/common.py @@ -40,7 +40,7 @@ def github_redirect(return_to): # TODO: Do we want to generalize the scopes? parameters = { "client_id": _github_client_id, - "scope": "repo:status write:repo_hook user:email repo_deployment read:org", + "scope": "repo:status public_repo write:repo_hook user:email repo_deployment read:org", "state": return_to, } return redirect("{}?{}".format(gh_authorize_url, urlencode(parameters))) -- 2.26.0
We use emails to facilitate collaboration, with well documented tooling, documentation, and tutorials, which you might encounter if you approached SourceHut on our terms rather than only looking at it insofar as it's necessary to get BSD CI for your GitHub project.
that's fine, you may jut be missing out on external contributions from people accustomed to PRs and who would rather not have to go through tutorials before they can even send a patch.
Comment by ~timotheecour on ~sircmpwn/builds.sr.ht
thanks for the links! I totally stand by my assessment that the sources are really hard to find (even after you showed me the, it's hard to find starting from https://builds.sr.ht/; I could be missing something big and obvious, but I'm sure I'm not the only one)
judging from the small number of unique committers to https://git.sr.ht/~sircmpwn/dispatch.sr.ht git repo, I also do believe that improving visibility (in particular accepting github PR's on a git mirror) would do wonders in terms of increasing external contributions; same rationale as to why https://gitgitgadget.github.io/ exists (git repo doesn't accept github PR's so ppl created a way around that)
that being said, would this help fix this issue? https://github.com/timotheecour/dispatch.sr.ht/pull/1
Comment by ~timotheecour on ~sircmpwn/builds.sr.ht
btw, what is the git repo url (or github mirror if it exists) for builds.sr.rt (that would contain 5b1bb83b1454507e80336c4696df28170b9bb18d ) ? I've asked here https://todo.sr.ht/~sircmpwn/builds.sr.ht/276#event-31402 but all I got was a "lol" ;-) (oh and super helpful for the prompt answers btw, thanks!)
Comment by ~timotheecour on ~sircmpwn/builds.sr.ht
actually I'm seeing 0 forks on that list