Ali Caglayan (Apr 01 2022 at 11:07): Ali Caglayan (Apr 01 2022 at 11:07):Or I thought I did @Gaëtan Gilbert how do you set the env variables for triggering the bench?
Ali Caglayan (Apr 01 2022 at 11:08):As in which variable did you use before
Gaëtan Gilbert (Apr 01 2022 at 11:15):coq_opam_packages Screenshot_20220401_131407.png
Gaëtan Gilbert (Apr 01 2022 at 11:16):impossible when retrying a job AFAICT, you need a new commit
Ali Caglayan (Apr 01 2022 at 11:20):If I delete the job, then I get the same screen with the variables.
Ali Caglayan (Apr 01 2022 at 11:21):This is what I did but it seems to have ignored my input
Ali Caglayan (Apr 01 2022 at 11:23):Do you know if the "key value" occurs in the log? I couldn't find it
Gaëtan Gilbert (Apr 01 2022 at 11:24):it should be in the printenv and also in the DEBUG: coq_opam_packages
Gaëtan Gilbert (Apr 01 2022 at 11:25):how do you delete jobs?
Ali Caglayan (Apr 01 2022 at 11:25):When you cancel there is a bin icon
Ali Caglayan (Apr 01 2022 at 11:25):Have a go with mine: https://gitlab.com/coq/coq/-/jobs/2280170209
Ali Caglayan (Apr 01 2022 at 11:26):When you click the cancel button there should be a delete jobs button there too
Ali Caglayan (Apr 01 2022 at 11:26):Once you click that it should bring you back (maybe I refreshed) to the start job screen with the value and keys
Ali Caglayan (Apr 01 2022 at 11:27):Thats what I used to trigger it last time but it didn't seem to work
Ali Caglayan (Apr 01 2022 at 11:27):Looks like it didn't cleanup gracefully there
Ali Caglayan (Apr 01 2022 at 11:28):Yeah as you can see coq_opam_packages is the same as before
Gaëtan Gilbert (Apr 01 2022 at 11:28):yeah
just push a new commit
Gaëtan Gilbert (Apr 01 2022 at 11:28):(commit --amend works)
Ali Caglayan (Apr 01 2022 at 11:30):I pushed a temp commit for now restricting to two jobs
Ali Caglayan (Apr 01 2022 at 11:30):Let's see if triggering one still works
Ali Caglayan (Apr 01 2022 at 11:32):Alright trying just coq-bignums : https://gitlab.com/coq/coq/-/jobs/2280435968
Ali Caglayan (Apr 01 2022 at 11:33):Looks like it worked
Ali Caglayan (Apr 01 2022 at 11:33):Since GitLab rolled this feature out a few weeks ago I guess it has some rough edges
Ali Caglayan (Apr 01 2022 at 11:34):Do you know where I should report GitLab issues?
Gaëtan Gilbert (Apr 01 2022 at 11:34):only the api part is new, not the web interface part
Gaëtan Gilbert (Apr 01 2022 at 11:35):Ali Caglayan said:
Do you know where I should report GitLab issues?
https://gitlab.com/gitlab-org/gitlab/-/issues/ maybe
Ali Caglayan (Apr 01 2022 at 14:33):By the way if anybody is interested, I use the Stylish plugin for firefox which lets me override some css. I have one set up that reduces the line gap in GitLab logs.
image.png
compared with
image.png
if you want to tweak it like I did, override:
.log-line {
line-height: 0.95;
min-height: 0.0;
}
Beware that extensions like Stylish essentially have permission to see all your browsing activity. I recommend reading the privacy section of https://en.wikipedia.org/wiki/Stylish
Ali Caglayan (Apr 01 2022 at 16:38):@Maxime Dénès Wow I did not know about that. Thanks for letting me know
Ali Caglayan (Apr 01 2022 at 16:38):I found an open source fork of stylish instead which is called stylus https://github.com/openstyles/stylus/
Maxime Dénès (Apr 01 2022 at 16:41):Yes, that's what I used to have. Beware though, that it is still an attack surface.
Ali Caglayan (Apr 01 2022 at 16:42):What do people do to tweak css safely then?
Gaëtan Gilbert (Apr 01 2022 at 16:54):I'm on stylus
Maxime Dénès (Apr 01 2022 at 22:55):Yes, I don't think there's a problem with Stylus. But there also used to be no problem with Stylish. So my point was not "you shouldn't do it", but rather that giving permissions to an extension to read the content you browse is still something.
Last updated: May 31 2023 at 16:01 UTC