|
|
Chromium Code Reviews|
Created:
4 years, 6 months ago by nednguyen Modified:
4 years, 5 months ago CC:
catapult-reviews_chromium.org, telemetry-reviews_chromium.org, Zhen Wang, aiolos (Not reviewing), eakuefner, dtu Base URL:
https://github.com/catapult-project/catapult@master Target Ref:
refs/heads/master Project:
catapult Visibility:
Public. |
Description[Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name
We don't throw exceptions when there is duplicate keys indexed by
module name because telemetry_perf_unittest currently depends on this
naming collision to reduce the number of benchmark it smokes test (bad!)
This CL also renames linux_based_platform_backend_unittest.TestBackend classes to
linux_based_platform_backend_unittest.TestLinuxBackend to
avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05ac80ba6ae7cc3a/telemetry/telemetry/internal/platform/posix_platform_backend_unittest.py#L13)
Change announcement: https://groups.google.com/a/chromium.org/forum/#!topic/telemetry-announce/i6FlJJDFWQA)
Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/897866760cc7c37b766620f2589ad19026e775b1
Patch Set 1 #Patch Set 2 : [telemetry] Throws exception #
Messages
Total messages: 26 (13 generated)
Description was changed from ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys BUG=catapult:# ========== to ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name BUG=catapult:# ==========
Description was changed from ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name BUG=catapult:# ========== to ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name ==========
nednguyen@google.com changed reviewers: + kouhei@chromium.org
The CQ bit was checked by nednguyen@google.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2016/06/27 04:52:01, commit-bot: I haz the power wrote: > Dry run: CQ is trying da patch. Follow status at > > https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... Note to myself: this can be a breaking change, hence I should send out a notice to telemetry-announce@
lgtm telemetry/telemetry/internal/platform/linux_based_platform_backend_unittest.py: Would you describe the change here?
Description was changed from ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name ========== to ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) ==========
Description was changed from ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) ========== to ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) ==========
Description was changed from ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) ========== to ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) ==========
On 2016/06/27 04:53:41, kouhei wrote: > lgtm > > telemetry/telemetry/internal/platform/linux_based_platform_backend_unittest.py: > Would you describe the change here? Done
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Description was changed from ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) ========== to ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) COMMIT=false (Only commit this after July 7th, see: https://groups.google.com/a/chromium.org/forum/#!topic/telemetry-announce/i6F...) ==========
Description was changed from ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) COMMIT=false (Only commit this after July 7th, see: https://groups.google.com/a/chromium.org/forum/#!topic/telemetry-announce/i6F...) ========== to ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) Change announcement: https://groups.google.com/a/chromium.org/forum/#!topic/telemetry-announce/i6F...) ==========
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) Change announcement: https://groups.google.com/a/chromium.org/forum/#!topic/telemetry-announce/i6F...) ========== to ========== [Telemetry] Make discover throw exceptions when it detects duplicate keys indexed by class name We don't throw exceptions when there is duplicate keys indexed by module name because telemetry_perf_unittest currently depends on this naming collision to reduce the number of benchmark it smokes test (bad!) This CL also renames linux_based_platform_backend_unittest.TestBackend classes to linux_based_platform_backend_unittest.TestLinuxBackend to avoid naming collision with posix_platform_backend_unittest.TestBackend (https://github.com/catapult-project/catapult/blob/a8a6fb7ea065c2df8ae129ad05a...) Change announcement: https://groups.google.com/a/chromium.org/forum/#!topic/telemetry-announce/i6F...) Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapu... ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001) as https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
Message was sent while issue was closed.
CQ bit was unchecked.
Message was sent while issue was closed.
kbr@chromium.org changed reviewers: + kbr@chromium.org
Message was sent while issue was closed.
This breaks all of the GPU tests on the Chromium waterfall. See the failing tryjobs like: https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel... from this failed roll: https://codereview.chromium.org/2136653002
Message was sent while issue was closed.
+more Telemetry people because this should probably be reverted (and I don't have privileges to do so)
Message was sent while issue was closed.
A revert of this CL (patchset #2 id:20001) has been created in https://codereview.chromium.org/2137783002/ by nednguyen@google.com. The reason for reverting is: Breaks all of the GPU tests on the Chromium waterfall: https://codereview.chromium.org/2136653002 https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel....
Message was sent while issue was closed.
On 2016/07/09 01:22:09, nednguyen (ooo til 7-11) wrote: > A revert of this CL (patchset #2 id:20001) has been created in > https://codereview.chromium.org/2137783002/ by mailto:nednguyen@google.com. > > The reason for reverting is: Breaks all of the GPU tests on the Chromium > waterfall: https://codereview.chromium.org/2136653002 > https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel.... The breakage could be a real bug in gpu tests: AssertionError: Found conflicting classes for the same key: key=test_base, class_1=<class 'gpu_tests.cloud_storage_test_base.TestBase'>, class_2=<class 'gpu_tests.gpu_test_base.TestBase'> It's possible that currently, one of the two classes is skipped. I will make a CL to rename cloud_storage_test_base.TestBase to cloud_storage_test_base.CloudStorageTestBase |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
