[ 
https://issues.apache.org/jira/browse/BEAM-10527?focusedWorklogId=464821&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-464821
 ]

ASF GitHub Bot logged work on BEAM-10527:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/Jul/20 00:56
            Start Date: 31/Jul/20 00:56
    Worklog Time Spent: 10m 
      Work Description: ibzib commented on pull request #12385:
URL: https://github.com/apache/beam/pull/12385#issuecomment-666849394


   I got `flinkCompatibilityMatrixPROCESS` to pass on my machine by escaping 
the arguments via `${1@Q}`. Apparently whatever shell Jenkins is using does not 
support this. I will have to find a better solution.
   
   I have already spent a long time trying to fix quotes, so I can't help but 
wondering: why do we need `flinkCompatibilityMatrixPROCESS` in the first place, 
when it is not being run anywhere? If it's important, shouldn't we add it to 
some postcommit?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 464821)
    Time Spent: 3h 10m  (was: 3h)

> Python2_PVR_Flink precommit should publish test results to Jenkins
> ------------------------------------------------------------------
>
>                 Key: BEAM-10527
>                 URL: https://issues.apache.org/jira/browse/BEAM-10527
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: P2
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Right now we only have the logs, which often require scrolling up to see the 
> failure (which itself often requires curl'ing the logs because they are too 
> large for a browser to load comfortably). This causes frequent 
> misunderstandings. For example, folks often mistake errors printed by 
> pipelines that are meant to fail (e.g. test_error_message_includes_stage) for 
> actual test failures.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to