-
Notifications
You must be signed in to change notification settings - Fork 94
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
Move to entry points #3413
Move to entry points #3413
Conversation
A bunch of minor code style failures revealed on Travis CI. |
08a9664
to
4b4fff6
Compare
4b4fff6
to
36c88f4
Compare
@sgaist - there's still a bunch of test failures. See |
e3e416c
to
8d25b4b
Compare
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.
Very close! Several tests passing, but found several under tests/validation
failing, probably due to -v
being verbose for cylc validate
(and possibly other subcommands). Added comment with links/pointers to what I think is the problem.
Thank you @sgaist
One thing that is currently giving me some trouble: the help option. There's currently all kinds of possible variants to get help on something. One that I havent seen before is We would then have:
What do you guys think about that ? |
Happy to have that standardized. You can get rid of any such weird historical anachronisms 😁 |
But @sgaist |
It's how git does it.. i.e |
I see I haven't been precise enough. I meant it only for the main entry point.
Agreed, that's why it wasn't listed and that part is already working. |
We can definitely standardise behaviour! |
8d25b4b
to
97de025
Compare
One question about the tests, is there any way to run single tests or more specifically the ones that are currently failing explicitly ? While it seems pretty thorough, which is nice, the current test suite is a bit difficult to dive in. |
Hi @sgaist , yes, you can use $ ./etc/bin/run-functional-tests.sh -v ./tests/api-suite-info/00-get-graph-raw-1.t I use Hope that helps 👍 |
ps: some tests may fail occasionally on Travis, but pass on your environment. Which is frustrating. But if they pass on your environment, it should be fine to just say that here, and one of us can try that too, or kick travis until the build passes 👍 Thanks!!! |
@sgaist - the functional tests can be difficult to diagnose if you don't have much Cylc background (annoying, but it's just hard to test a workflow engine). In this case any failures should be pretty straightforward, but if you find it too maddening we might be able to dive in and help. |
Matches current master behaviour
As for jobs-summit and graph-diff, this commands takes arguments after "--".
7a52b8e
to
6ea2267
Compare
Two test failures unfortunately :(
|
Here is an overview of what got changed by this pull request: Issues
======
- Added 78
Complexity increasing per file
==============================
- cylc/flow/scripts/cylc_print.py 27
- cylc/flow/scripts/cylc_check_versions.py 21
- cylc/flow/scripts/cylc_run.py 1
- cylc/flow/scripts/cylc_get_directory.py 1
- cylc/flow/scripts/cylc_ping.py 5
- cylc/flow/scripts/cylc_dump.py 5
- cylc/flow/scripts/cylc_checkpoint.py 1
- cylc/flow/scripts/cylc_kill.py 2
- cylc/flow/scripts/cylc_hold.py 5
- cylc/flow/scripts/cylc_help.py 23
- cylc/flow/scripts/cylc_jobs_poll.py 2
- cylc/flow/scripts/cylc_get_suite_config.py 7
- cylc/flow/scripts/cylc_suite_state.py 25
- cylc/flow/scripts/cylc.py 32
- cylc/flow/scripts/cylc_cycle_point.py 36
- cylc/flow/scripts/cylc_function_run.py 3
- cylc/flow/scripts/cylc_poll.py 2
- cylc/flow/scripts/cylc_ls_checkpoints.py 5
- cylc/flow/scripts/cylc_jobs_submit.py 2
- cylc/flow/scripts/cylc_reset.py 7
- cylc/flow/scripts/cylc_set_verbosity.py 2
- cylc/flow/scripts/cylc_spawn.py 1
- cylc/flow/scripts/cylc_broadcast.py 22
- cylc/flow/scripts/cylc_report_timings.py 7
- cylc/flow/scripts/cylc_insert.py 3
- cylc/flow/scripts/cylc_get_site_config.py 4
- cylc/flow/scripts/cylc_ext_trigger.py 7
- cylc/flow/scripts/cylc_get_suite_version.py 1
- cylc/flow/scripts/cylc_remote_init.py 2
- cylc/flow/scripts/cylc_remove.py 1
- cylc/flow/scripts/cylc_client.py 3
- cylc/flow/scripts/cylc_edit.py 14
- cylc/flow/scripts/cylc_restart.py 1
- cylc/flow/scripts/cylc_get_suite_contact.py 4
- cylc/flow/scripts/cylc_register.py 1
- cylc/flow/scripts/cylc_graph.py 14
- cylc/flow/scripts/cylc_reload.py 1
- cylc/flow/scripts/cylc_check_software.py 13
- cylc/flow/scripts/cylc_show.py 32
- cylc/flow/scripts/cylc_stop.py 14
- cylc/flow/scripts/cylc_validate.py 19
- cylc/flow/scripts/cylc_nudge.py 1
- cylc/flow/scripts/cylc_submit.py 21
- cylc/flow/scripts/cylc_cat_log.py 44
- cylc/flow/scripts/cylc_search.py 20
- cylc/flow/scripts/cylc_monitor.py 83
- cylc/flow/scripts/cylc_view.py 13
- cylc/flow/scripts/cylc_diff.py 9
- cylc/flow/scripts/cylc_release.py 3
- cylc/flow/scripts/cylc_subscribe.py 10
- cylc/flow/scripts/cylc_remote_tidy.py 2
- cylc/flow/scripts/cylc_extract_resources.py 4
- cylc/flow/scripts/cylc_jobs_kill.py 2
- cylc/flow/scripts/cylc_get_host_metrics.py 8
- cylc/flow/scripts/cylc_scan.py 21
- cylc/flow/scripts/cylc_list.py 24
- cylc/flow/scripts/cylc_trigger.py 18
- cylc/flow/scripts/cylc_message.py 14
See the complete overview on Codacy |
Kicked Travis CI as the failed test |
Kicking again! |
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.
Conflicts resolved, tests passing 🍾.
Thanks for your efforts @sgaist, most Cylc changes go through a lot easier, honest!
@sgaist great work! Thanks a lot for your contribution and patience 👏 👏 |
@sgaist, many thanks from me too, good job 💐 |
@oliver-sanders No worries, I'm used to more difficult merges :-) You're welcome guys ! As next "big" step, may I suggest to add pre-commit like talked in cylc-admin issue 64 ? This would partly help cleanup the warnings that have appeared on codacy and help automate coding style standardisation. It can then be applied either once on the whole code base (but might be a bit aggressive with regards to other pull request) or file by file when one is modified. |
+1 for the pre-commit hook @sgaist. Is that something you'd like to submit as a PR? Or could help testing perhaps? |
@sgaist - Nice work! (and thanks sorting the conflicts I introduced!) 🍻 |
I'm in favour of pre-commit hook. We can discuss more on the cylc-admin issue. |
@kinow Do you mean submit a possible configuration to get started on cylc-flow ? If so, sure thing, I can do that. I'll just wait the confirmation to avoid noise. |
@sgaist yes, if you have time tgat would be great, please ☺ |
These changes partially address #2802, #2972
Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.