-
Notifications
You must be signed in to change notification settings - Fork 14
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
Allow customization of Coq version #252
Conversation
Edit: The deployment had failed, and it was not working correctly @Zimmi48 thoughts on merging? |
7352528
to
5e4da63
Compare
OK, I will have a look today. |
Something happened that made the bot crash. The log says: Process exited with status 143. |
I have not observed it (and did not see such messages in the log), but let me try splitting up the commit into the OCaml part and the bash part, maybe that will reveal what's going on more clearly. (Though if this only happened about 5 minutes ago, that might be a race condition from me merging #251 or #253 and a redeploy happening?) |
Support is not yet hooked up in the OCaml code.
5e4da63
to
d2c6908
Compare
I've split this PR into two commits, one for just the bash change and one for the OCaml change, I'm now trying the deploy of just the bash one |
Bash-only commit seems to be working at coq-community/run-coq-bug-minimizer#2 (comment) |
Is it possible that OCaml doesn't like multiple |
I see the 143 error only on redeploy. I continue to see |
src/bot.ml
Outdated
( Str.matched_group 1 body | ||
, Str.matched_group 2 body |> extract_minimize_file ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue seems to be this pair of lines. Maybe extract_minimize_file
messes things up in a way that Str.matched_group 1 body
fails? (Does OCaml evaluate tuples right-to-left?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tuple evaulation order is undefined afaik
Try writing an expect test to test out your regex. Example in here: #240 You can do |
ca88124
to
5de2adf
Compare
Not entirely clear what the protocol should be, see also coq#183. We currently allow things like `coq-8.14` and `coq.dev` and `coq: dev` and `ocaml: 4.11`, etc.
5de2adf
to
383c157
Compare
Seems to be working pretty well. Thoughts on merging @Zimmi48 ? |
I'm not in a state where I can properly review the PR but if you think this is sufficiently tested (including the case with no argument), then I'm fine with merging. I would just note that it looks like we are starting to grow a language of commands to coqbot and it would be preferable if we try to design this language consistently. It was decided in a Coq Call (then reported as an issue here #250, but not yet implemented) that |
I've added support for |
Seems to work both with and without versions at coq-community/run-coq-bug-minimizer#2 (comment), I'll merge |
Not entirely clear what the protocol should be, see also #183. We
currently allow things like
coq-8.14
andcoq.dev
andcoq: dev
andocaml: 4.11
, etc.