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

Dev/support entry point #333

Merged
merged 22 commits into from
Feb 24, 2020

Conversation

mirkobronzi
Copy link
Contributor

No description provided.

@mirkobronzi mirkobronzi marked this pull request as ready for review February 18, 2020 17:29
@bouthilx
Copy link
Member

bouthilx and others added 5 commits February 23, 2020 22:35
Why:

The commandline parser is responsible of parsing the commandline (duh)
and thus should also have the responsibility of inferring what the user
script is in the given commandline. The repository check still remains
in resolve_config as this is not specific to commandline parsing. This
enables more complex parsing and reuse of templates to keep original
positions in the commandline (previously it was assumed the script would
be at first position in the commandline).

How:

Infer user script during parsing of commandline and save it as an
attribute of the parser. The `user_args` now keeps the `user_script`
within it, we can't simply pop out the first item anymore. The
`user_script`, if found, is then used outside of the parser to detect
a VCS.
Why:

The modification to support more complex inference of user script fixed
a bug that went unnoticed in the functional tests for branching.
The modification of the user script name, which should be detected as a
change in the commandline call, was not detected because it was popped
out of `user_args`. With the modification it was not properly detected,
making plenty of tests fail because they were unfortunately relying on
the bug.

How:

Add --cli-change-type noeffect to let the EVC flow even though there are
changes in the commandline calls (the bug was implicitly doing this).

The test for --non-monitoring-arg was not suppose to lead to any version
change, because the commandline should not be detected as different.
Thus, in this case we remove --cli-change-type noeffect.
Support entry point from within OrionCmdlineParser
Add missing fix for func algo tests
@codecov-io
Copy link

Codecov Report

Merging #333 into develop will increase coverage by 0.01%.
The diff coverage is 26.98%.

Impacted file tree graph

@@            Coverage Diff             @@
##           develop    #333      +/-   ##
==========================================
+ Coverage    41.19%   41.2%   +0.01%     
==========================================
  Files           63      63              
  Lines        10820   10821       +1     
  Branches       271     271              
==========================================
+ Hits          4457    4459       +2     
+ Misses        6339    6338       -1     
  Partials        24      24
Impacted Files Coverage Δ
tests/unittests/core/io/test_space_builder.py 17.64% <ø> (-0.08%) ⬇️
tests/unittests/core/evc/test_conflicts.py 20.74% <ø> (ø) ⬆️
tests/unittests/core/cli/test_info.py 16.85% <0%> (+0.06%) ⬆️
tests/unittests/core/conftest.py 33.74% <0%> (-0.42%) ⬇️
tests/unittests/core/io/test_experiment_builder.py 13.21% <0%> (-0.03%) ⬇️
tests/unittests/core/test_branch_config.py 13.16% <0%> (-0.04%) ⬇️
tests/unittests/core/test_insert.py 24.44% <0%> (ø) ⬆️
tests/functional/algos/test_algos.py 100% <100%> (ø) ⬆️
tests/functional/demo/test_demo.py 97.45% <100%> (ø) ⬆️
tests/functional/branching/test_branching.py 99.22% <100%> (ø) ⬆️
... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b059d83...cb7277f. Read the comment docs.

@bouthilx bouthilx merged commit 540bddc into Epistimio:develop Feb 24, 2020
bouthilx added a commit to bouthilx/orion that referenced this pull request Feb 25, 2020
PR Epistimio#333 adds support to entry points, removing the requirement to make
scripts executable. This commit adapts to doc to this new feature.
bouthilx added a commit to bouthilx/orion that referenced this pull request Feb 25, 2020
PR Epistimio#333 adds support to entry points, removing the requirement to make
scripts executable. This commit adapts to doc to this new feature.
bouthilx added a commit to bouthilx/orion that referenced this pull request Mar 6, 2020
PR Epistimio#333 adds support to entry points, removing the requirement to make
scripts executable. This commit adapts to doc to this new feature.
@bouthilx bouthilx mentioned this pull request Jun 23, 2020
bouthilx added a commit that referenced this pull request Jun 23, 2020
PR #333 adds support to entry points, removing the requirement to make
scripts executable. This commit adapts to doc to this new feature.
@bouthilx bouthilx mentioned this pull request Jun 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants