User Details
- User Since
- Feb 7 2018, 7:04 PM (154 w, 6 d)
Today
I am seeing this consistently fail on our internal Ubuntu bot:
Yesterday
It looks like this broke the windows lldb bot:
Fri, Jan 22
Tue, Jan 19
It looks like this broke the windows LLDB buildbot: http://lab.llvm.org:8011/#/builders/83/builds/2795
Wed, Dec 30
This broke the windows mlir bot. Please fix it or revert it:
Dec 3 2020
Dec 2 2020
This caused failures on the Windows lldb buildbot:
Dec 1 2020
Nov 20 2020
Nov 19 2020
Nov 18 2020
Nov 13 2020
Nov 12 2020
onnx-mlir (https://github.com/onnx/onnx-mlir) is currently using parseDimAndSymbolList. Is the intention for this function to not be available outside of mlir any more? I notice it no longer has any uses inside mlir either.
Nov 11 2020
It looks like this broke the windows lldb buildbot:
Nov 10 2020
This test is failing on the Windows bot:
Nov 5 2020
This change broke the windows lldb bot:
Nov 2 2020
@frgossen , Thanks! Let me know if you need any help investigating.
Oct 31 2020
I haven't had a chance to debug this yet, but we are seeing failures in the mlir tests on Windows Debug that appear to be caused by this change. The failures are:
Oct 30 2020
We are seeing a failure in the mlir build on Ubuntu with gcc/g++ since these two changes went in:
Oct 27 2020
Oct 26 2020
It looks like this broke the windows lldb bot:
load-pdb is still failing on the Windows bot. Can you please commit a fix soon or revert the change?
The new test fails on Windows when we compile Debug (instead of Release). Is that expected?
Oct 14 2020
I ask because I'm still trying to figure out why 899 LLDB tests started failing for me on Friday. (Actually, it was 936 tests, but I fixed 37 of them with a fix to a line that was introduced almost a year ago. I have not idea why the problems just started appearing on the 9th.)
It looks like this changed caused a failure on the windows bot and your follow up change to fix the test left it still broken. Can you have a look?
Oct 13 2020
Oct 12 2020
Oct 9 2020
Oct 6 2020
Oct 5 2020
Oct 3 2020
Oct 2 2020
I will try it. I'll let you know if it makes a difference.
Since this was committed, all of our internal bots (but not the external windows bot!) are hanging when the tests run. I've looked into it some and I noticed a couple of things:
Sep 25 2020
LGTM
Sep 24 2020
Sep 16 2020
This broke some bots:
Sep 10 2020
Apr 9 2020
It looks like this broke the windows lldb buildbot:
Mar 11 2020
Adding Nate who is going to own the Windows MLIR Buildbot during my maternity :).
Mar 5 2020
Mar 4 2020
Make check-mlir be the only checks that run
Add AMDGPU and NVPTX to the targets
Mar 3 2020
I'm seeing an error on Windows with this:
Thanks! This works.
Mar 2 2020
@gkistanova: We have the machine setup to connect to silent master (buildmaster_host = 'lab.llvm.org', port = 9994) as we expect some failures. Let me know if we need to do anything else other than commit the patch and wait for a reboot. Thanks!
This change broke the MLIR build on Windows.
Feb 27 2020
Feb 24 2020
It looks like this broke the Windows LLDB Buildbot:
Feb 21 2020
Looks like this broke the Windows LLDB bot: