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

fix the condition of max nodes #1840

Merged
merged 1 commit into from
Aug 27, 2018
Merged

fix the condition of max nodes #1840

merged 1 commit into from
Aug 27, 2018

Conversation

hanzou666
Copy link
Contributor

An equal sign isn't contained in the source code, although vg snarls help is as following:

    -m, --max-nodes N      only compute traversals for snarls with <= N nodes [10]

So, I propose to append an equal sign to the condition of max_nodes.

@cgcloud-jenkins
Copy link

Can one of the admins verify this patch?

@ekg
Copy link
Member

ekg commented Aug 24, 2018

Jenkins, OK to test.

1 similar comment
@adamnovak
Copy link
Member

Jenkins, OK to test.

@adamnovak
Copy link
Member

(Also @ekg should now be a proper Jenkins admin fro the vg project.)

@cgcloud-jenkins
Copy link

Jenkins vg tests complete for PR 1840. View the full report here.

19 tests passed, 0 tests failed and 10 tests skipped in 19689 seconds

Tests produced 2684 warnings. 2684 were for lower-than-expected alignment scores

@adamnovak adamnovak merged commit a481191 into vgteam:master Aug 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants