Hi Kenneth, thanks for your answer.
All our easyconfig files are saved in an internal git repository. After each successfully build the easyconfig file was being pushed to the git repository with its build information. That's what is not working now. After new successful build no git push is triggered. No special commands. i.e: $ eb -d --robot . easyconfig $ eb --show-config # # Current EasyBuild configuration # (C: command line argument, D: default value, E: environment variable, F: configuration file) # buildpath (E) = /dev/shm installpath (E) = /XX/easybuild.el7.x86_64 modules-tool (E) = Lmod optarch (E) = GENERIC packagepath (E) = /XX/easybuild.el7.x86_64/packages prefix (E) = /XX/easybuild.el7.x86_64 repository (E) = GitRepository repositorypath (E) = [email protected]/easyconfigs.git robot-paths (D) = /XX/easybuild.el7.x86_64/software/EasyBuild/2.9.0/lib/python2.7/site-packages/easybuild_easyconfigs-2.9.0-py2.7.egg/easybuild/easyconfigs sourcepath (E) = /XX/easybuild/sources I've also tried passing the repository options in the command line. $ eb --check-github == temporary log file in case of crash /tmp/eb-MDnvHJ/easybuild-_xllBs.log Checking status of GitHub integration... Making sure we're online... OK * GitHub user... (none available) => FAIL * GitHub token... (no token found) => FAIL * git command... OK ("git version 2.7.4; ") * GitPython module... OK (GitPython version 1.0.1) * push access to None/easybuild-easyconfigs repo @ GitHub... FAIL (no GitHub user specified) * creating gists... OK * location to Git working dirs... not found (suboptimal) One or more checks FAILed, GitHub configuration not fully complete! See http://easybuild.readthedocs.org/en/latest/Integration_with_GitHub.html#configuration for help. Status of GitHub integration: * --from-pr: OK * --new-pr: not supported * --review-pr: OK * --update-pr: not supported * --upload-test-report: not supported > It's normal that you're not seeing any 'git' commands pop up in the debug log, this is handled entirely by GitPython. any way to debug the GitPython process? Thanks, Arnau 2016-10-04 13:28 GMT+02:00 Kenneth Hoste <[email protected]>: > Hi Arnau, > > On 04/10/16 12:25, Arnau wrote: > >> Hi, >> >> while running EB 2.8.2 on SL6.7 we had some Git Repository configuration >> that was working nicely: >> >> repository=GitRepository >> [email protected]/easyconfigs.git >> >> Now we have another instance running RH7 and EB2.9 and the same Git >> Repository configuration has stooped working. >> >> A part from new EB and new OS the GitPython package has changed from >> 0.3.2-0.6.RC1.el6 to >> 1.0.1-5.el7 (both coming from EPEL). I've tried to install an old version >> of GitPython (/GitPython-0.3.2-0.7.RC1.fc21.noarch) but the problem >> persists >> >> I'm running in debug mode and I don't see any refernce to any git >> command, only few refernces to "name: github_account, config: None". >> >> Anyone faced similar issue? How may I debug this problem? >> > > > Can you specify more precisely what you are trying (commands executed, > output of 'eb --show-config'), and what is not working anymore? > What output are you getting from 'eb --check-github' (although that's > probably mostly irrelevant to your problem)? > > It's normal that you're not seeing any 'git' commands pop up in the debug > log, this is handled entirely by GitPython. > > > regards, > > Kenneth >
