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

loosen commit message requirements w.r.t. to patches as long as all easyconfigs are new #2438

Merged

Conversation

migueldiascosta
Copy link
Member

It seems to me that as long as all easyconfigs are new, the commit message could still be automatically generated

If a new patch being added applies to an existing easyconfig, that easyconfig would need to be modified so a meaningful commit message is still needed, this change only affects the cases where all easyconfig files are new

do close if I'm missing something

@boegel boegel added this to the 3.6.0 milestone Mar 14, 2018
@boegel
Copy link
Member

boegel commented Mar 14, 2018

@migueldiascosta This makes sense to me, I've found the current behaviour rather annoying and unnecessary myself... :)

We need to be a bit careful when changing tools/github.py, since most of the relevant tests for that module are effectively being skipped for PRs (because the GitHub token is not available to prevent that is being leaked).

I'll run the github subsuite myself with this change, and maybe try to enhance the tests to check that this behaviour is retained.

@boegel
Copy link
Member

boegel commented Mar 14, 2018

No problems with tests, so this is good to go imho. Thanks @migueldiascosta!

@boegel boegel merged commit 9024623 into easybuilders:develop Mar 14, 2018
@boegel
Copy link
Member

boegel commented Mar 14, 2018

Ugh, seems like I wasn't careful enough, I didn't check the GitHub-related tests in test/options.py...

@migueldiascosta Can you look into fixing this broken test?

FAIL: Test use of --new-pr (dry run only).
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/353536935/lib/python2.6/site-packages/easybuild_framework-3.6.0.dev0-py2.6.egg/test/framework/options.py", line 2508, in test_new_update_pr
    self.assertErrorRegex(EasyBuildError, error_msg, self.eb_main, args, raise_error=True, testing=False)
  File "/home/travis/virtualenv/python2.6.9/lib/python2.6/site-packages/vsc_install-0.10.32-py2.6.egg/vsc/install/testing.py", line 122, in assertErrorRegex
    self.assertTrue(False, "Expected errors with %s(%s) call should occur" % (call.__name__, str_args))
AssertionError: Expected errors with eb_main(['--new-pr', '--github-user=easybuild_test', '/tmp/eb-OQQvWe/eb-qGd7yf/eb-QxtCZq/toy.eb', '-D', '--disable-cleanup-tmpdir', '--git-working-dirs-path=/tmp/eb-OQQvWe/eb-qGd7yf/eb-QxtCZq/eb-k2lenT/eb-uNqV__/git-working-dir8H5nMe', '/tmp/353536935/lib/python2.6/site-packages/easybuild_framework-3.6.0.dev0-py2.6.egg/test/framework/sandbox/sources/toy/toy-0.0_fix-silly-typo-in-printf-statement.patch'], raise_error=True, testing=False) call should occur

migueldiascosta added a commit to migueldiascosta/easybuild-framework that referenced this pull request Mar 15, 2018
migueldiascosta added a commit to migueldiascosta/easybuild-framework that referenced this pull request Mar 15, 2018
@boegel
Copy link
Member

boegel commented Mar 15, 2018

broken test fixed in #2443

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants