The correct incantation for the behavior you want should be now:
@expectedFailureAll(oslist=no_match(lldbplatformutil.getDarwinOSTriples())).
We are trying do drop the "Unless" versions of the decorators, as the
approach does not scale well. I've put the decorator in place now.
I'll put the tls is
On 4 July 2016 at 06:01, NAKAMURA Takumi via llvm-dev
wrote:
> "git-describe -t" works also for lw tags.
But it doesn't work if there are no tags, I just tested on LLVM and I get:
$ git describe
fatal: No names found, cannot describe anything.
Should be easy enough to create the tags on each br
On 4 July 2016 at 00:42, Robinson, Paul wrote:
> Daniel claimed it was not different, even though he proposed the text.
> I think it is better, as "egregious" (even though it is qualitative)
> helps identify what "rare" circumstances would come under the policy.
> As a non-lawyer I do think it's d
On 4 Jul 2016, at 12:13, Renato Golin via llvm-foundation
wrote:
>
> And since tagging *every* commit doesn't scale for long ranges, and
> anything else will need scripting on the client side, I think we can
> get rid *completely* of any server side hook, and let the client side
> scripts deal w
What doesn't scale about tagging every commit?
True, every tag creates a small file on disk, but then so does every commit.
If you're worried about lots of files in a directory then you can put tags
in nested directories by putting one or more /'s in the tag name. So you
can hide all the commit t
On 4 July 2016 at 15:21, Bruce Hoult wrote:
> What doesn't scale about tagging every commit?
Both Jim and Takumi have reported problems with thousands of tags.
Even though neither of them responded to your enquiries for additional
data, we can't assume there isn't any.
Furthermore, "git describe
Hello List!
I'm trying to add LLDB/DWARF debugging information to the RoboVM opensource
fork [1]
Java AOT compiler. RoboVM uses the LLVM 3.6 (pre-release version) debugging
format
and I got the basics working, but can't get the stack variable inspection
to work.
The IR is generated by RoboVM's own
> El jul. 4, 2016, a las 11:15, Renato Golin escribió:
>
> On 4 July 2016 at 15:21, Bruce Hoult wrote:
>> What doesn't scale about tagging every commit?
>
> Both Jim and Takumi have reported problems with thousands of tags.
> Even though neither of them responded to your enquiries for additiona
>From my perspective:
Do whatever makes y'all happy here :)
On Mon, Jul 4, 2016 at 4:27 AM, Renato Golin
wrote:
> On 4 July 2016 at 00:42, Robinson, Paul wrote:
> > Daniel claimed it was not different, even though he proposed the text.
> > I think it is better, as "egregious" (even though it i
Very few operations search for commit objects by reading every single
commit file. Most operations that read commit objects already know what
they are looking for based on their hash. Plus, over time commit objects
are packed into well indexed archive files, so the total number of commits
stored in
10 matches
Mail list logo
