Re: [lldb-dev] [llvm-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

2017-08-11 Thread Brian Cain via lldb-dev
Opened https://bugs.llvm.org/show_bug.cgi?id=34168

rc2 uploaded
to /home/testers/uploads/clang+llvm-5.0.0-rc2-linux-x86_64-sles11.3.tar.xz
-- I tried to use /data/testers-uploads/ but that failed.

292e39fe52d7404fcd5cd962cf8917600d45f507
 rc2/clang+llvm-5.0.0-rc2-linux-x86_64-sles11.3.tar.xz


On Fri, Aug 11, 2017 at 7:36 PM, Matthias Braun  wrote:

> +CC Alina
>
> Maybe the bitcode is generated too aggressively and we should find ways to
> disable the Bitcode tests if the host CPU isn't new enough (or
> alternatively disable the bitcode tests by default and only enable them
> when someone asks for them via TEST_SUITE_SUBDIRS?)
>
> - Matthias
>
> > On Aug 11, 2017, at 4:44 PM, Hans Wennborg via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
> >
> > I'm not aware of a bug filed for this, so please file one. I don't
> > know much about the workings of test-suite myself, though.
> >
> > On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain 
> wrote:
> >> Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem
> to be
> >> failing for me with SIGILL.  I'm guessing that my host CPU doesn't
> support
> >> the instructions we're testing?
> >>
> >> Is there already a bug on this failure?  Are there any CPUID-style
> feature
> >> detection flags I can easily add to mark these tests UNSUPPORTED for, or
> >> would I have to write this detection feature?
> >>
> >> On Thu, Aug 10, 2017 at 9:00 PM, Hans Wennborg via Release-testers
> >>  wrote:
> >>>
> >>> Dear testers,
> >>>
> >>> 5.0.0-rc2 was just tagged.
> >>>
> >>> I know we still have a bunch of open release blockers, but there has
> >>> been a lot of merged patches and I'd like to find out what the status
> >>> is.
> >>>
> >>> Please build, test and upload binaries to the sftp. When uploading,
> >>> make sure to use the /data/testers-uploads/ directory on the server.
> >>> Let me know if there are any issues.
> >>>
> >>> I'll upload sources, docs and your binaries to the pre-release website
> >>> once they're ready.
> >>>
> >>> Cheers,
> >>> Hans
> >>> ___
> >>> Release-testers mailing list
> >>> release-test...@lists.llvm.org
> >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
> >>
> >>
> >>
> >>
> >> --
> >> -Brian
> > ___
> > LLVM Developers mailing list
> > llvm-...@lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>


-- 
-Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [llvm-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

2017-08-11 Thread Matthias Braun via lldb-dev
+CC Alina

Maybe the bitcode is generated too aggressively and we should find ways to 
disable the Bitcode tests if the host CPU isn't new enough (or alternatively 
disable the bitcode tests by default and only enable them when someone asks for 
them via TEST_SUITE_SUBDIRS?)

- Matthias

> On Aug 11, 2017, at 4:44 PM, Hans Wennborg via llvm-dev 
>  wrote:
> 
> I'm not aware of a bug filed for this, so please file one. I don't
> know much about the workings of test-suite myself, though.
> 
> On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain  wrote:
>> Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem to be
>> failing for me with SIGILL.  I'm guessing that my host CPU doesn't support
>> the instructions we're testing?
>> 
>> Is there already a bug on this failure?  Are there any CPUID-style feature
>> detection flags I can easily add to mark these tests UNSUPPORTED for, or
>> would I have to write this detection feature?
>> 
>> On Thu, Aug 10, 2017 at 9:00 PM, Hans Wennborg via Release-testers
>>  wrote:
>>> 
>>> Dear testers,
>>> 
>>> 5.0.0-rc2 was just tagged.
>>> 
>>> I know we still have a bunch of open release blockers, but there has
>>> been a lot of merged patches and I'd like to find out what the status
>>> is.
>>> 
>>> Please build, test and upload binaries to the sftp. When uploading,
>>> make sure to use the /data/testers-uploads/ directory on the server.
>>> Let me know if there are any issues.
>>> 
>>> I'll upload sources, docs and your binaries to the pre-release website
>>> once they're ready.
>>> 
>>> Cheers,
>>> Hans
>>> ___
>>> Release-testers mailing list
>>> release-test...@lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>> 
>> 
>> 
>> 
>> --
>> -Brian
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev