-
Notifications
You must be signed in to change notification settings - Fork 5
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
Run Gemfile.devel in Github Actions with metanorma-cli #317
Comments
According to my understanding we have to avoid any
Sorry I completely missing this part, i'm not sure how easy it will be to automate it, but let me try |
Perhaps, but it's not my code, it's @abunashir ’s, and I'm disinclined to be the one to fix it. And the point of this spec is to test that the system call to metanorma is working. |
Samples/templates testing now should take in account Update: link to the run https://github.com/metanorma/metanorma-cli/actions/runs/6963118635 |
Test failed, one more update required, will rerun CI soon Update: link to the run https://github.com/metanorma/metanorma-cli/actions/runs/6963118635 |
It's working, as I confirmed last night. Ticket stays open until the various random errors on running template also go away. |
The new issue with templates appears to be mostly 2.7, and GHA hanging at:
https://github.com/metanorma/metanorma-cli/actions/runs/7011812490 |
As a matter of principle I think version constraints must be stated in the gemspec, not in build scripts. |
This one was a workaround which I hope can be removed already, I will do after release |
@CAMOBAP can this issue close? |
@opoudjis I hope so |
As alerted in metanorma/isodoc#546 , Gemfile.devel is ignored in GitHub Actions when running metanorma-cli. Alex has done some fixes, which have made it possible for the metanorma-cli spec file to run correctly with the Gemfile.devel branches of underlying gems. But the samples it contains are still being run with the main branch as far as I can tell: they are crashing in the XSLT preprocessing line of the main branch of isodoc, which is different from the corresponding line in the branch of isodoc named in Gemfile.devel.
As I have found in my own running of metanorma-cli, any system calls to
metanorma
need to be put asbundle exec metanorma
, in order to pick up the Gemfile.devel; it may also be that the system calls are not picking up Gemfile.devel in their environment.I am doing a new release which may address the bug I'm trying to rectify; but the ability to run samples with branches named in Gemfile.devel in GitHub Actions remains a requirement. Especially if the fix I'm working with fails.
The text was updated successfully, but these errors were encountered: