RESOLVED FIXED 183103
[build.webkit.org] unit-tests fail if buildbot 0.8.6p1 is not installed locally
https://bugs.webkit.org/show_bug.cgi?id=183103
Summary [build.webkit.org] unit-tests fail if buildbot 0.8.6p1 is not installed locally
Aakash Jain
Reported 2018-02-24 15:57:48 PST
After https://trac.webkit.org/changeset/225534/webkit added import statements, unit-tests requires that buildbot 0.8.6p1 in installed locally. If another buildbot version is installed locally, the tests fails which a confusing error like below. Traceback (most recent call last): File "./steps_unittest.py", line 12, in <module> from steps import (CheckOutSource, Run32bitJSCTests, RunAndUploadPerfTests, RunBenchmarkTests, File "/Users/aakash_jain/code1/OpenSource/Tools/BuildSlaveSupport/build.webkit.org-config/steps.py", line 100, in <module> class CheckOutSource(source.SVN): AttributeError: 'module' object has no attribute 'SVN' Earlier webkitpy used to take care of buildbot packages in background. We stop remove these extra import statements, unless we have a better need to import these explicitly.
Attachments
Proposed patch (1.49 KB, patch)
2018-02-24 16:02 PST, Aakash Jain
no flags
Aakash Jain
Comment 1 2018-02-24 16:02:18 PST
Created attachment 334567 [details] Proposed patch
Aakash Jain
Comment 2 2018-02-24 16:08:35 PST
The following code forces to use buildbot from webkitpy.thirdparty.autoinstalled : https://trac.webkit.org/browser/webkit/trunk/Tools/BuildSlaveSupport/build.webkit.org-config/steps_unittest.py#L38 So, if we import any buildbot module before executing above code, they will be directly imported from locally installed buildbot package.
WebKit Commit Bot
Comment 3 2018-02-25 10:38:42 PST
Comment on attachment 334567 [details] Proposed patch Clearing flags on attachment: 334567 Committed r228977: <https://trac.webkit.org/changeset/228977>
WebKit Commit Bot
Comment 4 2018-02-25 10:38:43 PST
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 5 2018-02-25 10:39:21 PST
Note You need to log in before you can comment on or make changes to this bug.