1. 11 4月, 2020 2 次提交
    • H
      Temporary Disable Flaky test_cond Under Windows (#23424) · 4c57e395
      Huihuang Zheng 提交于
      The flaky windows test is hard to debug. It just has an exit code 0xc0000374 without any log so we don't know where and why. The probability of failure is about 1/50.
      
      I spent 3 days and found it happened only when using PE + control flow + Windows. Exit code 0xc0000374 indicates heap corruption or access violation, but I found the memory is enough during debugging. There is no failed test under 500+ linux tests. I suspect the reason is multiple thread difference between Windows and Linux but I don't have time to completely debug it now. I will temporary disable the test and fix it in next days.
      4c57e395
    • Z
  2. 10 4月, 2020 38 次提交