Improving standards compliance

[pmoura]

The current experimental Logtalk support for Scryer Prolog is enough to run the standards compliance test sets. If you want to help in improving standards compliance, consider running the tests, looking into the test failures, and selecting the issues that you want to address (possibly creating a WIP pull request so that others are aware of what you're trying to fix). Running the tests is easy:

1. Clone the logtalk3 repo, run the manual installation script, and then logtalk_user_setup script.
2. Ensuring that your Scryer Prolog repo clone is up-to-date, run cargo clean followed by cargo run --release.
3. Ensure that the scryer-prolog/target/release is in your system path so that running scryer-prolog runs the git version.
4. Change you directory to ~/logtalk/tests/prolog and then run logtalk_tester -p scryer -g "set_logtalk_flag(clean,off)" -w -t 360

To run a test set manually, change directory to the test set directory and the run the scryerlgt script followed by the {tester} goal at the top-level.

Hope this helps. Happy hacking and bug fixing!

[pmoura]

P.S. Logtalk 3.53.0, released yesterday, includes a new issue_creator tool for automatically creating bug report issues for failed tests in GitHub or GitLab servers. With this tool (and an improved version of the setup-scryer-prolog action used from a compliance pipeline), the bug hunting process described above can be automated...

[infogulch]

Maybe it would be helpful to integrate this compliance testing suite into the github workflow that runs automatically on push & pr here in the scryer repo. I'm willing to help implement this; would such a contribution be desired?

[infogulch]

Awesome, thanks. The new run with these changes is going: https://github.com/infogulch/scryer-prolog/actions/runs/4591169519

[infogulch]

I noticed that the logtalk-actions/setup-logtalk@master action prints ~8k lines reporting details of the download and unpacking of the logtalk git repo files. I think it would be better if these verbose logs were omitted by default.

[infogulch]

Nice, it worked!

https://github.com/infogulch/scryer-prolog/actions/runs/4591169519/jobs/8107155034

[infogulch]

This is added in PR #1776. (Independence from ISO Prolog regressions?)

[pmoura]

I noticed that the logtalk-actions/setup-logtalk@master action prints ~8k lines reporting details of the download and unpacking of the logtalk git repo files. I think it would be better if these verbose logs were omitted by default.

The setup-logtalk action now uses unzip -q and wget -nv to silence most of those messages. Thanks for the suggestion.