Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
14 | The other reproduce tests make use of diff, so I've just followed their lead. However, cmp probably is more appropriate for the binary files. Perhaps we should change them all to use cmp instead of diff where applicable? |
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
2 | I can try deleting shell but will need to add it back to prevent potential testing issues on Windows related to paths being too long when the reproduce TAR file is extracted. That's the reason why all the reproduce tests that extract the TAR file include shell. | |
14 | I will change to cmp, although diff is a lit built-in command, so that might explain its usage elsewhere. We have some legacy downstream regression tests which we are gradually migrating to lit. That's why we noticed that this coverage was missing. |
I don't know much about lit internals but the existing REQUIRES: shell made me wonder why it is needed. Feel free to keep it or not at your discretion.
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
2 | So basically you want to run this test on non-windows machine right? UNSUPPORTED: system-windows should express the intention more clearly. |
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
2 | It might be worth a comment too saying WHY it's not supported on Windows, because that restriction isn't obvious at first glance. | |
13 | Idle musing, feel free to ignore: I wonder whether we really need to check that the archive in the tar file is binary identical to the input one? Would just checking that the file is in the package be sufficient? |
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
13 | I also wonder about it. Our reproduce-windows.s has: # RUN: tar tf repro.tar | FileCheck %s # CHECK: repro/response.txt # CHECK: repro/{{.*}}/build/foo.o |
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
2 | I've followed what the other reproduce tests have done. I suspect the reasoning for shell is that this can be overridden if your Windows shell, environment and tools can support long paths. By default, shell is not enabled on Windows. I will add a comment. | |
13 | I've basically followed the convention of the other reproduce tests (except the Windows specific ones) that all check the contents too. I'm guessing this is just to be sure that it's also the correct file. I'm happy to change it to only test for its presence in the TAR file if that's the consensus. |
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
13 | I don't really have an opinion either way. Happy to defer to others on this one. |
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
6 | Does it mean that using tar tf like reproduce-windows.s do would allow this to be enabled on windows? | |
13 | I'd slightly prefer to avoid checking the content because LLD tests are already take some time to pass and would be good to reduce this time. I do not mind to leave it for a follow-up, but see my question above. |
LGTM
lld/test/ELF/reproduce-deplibs.s | ||
---|---|---|
6 | Then it is better to do in this way as disabling this test is unnecessary. If your intention is to improve testing coverage then enabling it to run on windows bots looks like a good thing to me. | |
13 | My main concern now it that this and seems few other tests about --reproduce are disabled for no reason it seems. |
Can you also delete shell and check whether harbomaster (pre-merge testing) complains?