In the past here was the flow that I was able to use to test kernels, and subsequently get the Kernel Tester badges: 1) Boot from testing .iso. 2) in kernel test directory, copy config.example to .config 3) uncomment "submit=authenticated" 4) edit in username and password for FAS user credentials, save and exit 5) sudo ./runtests.sh (and/or add -t performance)
If done correctly, resulting in an "Upload successful" from the script,
In the past, this would result in an email acknowledging: ran a test of x.yy.z....... And subsequently, if enough were submitted, a badge was awarded.
At some point, (5.16-5.19 or so) I was getting the ack emails, but not getting badges (well over a hundred of them, so a badge should have been granted)
After something 5.19, no email was sent anymore either. So I assume that the kernel tests go through, but there are no emails, and also no badges.
Any ideas? Any other informaion that I can provide? Have I done something wrong?
Another user reported not receiving the badge in #155. It's currently under investigation.
I've seen that messages are emitted on the bus regarding kernel test results uploaded to the wiki. But for some reason Badges is not evaluating the message correctly it seems.
Regarding e-mail notifications, you may need to enable these in FMN. Anyway, the e-mail notification is a separate issue not related to badges. It may have the same cause, but its not something I can look into.
Do you happen to know the rough time, preferably in UTC, when you ran kernel tests, uploaded results? I need to find the message(s) in datagrepper.
Metadata Update from @gui1ty: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None - Issue assigned to gui1ty - Issue tagged with: T: bug
@sumantrom or @sayanchowdhury if one of you has any ideas, please let me know.
I've pinged Sumantro before on Matrix. But haven't had any response. There's more info from the other user on Discussion. For that user I dug up the message, but I haven't been able to figure out why the badge is not awarded.
Others seem to get the badge just fine.
I think I may have found something. The message for the user that got the badge looks like:
{ "certificate": null, "crypto": null, "headers": { "fedora_messaging_schema": "base.message", "fedora_messaging_severity": 20, "sent-at": "2023-07-09T16:05:40+00:00" }, "i": 0, "msg": { "agent": "buckaroogeek", "test": { "arch": "x86_64", "authenticated": true, "failed_tests": "None", "fedora_version": "38", "kernel_version": "6.4.2-200.fc38.x86_64", "release": "Fedora release 38 (Thirty Eight)", "result": "WARN", "testdate": "Sun Jul 9 04:00:04 PM UTC 2023", "tester": "buckaroogeek", "testset": "default" } }, "msg_id": "2023-24a713ea-7160-4b52-a7ea-28b7ad2cf9e1", "packages": [], "signature": null, "source_name": "datanommer", "source_version": "1.0.4", "timestamp": 1688918740.0, "topic": "org.fedoraproject.prod.kerneltest.upload.new", "username": null, "users": [] }
For the user that didn't get the badge it looks like:
{ "body": { "agent": "ilikelinux", "test": { "arch": "x86_64", "authenticated": true, "failed_tests": "None", "fedora_version": "38", "kernel_version": "6.4.2-201.fc38.x86_64", "release": "Fedora release 38 (Thirty Eight)", "result": "PASS", "testdate": "Sun Jul 9 11:58:47 AM -03 2023", "tester": "ilikelinux", "testset": "performance" } }, "headers": { "fedora_messaging_schema": "base.message", "fedora_messaging_severity": 20, "sent-at": "2023-07-09T15:14:21+00:00" }, "id": "2023-8833f6ff-d94c-4616-9f62-a43836b3e4cb", "queue": null, "topic": "org.fedoraproject.prod.kerneltest.upload.new" }
The rule criteria for that badge is:
criteria: datanommer: filter: topics: - "%(topic)s" users: - "%(msg.agent)s" operation: count condition: greater than or equal to: 1 recipient: "%(msg.agent)s"
The first message has agent inside msg. Whereas the second message has agent inside body. The question is of course, where that difference comes from. But I can tinker around a bit to see if I get it working, nonetheless.
agent
msg
body
Yeah, I tested for F38 during test days - no badge. Just tested for F39 for kernel test days - no badge. Looks like something is broken.
I've run a script, as I've done previously, to award the badge. All users not already having the Science (Kernel Tester I) have been awarded, provided they used their FAS username.
I didn't see you, @gbcox, on the list. What username did you use?
@gui1ty Thanks for the quick reply. That's weird. I followed the test day instructions as described in the Fedora Magazine article - and afterwards received an email confirmation as shown.
You are on the 6.5 list. Not sure what happened to 6.6. That's something to discuss with the organizers of the event.
I'll run the script again for the 6.5 list. I'm pretty sure that will award you the badge.
Turns out I made a mistake, not changing the URL in the script. So, earlier I ran the script for the 6.4 event again. I've run it now for 6.5 and 6.6 as well.
Other than the first badge in the series is not really possible at the moment. But we plan on getting this fixed once Badges 2.0 is usable. So, everyone hang in there and keep those tests coming.
Hello, I ran a test yesterday for 6.7 and looks like badges are still not being awarded properly. LMK if you need more info to get it credited for me. Thanks much.
As mentioned before, the automatic awarding is broken currently. I will run the script again, manually, once the test week is over.
However, to temper expectations, the manual approach does not take previous participation into account. So, it awards the badge only to first time participants.
Thanks for getting back to me. So, I have a badge now, and the next badge will be I believe for participating 5 times. Is the system keeping track of this or do I need to save all of the log files and send a message when I done this 5 times, 10 times, etc.
Thanks!
On Mon, Jan 22, 2024 at 09:38 Sandro . pagure@pagure.io wrote:
gui1ty added a new comment to an issue you are following: `` Hello, I ran a test yesterday for 6.7 and looks like badges are still not being awarded properly. LMK if you need more info to get it credited for me. Thanks much. As mentioned before, the automatic awarding is broken currently. I will run the script again, manually, once the test week is over. However, to temper expectations, the manual approach does not take previous participation into account. So, it awards the badge only to first time participants. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-badges/issue/912
gui1ty added a new comment to an issue you are following: ``
However, to temper expectations, the manual approach does not take previous participation into account. So, it awards the badge only to first time participants. ``
To reply, visit the link below or just reply to this email https://pagure.io/fedora-badges/issue/912
To be frank, anything above tier 1 will just not be awarded for the time being. It's too much work to track and verify. However, there's ongoing work on overhauling Badges, so all badges can be awarded once more in an automated fashion. But it's too soon for promises of any kind.
OK, thanks!
On Mon, Jan 22, 2024 at 10:32 Sandro . pagure@pagure.io wrote:
gui1ty added a new comment to an issue you are following: `` Thanks for getting back to me. So, I have a badge now, and the next badge will be I believe for participating 5 times. Is the system keeping track of this or do I need to save all of the log files and send a message when I done this 5 times, 10 times, etc. To be frank, anything above tier 1 will just not be awarded for the time being. It's too much work to track and verify. However, there's ongoing work on overhauling Badges, so all badges can be awarded once more in an automated fashion. But it's too soon for promises of any kind. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-badges/issue/912
To be frank, anything above tier 1 will just not be awarded for the time being. It's too much work to track and verify. However, there's ongoing work on overhauling Badges, so all badges can be awarded once more in an automated fashion. But it's too soon for promises of any kind. ``
This repository has moved over to Fedora Forge. All issue tickets have been transferred in there.
Metadata Update from @t0xic0der: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)