-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TODO: Improve the UI/build hierachy #127
Comments
Hi @tmcgilchrist @kit-ty-kate |
Hi @kit-ty-kate @tmcgilchrist Please am trying to run opam-repo-ci locally on my PC, I am having this challenge running the scheduler, I get ocluster-scheduler command not found, can you guide me please on how to resolve this? |
Hi @Africanbae (I'm helping co-mentor the opam-repo-ci project for Outreachy).
I think the README in the OCluster repository assumes that you have actually installed the various command line tools such as
|
Hi @patricoferris as regards ocluster running locally on my pc, i have been trying the second stage https://github.com/ocurrent/opam-repo-ci/blob/7adacb8aa3fdb86c07b3c11544223bc2d28a9fa6/CONTRIBUTING.md#running-ocluster but I get ---panic: reflect: indirection through nil pointer to embedded struct [recovered] |
@art-w maybe you know? |
@Africanbae > Are you using minikube/kubernetes and trying to run the OCluster Dockerfiles? (it seems to be an error when docker is not started) Sadly the OCluster Dockerfiles are not usable out of the box, so it would actually be easier to skip the docker stuff and run the ocluster directly, by following all the shell commands in the README. |
Please how can I access the docker file, I am really confused because am using a fedora OS and i don't know how to start from number 1, can i be guided please? |
I have been stuck on running a build service locally, I have the scheduler running on one terminal but when I submit a new job on another terminal, i get --- Missing scheme in (expected 'capnp://...') but before I was getting this result the tailing took a lot of time loading but i did not get any result at the end |
Hi @Africanbae, That sounds to me like the
If the first Do you know if this is what happened? Do you know what error the admin command might have had? |
Hi @patricoferris thanks for the reply, I got Failed: Client "test-user" already registered! when I ran the first ocluster-admin but I noticed the submission.cap file was empty when I checked with the text-editor. What could be wrong? Is there something I didn't do right? |
It sounds like maybe you ran the command multiple times. When the command failed with
with the scheduler running. This will remove the old test-user client and let you regenerate the test-user client and hopefully you can check that the |
@Africanbae > Can you try the following steps and report any potential issues? It should take care of all the ocluster issues you've been having :) Step 0: dependenciesYou'll need $ docker --version
Docker version 20.10.12, build e91ed57
$ docker-compose --version
docker-compose version 1.29.2, build 5becea4c In the following steps, I'm going to assume that we can work in the $ mkdir ~/ocaml && cd ~/ocaml
~/ocaml/ $ ls Also please make sure that you don't have any ocluster still running in the background! Step 1: get
|
Thanks @art-w as regards docker-compose --version i got docker-compose version 1.29.2, build unknown (hope it doesn't matter since it is not an error) |
i got this when i ran make dev-start--- rm -Rf dev/capnp-secrets |
I think your docker is not setup correctly. Can you use docker without |
it seems its docker-compose that is not set up correctly |
Can you share the output of :
|
$ docker info Client: Context: default Debug Mode: false Plugins: app: Docker App (Docker Inc., v0.9.1-beta3) buildx: Docker Buildx (Docker Inc., v0.8.1-docker) scan: Docker Scan (Docker Inc., v0.17.0) Server: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? errors pretty printing info |
Ok so |
sudo systemctl restart docker [sudo] password for ope: Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xeu docker.service" for details. $ systemctl status docker.service × docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; dis> Active: failed (Result: exit-code) since Thu 2022-04-21 08:> TriggeredBy: × docker.socket Docs: https://docs.docker.com Process: 8704 ExecStart=/usr/bin/dockerd -H fd:// --containe> Main PID: 8704 (code=exited, status=1/FAILURE) CPU: 132ms Apr 21 08:59:56 fedora systemd[1]: docker.service: Scheduled res> Apr 21 08:59:56 fedora systemd[1]: Stopped Docker Application Co> Apr 21 08:59:56 fedora systemd[1]: docker.service: Start request> Apr 21 08:59:56 fedora systemd[1]: docker.service: Failed with r> Apr 21 08:59:56 fedora systemd[1]: Failed to start Docker Applic> lines 1-14/14 (END) |
Uh okay your docker is really broken... Can you reinstall it by following some online tutorials for fedora? (I'm afraid I don't have the knowledge to help you for this) |
okay thanks @art-w am on working on it already |
I have been able to resolve docker by reinstalling and removing it from trused zone docker info Client: Context: default Debug Mode: false Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 20.10.12 Storage Driver: btrfs Build Version: Btrfs v5.15.1 Library Version: 102 Logging Driver: journald Cgroup Driver: systemd Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: /usr/libexec/docker/docker-init containerd version: 3df54a852345ae127d1fa3092b95168e4a88e2f8 runc version: v1.0.3-0-gf46b6ba init version: Security Options: seccomp Profile: default cgroupns Kernel Version: 5.16.9-200.fc35.x86_64 Operating System: Fedora Linux 35 (Workstation Edition) OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 7.625GiB Name: fedora ID: 4HSY:IMID:K6AR:XRT3:4HZE:5NXQ:ZG6R:CI6O:3UJY:QTGU:VOL3:EJRQ Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: true |
While running make-dev start ----i get this has part of the output pipeline_1 | 2022-04-21 17:39.24 opam_repo_ci.index [INFO] Index.record local/opam-repository 3ea724 (lint) -> - It has been on frontend_1 | Waiting for build...for the past one hour, does it take a long time? |
Hi @art-w, thanks for yesterday. I am not able to reach http://localhost:8090/ for the opam-repo-ci website but this is opening http://localhost:8080/ for the ocurrent pipeline. |
I think it's caused by the nested git submodules not being there. Can you try: ~/ocaml/opam-repo-ci $ git submodule update --init --recursive (Thanks for the full log for the error! But no need to repeat |
I have tried ~/ocaml/opam-repo-ci $ git submodule update --init --recursive but still didn't work |
Thanks ok, I made some adjustments... Any luck with: ~/ocaml/opam-repo-ci/ $ git fetch art-w
~/ocaml/opam-repo-ci/ $ git rebase art-w/docker |
Still site can't be reached or do I have to run any other thing after rebase? |
Ha yes you need to re-run |
ohhh...i guess so just wanted to be sure |
After running make dev-start i get pipeline_1 | 2022-04-22 13:11.04 application Wrote capability reference to "./dev/capnp-secrets/opam-repo-ci-admin.cap" |
Is the opam-repo-ci website at http://localhost:8090 reachable? There might be some errors printed at the start but hopefully it should work out after a few seconds... You may have to re-run |
Thanks @art-w i can now reach http://localhost:8090/ . please as regards the issue am working on, which of the file will i be making changes on? |
There are multiple ways to do it (and I'm unsure which @kit-ty-kate had in mind). Considering you're running low on time, you should look at: https://github.com/ocurrent/opam-repo-ci/blob/master/web-ui/github.ml#L186 For each entry in the tree available via http://localhost:8090/github/local/opam-repository the variable |
On top of my head, for this particular issue I was more thinking of a change in either This could be done by changing the representation of Once done the web-ui should be able to do the changes automatically according to what |
Thanks @kit-ty-kate @art-w, Ocaml is a new language that I am just learning, as regards the task, i understand am meant to create two separate github statuses, please can i get a sample of how to go about making a github status? Here is what used but i am not sure am correct because i got an error when i tried it |
I've seen some users complain about the web-ui design. In particular the build hierarchy isn't that clear.
For instance in these following examples, it isn't clear for newcomers if it's the main build that failed or something else (in that case it's something else):
My proposal would be to change the hierarchy to be something like:
I would also split the revdeps into a separate github status entry to quickly understand if it's a core issue with the package or a revdeps issue. Maybe it would need its own status page but maybe adding it at the end in the same way lower-bounds/archtectures/... are done would be enough if the status is split.
The text was updated successfully, but these errors were encountered: