Chris Apple
Chris Apple
@folliehiyuki just pinging you here as you wrote the original version. I'm going to dig in more at some point, but perhaps in your expertise you see the problem right...
Good investigation. I'll see if I can dive in at some point and figure out if there is a workaround or we need to file a ticket. Thanks for spending...
~~This has been merged, our monthly release goes out in a few days. I'll check it then (because we have a big refactor going through with that release I don't...
No, I think my most recent comment was erroneous (on a wrong ticket). I can still repro this exactly. Thanks for checking on it.
> My idea on how to approach this would be by creating a separate repository that holds the unit tests and files to test on. We could then create an...
(it looks like there is very thorough reviewing going on here, please ping me if you need another pair of eyes, otherwise I completely defer to @sandr01d and @carlfriedrich )
@thinkski pinging you on this again, in case you didn't see!
Thanks @thinkski ! Feel free to close this ticket. I am trying to wrestle with ct-ng to build an m1->rpi3 crosstools and it's giving me grief. These builds you've produced...
I think that seems reasonable. We are open to changing the attribute names. I like the sound of "realtime(required)" and "realtime(forbidden)" Some other possibilities (spitballing): For nonblocking: * realtime *...
> > * rtsan(*) > > I think we shouldn't name stuff after the verification mechanism, since that could be changed/extended to use something other than rtsan. Seems reasonable to...