forward slashes in step text links are rendered as / |
||||||
Issue descriptionLink to log: https://chromium-swarm.appspot.com/task?id=394a7460f686a610&refresh=10&show_raw=1 Here I see this crash: I 62.362s run_tests_on_device(00b66ea289732aec) [ RUN ] dEQP_GLES2.Default/functional_debug_marker_random I 62.362s run_tests_on_device(00b66ea289732aec) dEQP-GLES2.functional.debug_marker.random I 62.362s run_tests_on_device(00b66ea289732aec) [ CRASHED ] Also from my understanding of the buggy CL, this test is probably where the crash is really happening. However, in the build: https://ci.chromium.org/buildbot/tryserver.chromium.angle/android_angle_deqp_rel_ng/849 I see a bunch of unrelated failures: dEQP_GLES2.Default/functional_draw_draw_elements_points_single_attribute dEQP_GLES2.Default/functional_fbo_completeness_renderable_renderbuffer_stencil_rgb16f dEQP_GLES2.Default/functional_clipping_triangle_vertex_clip_two_clip_neg_y_and_neg_x_neg_y_neg_z dEQP_GLES2.Default/functional_buffer_write_recreate_store_identical_1 Also the failures for some reason in my LUCI UI are not displaying the "/" character properly. The debug marker test failure is not visible. The "/" character problem happens everywhere for me but the incorrect test failures seems to only happen on Android that I know of. Ken or Marc-Antoine, can you help me pipe this to the right person?
,
Oct 19 2017
+jbudorick and phajdan.jr about the incorrect failing test names being reported. That problem's probably somewhere in src/base/test/launcher/ .
,
Dec 4 2017
Moving Infra>Client>Android -> Infra>Client>Chrome+OS=Android
,
Dec 4 2017
,
Dec 4
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 4
This looks like it's still happening https://screenshot.googleplex.com/tYGFwTELRUo However, it looks like the annotation already has the escaped characters $ cit logdog cat logdog://logs.chromium.org/chromium/buildbucket/cr-buildbucket.appspot.com/8928739301813362848/+/annotation other_links: < label: "Merge script log" logdog_stream: < name: "steps/angle_deqp_gles3_gles_tests_on_Android_device_Nexus_5X__retry_with_patch_/0/logs/Merge_script_log/0" > > other_links: < label: "dEQP.GLES3/functional_shaders_struct_local_parameter_out_lowp_fragment" logdog_stream: < name: "steps/angle_deqp_gles3_gles_tests_on_Android_device_Nexus_5X__retry_with_patch_/0/logs/dEQP.GLES3__x2f_functional_shaders_struct_local_parameter_out_lowp_fragment/0" > > other_links: < label: "dEQP.GLES3/functional_shaders_struct_local_parameter_inout_lowp_fragment" logdog_stream: < name: "steps/angle_deqp_gles3_gles_tests_on_Android_device_Nexus_5X__retry_with_patch_/0/logs/dEQP.GLES3__x2f_functional_shaders_struct_local_parameter_inout_lowp_fragment/0" > > |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by hinoka@chromium.org
, Oct 19 2017Summary: milo: forward slashes in step text links are rendered as / (was: angle_endend_tests: Android Test harness doesn't seem to pick up correct failures after a crash)