Perforce bytes fix#3543
Conversation
This fixes some Python 3 issues.
Importing from future.builtins to override str and bytes actually leads to some subtle problems on Python 2.
Codecov Report
@@ Coverage Diff @@
## master #3543 +/- ##
==========================================
- Coverage 88.27% 88.27% -0.01%
==========================================
Files 323 323
Lines 33781 33779 -2
==========================================
- Hits 29819 29817 -2
Misses 3962 3962
Continue to review full report at Codecov.
|
|
Thanks @rodrigc - I will be back in the office on Wednesday PDT and will check it then. |
|
This fixes the issue for me. |
|
Could you describe your setup, configuration, and what steps you followed to verify the fix? |
|
The setup. It can replicate the problem. I installed your branch for master and worker on Python 2 and 3. After that, it works as expected. |
|
Thanks for providing details about your test setup, and testing on Python 2 and 3! |
|
Does this change require upgrading all the workers as well, or only the master? I can report that upgrading the master and the worker to the head (0.9.11-dev143) solves this problem. Thank you very much. |
|
You need to upgrade both |
Fix a case where the Perforce step was passing bytes all the way down
to RemoteCommand.
buildbot_worker.util.__init__.Obfuscated(b"something")was returning a string"b'something'"instead ofb"something"which was causing things to break.Fixes #3493