Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Binary garbage in /etc/lsb-release (on Travis CI) #15
Comments
For more information: xolox/python-executor#15
|
While I still don't know why this binary garbage appears during the parsing of This countermeasure has since been confirmed to fix the |
While implementing a fix for #10 I found a really weird edge case that (so far) has only manifested in the Python 2.6 environment on Travis CI: The parsing of
/etc/lsb-releaseresults in the expected variable names but the values contain binary garbage including nul bytes. Here's a failing Travis CI build where the following log message can be observed (hard wrapped for readability):At first this seemed a minor annoyance in the sense that the test suite failed on this and that needed a workaround (see d3451a9). However since then I found that this also has an adverse effect on the test suite of another project of mine which uses
executor.This has left me wondering whether this weird edge case is isolated to the Python 2.6 environment on Travis CI or whether this is a symptom of a bigger problem, possibly a programming error on my side. The weird thing is that the Python 2.7, 3.4, 3.5, 3.6 and PyPy builds all work fine...
In the short term I'm worried that I may have broken the
distributor_idanddistribution_codenamelogic for more environments then just the Python 2.6 environment on Travis CI, so I'm going to add a "countermeasure" of sorts toexecutor.The text was updated successfully, but these errors were encountered: