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

Problem with pep8 in WMAgent Dev #472

Open
ericvaandering opened this issue Apr 28, 2017 · 4 comments
Open

Problem with pep8 in WMAgent Dev #472

ericvaandering opened this issue Apr 28, 2017 · 4 comments

Comments

@ericvaandering
Copy link
Member

Hi @BrunoCoimbra @ticoann

When I try to run "pep8" within our deployment I get an error

[dmwm@72d561e8d903 WMCore]$ pep8
bash: /home/dmwm/unittestdeploy/wmagent/1.1.3.pre5/sw/slc6_amd64_gcc493/external/py2-pep8/1.7.0-comp2/bin/pep8: /build/dmwmbld/srv/state/dmwmbld/builds/comp_gcc493/w/slc6_amd64_gcc493/extern: bad interpreter: No such file or directory

This comes from the fact that the python it's trying to use at the start of which pep8 is this:
#!/build/dmwmbld/srv/state/dmwmbld/builds/comp_gcc493/w/slc6_amd64_gcc493/external/python/2.7.13/bin/python

If I replace this with the standard /usr/bin/env python , everything is OK. Can you fix the RPMs please?

@ticoann
Copy link
Contributor

ticoann commented Apr 28, 2017

@BrunoCoimbra,
I am not sure how this line is set in pep8 file (/home/dmwm/unittestdeploy/wmagent/1.1.3.pre5/sw/slc6_amd64_gcc493/external/py2-pep8/1.7.0-comp2/bin/pep8)

#!/build/dmwmbld/srv/state/dmwmbld/builds/comp_gcc493/w/slc6_amd64_gcc493/external/python/2.7.13/bin/python

It looks like this is set set the rpm creation not on deploy creation.

@BrunoCoimbra
Copy link
Contributor

Hi @ericvaandering @ticoann,

Thanks for reporting this issue. I've just included a fix on [1] and Lina is about to deploy it in testbed.
For a real test however you should test it on a wmagent since the problem was found there.
Could you please deploy it with the latest tag HG1705f and let me know if it works?

[1] cms-sw/cmsdist@5b661f7

@amaltaro
Copy link
Contributor

Bruno, there is no need to deploy it in testbed, it's not used there anyways.

@BrunoCoimbra
Copy link
Contributor

This tag is going to production on Monday. I agree that it's very unlikely to break anything, but it's better to make sure the fix didn't have any side effects.

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

No branches or pull requests

4 participants