I have no memory of writing this so I don't recall if it works or not, but in theory this should submit results to the version of kerneltests-harness that supports OpenID Connect.
Not sure what your intent is, but I merged your pull request and ran sudo ./runtests. My test results were not uploaded. When I run runtests.sh before this change, my results are automatically uploaded. (I also see an indication of pass/fail on the console when I run runtests.sh before this change.
Maybe I do not understand the purpose of the pull request.
garry@tfr$ sudo ./runtests [sudo] password for garry: Running default/memfd Running default/insert_leap_second Running default/selinux-dac-controls Running default/modsign Running default/mq-memory-corruption Running default/paxtest Running default/libhugetlbfs Running default/sysfs-perms Running default/cachedrop Running default/posix_timers Running default/stack-randomness Running default/timer-overhead Your log file is located at: /home/garry/src/kernel-tests/logs/32/5.6.10-300.fc32.x86_64/minimal-default-1588903174.0848687.log Submit your results to: https://apps.fedoraproject.org/kerneltest/ The following information is not submitted with your log; it is for informational purposes only. Vulnerability status: spectre_v2: Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling itlb_multihit: KVM: Mitigation: Split huge pages mds: Mitigation: Clear CPU buffers; SMT vulnerable l1tf: Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable spec_store_bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp tsx_async_abort: Not affected spectre_v1: Mitigation: usercopy/swapgs barriers and __user pointer sanitization meltdown: Mitigation: PTI garry@tfr$
That is because this pull request has nothing to do with the code that is currently running on https://apps.fedoraproject.org/kerneltest/ It is required for a rewrite of the app which is currently in staging. Provided testing works out, this code would be merged at the time that the front end code is promoted from staging.
I have no memory of writing this so I don't recall if it works or not, but in theory this should submit results to the version of kerneltests-harness that supports OpenID Connect.