https://bugs.libre-soc.org/show_bug.cgi?id=1193#c5 * DONE: add to dev-env-setup * DONE: add to openpower-isa.git's CI * TODO: add to all other repo's CI
(In reply to Jacob Lifshay from comment #0) > https://bugs.libre-soc.org/show_bug.cgi?id=1193#c5 ahh yeah this is the *cases* infrastructure not continuing when it generates a subtest.
added pytest-subtests to dev-env-setup and openpower-isa.git's CI. also added generating syscalls.json to CI. https://git.libre-soc.org/?p=dev-env-setup.git;a=shortlog;h=bc8a15c5d523b6b98605328a6ff8c74266883d9f commit bc8a15c5d523b6b98605328a6ff8c74266883d9f Author: Jacob Lifshay <programmerjake@gmail.com> Date: Tue Oct 24 19:09:49 2023 -0700 use https to clone commit 2ec0d8777b145a435451aa3dccfa170853987c58 Author: Jacob Lifshay <programmerjake@gmail.com> Date: Tue Oct 24 19:03:32 2023 -0700 add pytest-subtests==0.11.0 https://bugs.libre-soc.org/show_bug.cgi?id=1194 https://git.libre-soc.org/?p=openpower-isa.git;a=shortlog;h=a5d50b0759a5c9196ae0b10441905a5bbecaabce commit a5d50b0759a5c9196ae0b10441905a5bbecaabce Author: Jacob Lifshay <programmerjake@gmail.com> Date: Tue Oct 24 20:18:48 2023 -0700 install pytest-subtests==0.11.0 commit 5578bacd28f0b28502b3431c30e3dce6870a2e3e Author: Jacob Lifshay <programmerjake@gmail.com> Date: Tue Oct 24 20:18:27 2023 -0700 generate syscalls.json
(In reply to Jacob Lifshay from comment #2) > commit bc8a15c5d523b6b98605328a6ff8c74266883d9f > Author: Jacob Lifshay <programmerjake@gmail.com> > Date: Tue Oct 24 19:09:49 2023 -0700 > > use https to clone revert rhat please. do not make these kinds of "but security" changes.
(In reply to Luke Kenneth Casson Leighton from comment #3) > (In reply to Jacob Lifshay from comment #2) > > > commit bc8a15c5d523b6b98605328a6ff8c74266883d9f > > Author: Jacob Lifshay <programmerjake@gmail.com> > > Date: Tue Oct 24 19:09:49 2023 -0700 > > > > use https to clone > > revert rhat please. do not make these kinds of "but security" > changes. why? every other git clone in the file uses https...if you don't care about security then it shouldn't matter to you. if you think it makes the git.kernel.org server a target, it is anyway. https prevents MitM attacks, so is useful.
(In reply to Jacob Lifshay from comment #4) > why? every other git clone in the file uses https... damnit. they shouldn't be, but of course fucking stupid github/gitlab of *course* use https "bcuz sicurrrrr" goddamn nuisance. *sigh* ok leave it for now. > if you don't care about security then it shouldn't matter to you. don't put words in my mouth. you're not competent to properly do the risk assessment. > if you think it makes the > git.kernel.org server a target, it is anyway. gpg sign-offs. nothing else properly solves the problem. > https prevents MitM attacks, so is useful. completely irrelevant. you've fallen into the usual trap here. ok. i'm annoyed but given that github and gitlab are beyond our control there's no point wasting time here. ftr: https *fails* under certain circumstances (mobile broadband networks) due to *packet* level data corruption. Three Networks (three.co.uk) is particularly bad. some transparent cacheing proxies also manage to corrupt https traffic.