Skip to content
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

[tooling] Better integration of Coq Bench #10418

Open
ejgallego opened this issue Jun 21, 2019 · 12 comments
Open

[tooling] Better integration of Coq Bench #10418

ejgallego opened this issue Jun 21, 2019 · 12 comments

Comments

@ejgallego
Copy link
Member

@ejgallego ejgallego commented Jun 21, 2019

Since 2014 @clarus has maintained https://coq-bench.github.io/ ; indeed, this tooling seems to be not properly publicized, and as discussed in coq/opam-coq-archive#798 now an alternative was developed (http://check.ocamllabs.io/).

I've opened this issue to track integration of coq-bench within Coq's infrastructure. A few issues are:

  • infrastructure: currently coq-bench runs in @clarus servers; this is not ideal, what could be done about this?
  • notifications: check opam does send a message with changes in buildability to the OCamllabs Slack, could coq-bench do the same for Coq's gitter.
  • linking: where should we add links to the project, should it be in the manual? In Coq's web page?
@clarus
Copy link
Contributor

@clarus clarus commented Jul 22, 2019

@ejgallego Thanks for your message. I am currently looking at if I can achieve connection with Gitter.

@ejgallego
Copy link
Member Author

@ejgallego ejgallego commented Jul 22, 2019

Great @clarus ! I wonder which channel should it go, maybe we should create an OPAM channel?

I think you should be able to do it but just in case ping us on gitter if that doesn't work.

@clarus
Copy link
Contributor

@clarus clarus commented Jul 22, 2019

OK thanks, good for the idea of creating an opam channel.

@clarus
Copy link
Contributor

@clarus clarus commented Jul 24, 2019

Bench reports should now be available on this Gitter canal: https://gitter.im/coq/opam-bench-reports ! I will see over time if the implementation is stable.

@ejgallego
Copy link
Member Author

@ejgallego ejgallego commented Jul 24, 2019

Very nice!

@ejgallego
Copy link
Member Author

@ejgallego ejgallego commented Sep 16, 2020

There was some discussion in the Coq Call today about 2nd stage CI systems, this bug is relevant.

@clarus
Copy link
Contributor

@clarus clarus commented Sep 16, 2020

OK, thanks for the information! What should be done for example? What would be the use cases?

What I should do on the short term:

  • migrate the logs from Gitter to Zulip;
  • fix some package errors which recently accumulated.

@ejgallego
Copy link
Member Author

@ejgallego ejgallego commented Sep 16, 2020

@clarus maybe we could start a discussion about this bug in Zulip? Your list sounds good but I'm sure other devs will have more suggestions.

Coq weekly visio calls are also an option if we feel like live discussion would be good.

@clarus
Copy link
Contributor

@clarus clarus commented Sep 16, 2020

OK, I can start to work on the Zulip bug then. I can join the Coq call next week.

@ejgallego
Copy link
Member Author

@ejgallego ejgallego commented Sep 16, 2020

@ejgallego
Copy link
Member Author

@ejgallego ejgallego commented Sep 23, 2020

One thing that would be great to do is to have coq-bench to automatically open an issue in coq-opam-repos everytime a failure happens.

cc: @Zimmi48 / coqbot ppl

@ejgallego
Copy link
Member Author

@ejgallego ejgallego commented Sep 23, 2020

Another thing that would be useful is to provide a link / status display for coq bench from the main platform / coq opam repos website.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants