-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packit.stg did not accept our result update #1028
Comments
Hi @thrix, that's weird -- It works well in our testing PR (packit/hello-world#196 (comment)). But I've merged some bigger changes in our database schema so maybe a related problem to that. I am not working today so will take a look tomorrow. Sorry about that. |
I found a corresponding issue in Sentry. We did process the result, but there was raised an exception when we tried to get file from
so I assume we wrongly parse the EDIT: I see that the referenced PR uses |
I investigated that problem yesterday and found no indicator in the logs about why the check was not updated. Yes, I also spotted the Sentry issue and initially thought it's the cause, but after that, I realized this issue occurs quite often and it's probably because we do some URL swapping magic (TM) before we submit tests to TF and after we get the results back. So at the moment I think it was not the cause of the not updated check, but I'm not completely sure. |
Yes, it happens quite often, not only for this type of issue but for this PR I think it happened all the time or am I wrong? What I thought was that similarly as here we should use the value for |
Oh yes, you're right! Do you want to create a PR? I think we just need to move the if tft_test_run:
ref = tft_test_run.commit_sha outside of the |
Use commit_sha from DB when processing TF results Fixes #1028 Reviewed-by: Jiri Popelka <None>
Franta Sumsal reported an issue about:
systemd-ci-incubator/systemd#11
Saying
But according to our records we sent and update after our testing was completed with an error state:
Please investigate ... I know this is staging ... but it should still werk
The text was updated successfully, but these errors were encountered: