You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "XComp (via GitHub)" <gi...@apache.org> on 2023/01/25 12:36:51 UTC

[GitHub] [flink] XComp opened a new pull request, #21756: [FLINK-30787][debug] Adds dmesg call to test_controller to check whether it would succeed on Alibaba instances.

XComp opened a new pull request, #21756:
URL: https://github.com/apache/flink/pull/21756

   This draft adds dmesg to the `test_controller.sh` to check whether it would work on Alibaba instances to determine whether FLINK-13978 is the cause for the error in the e2e tests.


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] zentol commented on pull request #21756: [FLINK-30787][debug] Adds dmesg call to test_controller to check whether it would succeed on Alibaba instances.

Posted by "zentol (via GitHub)" <gi...@apache.org>.
zentol commented on PR #21756:
URL: https://github.com/apache/flink/pull/21756#issuecomment-1406342497

   I'd say lets remove it since no one has been asking for it.
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] zentol commented on pull request #21756: [FLINK-30787][debug] Adds dmesg call to test_controller to check whether it would succeed on Alibaba instances.

Posted by "zentol (via GitHub)" <gi...@apache.org>.
zentol commented on PR #21756:
URL: https://github.com/apache/flink/pull/21756#issuecomment-1404950896

   I mean, it also fails in your personal azure, and the whole dmesg business was added _after_ FLINK-13978.
   
   Chances are this just fails because the tests are run in docker :shrug: 


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] flinkbot commented on pull request #21756: [FLINK-30787][debug] Adds dmesg call to test_controller to check whether it would succeed on Alibaba instances.

Posted by "flinkbot (via GitHub)" <gi...@apache.org>.
flinkbot commented on PR #21756:
URL: https://github.com/apache/flink/pull/21756#issuecomment-1403551203

   <!--
   Meta data
   {
     "version" : 1,
     "metaDataEntries" : [ {
       "hash" : "95df77a3476ed067dd2ff8a6dc09b6be3da3b30a",
       "status" : "UNKNOWN",
       "url" : "TBD",
       "triggerID" : "95df77a3476ed067dd2ff8a6dc09b6be3da3b30a",
       "triggerType" : "PUSH"
     } ]
   }-->
   ## CI report:
   
   * 95df77a3476ed067dd2ff8a6dc09b6be3da3b30a UNKNOWN
   
   <details>
   <summary>Bot commands</summary>
     The @flinkbot bot supports the following commands:
   
    - `@flinkbot run azure` re-run the last Azure build
   </details>


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] XComp merged pull request #21756: [FLINK-30787][ci] Removes dmesg code since it's failing constantly

Posted by "XComp (via GitHub)" <gi...@apache.org>.
XComp merged PR #21756:
URL: https://github.com/apache/flink/pull/21756


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] XComp commented on pull request #21756: [FLINK-30787][debug] Adds dmesg call to test_controller to check whether it would succeed on Alibaba instances.

Posted by "XComp (via GitHub)" <gi...@apache.org>.
XComp commented on PR #21756:
URL: https://github.com/apache/flink/pull/21756#issuecomment-1406779908

   I was leaning towards this as well. I just wasn't sure whether the `dmesg` would be of any help in situations where we were just not aware that this dmesg output would be helpful. But looking into example dmesg output, I couldn't come up issues from the past where this would have been useful. :thinking: 


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink] XComp commented on pull request #21756: [FLINK-30787][debug] Adds dmesg call to test_controller to check whether it would succeed on Alibaba instances.

Posted by "XComp (via GitHub)" <gi...@apache.org>.
XComp commented on PR #21756:
URL: https://github.com/apache/flink/pull/21756#issuecomment-1404966145

   I wanted to verify it because of [Robert's comment](https://issues.apache.org/jira/browse/FLINK-30787?focusedCommentId=17680583&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17680583). He sounded confident that it worked at some point in time. But you're right; it looks like the azure pipeline change didn't cause that. I actually verified the order of the commits, beforehand, but must have mixed up the commit order.
   
   So, I see two options here:
   1. we remove this part of the code again because nobody complained in the passed.
   2. We enable kernel log access in the docker container as explained in [this StackExchange thread](https://unix.stackexchange.com/questions/390184/dmesg-read-kernel-buffer-failed-permission-denied)


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org