Displaying 11 results from an estimated 11 matches for "dummyrpc".
2018 Sep 11
2
JIT tests on AArch64
...ITTests/MCJITTest.lazy_function_creator_lambda
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/CoreAPIsStandardTest.DefineMaterializingSymbol
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/CoreAPIsStandardTest.FallbackDefinitionGeneratorTest
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/DummyRPC.ReturnErrorFailure
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/DummyRPC.ReturnExpectedFailure
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.AddObjectFailure
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.EmitAndFinalizeFailure
LLVM-Unit :: Exe...
2018 Sep 11
2
JIT tests on AArch64
...mbda
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/CoreAPIsStandardTest.DefineMaterializingSymbol
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/CoreAPIsStandardTest.FallbackDefinitionGeneratorTest
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/DummyRPC.ReturnErrorFailure
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/DummyRPC.ReturnExpectedFailure
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.AddObjectFailure
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.E...
2016 Dec 04
2
[Release-testers] 3.9.1-rc2 is ready for testing
Here's the failing tests for rc2 on SLES11.3 (glibc 2.11, libstdc++4.7).
I've done some amount of triaging what some critical elements of the
failures are. Unabridged log is attached.
Failing Tests (94):
LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncIntInt
LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncVoidBool
LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestSerialization
LLVM-Unit :: Support/SupportTests/ThreadPoolTest.Async
LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrier
LL...
2016 Dec 02
9
3.9.1-rc2 is ready for testing
Hi,
I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in
-rc1 before I could send out a release announcement, so I decided to merge
the fix and tag -rc2 to save some testing cycles.
We can always use more testers, so if you are interested in helping, let
me know.
Thanks,
Tom
2017 Jul 31
0
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
...has just been tagged.
>>>
>>> Please build, test and upload binaries to the sftp. Let me know if
>>> there are any issues.
>>
>> Built and tested rc1. Test failures on amd64-freebsd10:
>>
>> FAIL: LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/DummyRPC.TestClearHandlers (1346 of 38616)
>> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.DoubleFreeTest (2480 of 38616)
>> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.ReallocFreedPointerTest (2505 of 38616)
>> FAIL: AddressSanitizer-...
2017 Jul 31
3
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
...te:
>>
>> 5.0.0-rc1 has just been tagged.
>>
>> Please build, test and upload binaries to the sftp. Let me know if
>> there are any issues.
>
> Built and tested rc1. Test failures on amd64-freebsd10:
>
> FAIL: LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/DummyRPC.TestClearHandlers (1346 of 38616)
> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.DoubleFreeTest (2480 of 38616)
> FAIL: AddressSanitizer-Unit :: ./Asan-i386-inline-Test/AddressSanitizer.ReallocFreedPointerTest (2505 of 38616)
> FAIL: AddressSanitizer-Unit :: ./As...
2017 Jul 26
15
[5.0.0 Release] Release Candidate 1 tagged
Dear testers,
5.0.0-rc1 has just been tagged.
Please build, test and upload binaries to the sftp. 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.
Thanks,
Hans
2018 Jun 04
5
6.0.1-rc2 has been tagged
Hi,
The 6.0.1-rc2 release has been tagged. Testers may begin testing and
reporting results.
-Tom
2018 Apr 26
7
6.0.1-rc1 has been tagged
Hi,
I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading
binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do
so please try to do this before Friday, because I would like to tag 5.0.2-final then.
As a reminder to users and developers, May 18 is the deadline for submitting
merge requests for 6.0.1, so there is still time to get bug fixes
2018 Feb 09
0
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
...e issues, some of which might be easily fixable, others have been there since a long time, and might be harder to fix.
A full overview of the failures on amd64:
********************
Testing Time: 7907.21s
********************
Failing Tests (896):
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/DummyRPC.TestClearHandlers
AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.DoubleFreeTest
AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.ReallocFreedPointerTest
AddressSanitizer-Unit :: ./Asan-i386-calls-Test/AddressSanitizer.UseThenFreeThenUseTest
AddressS...
2018 Feb 09
2
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote:
> On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote:
>>
>> There's been a lot of merges since rc1, and hopefully the tests are in
>> a better state now.
>>
>> 6.0.0-rc2 was just tagged, after r324506.
>>
>>