[Apache TVM Discuss] [Development/pre-RFC] [RFC] Rebuild Docker images per commit

2022-03-10 Thread Manupa Karunaratne via Apache TVM Discuss
@driazati @leandron , I think this proposal will benefit all the work that require updates to dependencies. @masahi @Leo-arm @elenkalda-arm I would suggest lets scope scripts that is relevant to this proposal (as it seems there are already other places the attackers could exploit anyway) .

Re: [apache/tvm] [VOTE] Replace codeowners with more relevant automation (Issue #10471)

2022-03-10 Thread Andrew Reusch
Hi all, The vote result is +16: +1: 16 votes (5 binding) 0: no votes -1: no votes Therefore the resolution is accepted and the RFC will be merged. Thanks! Andrew -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm/issues/10471#issuecomment-1064303079 You are rec

Re: [apache/tvm] [VOTE] Replace codeowners with more relevant automation (Issue #10471)

2022-03-10 Thread Andrew Reusch
Closed #10471. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm/issues/10471#event-6219441981 You are receiving this because you are subscribed to this thread. Message ID:

[Apache TVM Discuss] [Development/pre-RFC] [RFC] Rebuild Docker images per commit

2022-03-10 Thread driazati via Apache TVM Discuss
[quote="manupa-arm, post:5, topic:12047"] I am not sure I follow this proposal. Can you elaborate ? [/quote] It's mostly that we trust all code running on a branch but not necessarily code running from PRs from forks, same as how Jenkins treats the `Jenkinsfile` today. After thinking about thi

[Apache TVM Discuss] [Development/pre-RFC] [RFC] UMA: Universal Modular Accelerator Interface

2022-03-10 Thread Michael J. Klaiber via Apache TVM Discuss
PR in TVM-RFC: https://github.com/apache/tvm-rfcs/pull/60 --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-uma-universal-modular-accelerator-interface/12039/16) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here]

Re: [apache/tvm-rfcs] [RFC] Unified device/target/memory scope planning (#38)

2022-03-10 Thread Mark Shields
Closed #38. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/38#event-6221275454 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/tvm-rfcs] [RFC] Unified device/target/memory scope planning (#38)

2022-03-10 Thread Mark Shields
Closing as obsolete, since most of this is either already done or has been subsumed by the Collage proposal. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/38#issuecomment-1064590913 You are receiving this because you are subscribed to this thread.

[Apache TVM Discuss] [Development/pre-RFC] [RFC] Type-Directed Relay Fuzzing Library

2022-03-10 Thread Michael Flanders via Apache TVM Discuss
I have some additional comments though I don't work on TVM/Relay; I just helped Steven out with some parts of the fuzzer. [quote="slyubomirsky, post:1, topic:12234"] Fuzzing infrastructure poses the most questions: Should it be defined within TVM’s codebase, or live separately? Where should th