{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":137544609,"defaultBranch":"master","name":"pw-ci","ownerLogin":"ovsrobot","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2018-06-16T01:25:00.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/45605505?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1557258271.0","currentOid":""},"activityList":{"items":[{"before":"a1a29f6a41528f32828243109f419d7b8c184f6e","after":"493abc52b6a9b39a77c272682dc3ffa912a131ed","ref":"refs/heads/master","pushedAt":"2024-01-24T18:07:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"ovsrobot","name":null,"path":"/ovsrobot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45605505?s=80&v=4"},"commit":{"message":"post_pw: Correct the patch ID detection.\n\nThe patch ID detection regex can match on multiple instances of the\nreported patch url. That will cause us to send a bad API request\ninto the patchwork server. Correct this by only trusting the first\nvalue to be sent.\n\nAcked-by: Michael Santana \nSigned-off-by: Aaron Conole ","shortMessageHtmlLink":"post_pw: Correct the patch ID detection."}},{"before":"00725eb4843cc7d2ecd51c787058b98197b79eac","after":"a1a29f6a41528f32828243109f419d7b8c184f6e","ref":"refs/heads/master","pushedAt":"2024-01-23T13:46:14.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"ovsrobot","name":null,"path":"/ovsrobot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45605505?s=80&v=4"},"commit":{"message":"post_pw: Store submitted checks locally as well\n\nJeremy Kerr reports that our PW checks reporting submitted 43000 API calls\nin just a single day. That is alarmingly unacceptable. We can store the\nURLs we've already submitted and then just skip over any additional\nprocessing at least on the PW side.\n\nThis patch does two things to try and mitigate this issue:\n\n1. Store each patch ID and URL in the series DB to show that we reported\n the check. This means we don't need to poll patchwork for check status\n\n2. Store the last modified time of the reports mailing list. This means\n we only poll the mailing list when a new email has surely landed.\n\nAcked-by: Michael Santana \nSigned-off-by: Aaron Conole ","shortMessageHtmlLink":"post_pw: Store submitted checks locally as well"}},{"before":"7be0947c160993a5948dfa9692f1dc572f8fea47","after":"00725eb4843cc7d2ecd51c787058b98197b79eac","ref":"refs/heads/master","pushedAt":"2023-12-06T14:02:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"ovsrobot","name":null,"path":"/ovsrobot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45605505?s=80&v=4"},"commit":{"message":"pw_mon: recheck via patchwork\n\nPrevious selection criteria for a patch series was based on\nscanning open series in the series DB. However, the series DB\nonly tracks those patches where a test is still outstanding.\nOnce a test is completed, it will be marked as inactive and\nthe scan won't find it. This wasn't caught during testing\nbecause the test setup had the series branch updates disabled\nwhich caused a series to stay active even after the results\nwould be marked completed.\n\nCheck the actual patch series directly. This will only work\nfor patchwork instances that don't have many (say only a few\ndozen) outstanding patchwork series. For heavily loaded\npatchwork instances that keep hundreds or thousands of\nseries outstanding the only solution is to use the events\ninterface to poll. That will be a forthcoming option.\n\nThe checking only currently supports selecting the first page\nof results. Support for pagination will be forthcoming.\n\nSigned-off-by: Aaron Conole ","shortMessageHtmlLink":"pw_mon: recheck via patchwork"}},{"before":"6981e2355e583b9006cceb819ad905b9c65a93ed","after":"7be0947c160993a5948dfa9692f1dc572f8fea47","ref":"refs/heads/master","pushedAt":"2023-11-30T13:49:17.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"ovsrobot","name":null,"path":"/ovsrobot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45605505?s=80&v=4"},"commit":{"message":"github: add a tool for restarting checks\n\nThe recheck framework can track specific recheck labels and track a\nstate for them. Add a tool that will restart github workflow runs\nand mark the git build table to check for a repoll. This will allow\nexisting monitor tools to re-poll the workflow and report rerun\nresults.\n\nAcked-by: Michael Santana \nSigned-off-by: Aaron Conole ","shortMessageHtmlLink":"github: add a tool for restarting checks"}},{"before":"a39b4b881d38d96019c692b231244cd1f6bf0578","after":"6981e2355e583b9006cceb819ad905b9c65a93ed","ref":"refs/heads/master","pushedAt":"2023-03-22T15:39:47.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"ovsrobot","name":null,"path":"/ovsrobot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45605505?s=80&v=4"},"commit":{"message":"Revert \"pw_mon: switch to using the events API for tracking series\"\n\nThere is some issue with the timestamp generation, and using\nthe series API seems to be failing. Reverting for now.\n\nThis reverts commit a39b4b881d38d96019c692b231244cd1f6bf0578.\n\nSigned-off-by: Aaron Conole ","shortMessageHtmlLink":"Revert \"pw_mon: switch to using the events API for tracking series\""}},{"before":"500afd62d79e4812b954664b74a97916c147ccd0","after":"a39b4b881d38d96019c692b231244cd1f6bf0578","ref":"refs/heads/master","pushedAt":"2023-03-22T13:04:14.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"ovsrobot","name":null,"path":"/ovsrobot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45605505?s=80&v=4"},"commit":{"message":"pw_mon: switch to using the events API for tracking series\n\nThe Patchwork API implemented events long ago, and emits events on\nmajor changes to patch series. For example, when a series is\nofficially marked completed, a special event gets generated noting the\nseries marker.\n\nWhen pw-ci was first implemented, such API and concepts weren't\navailable, so we had to work around it based on what existed. This has\nsome deficits, the biggest is that the way patch dates are stored is\nbased on the patch noted date (rather than received date), and that can\ncause us to miss patches in patchwork.\n\nThe Events API doesn't suffer from this issue. It also means we no\nlonger will generate queries for whether a series is completed, since\nwe can just monitor the events API for those series-completed events.\n\nThe drawback here is that we will generate extra requests to the\nserver in the normal case. That's because the events API doesn't\ninclude some needed details about the series (like authorship details)\nthat we track. But the upside is we shouldn't miss patches with\nauthorship dates in the past any longer.\n\nSigned-off-by: Aaron Conole \nAcked-by: Michael Santana ","shortMessageHtmlLink":"pw_mon: switch to using the events API for tracking series"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAD6DLZUgA","startCursor":null,"endCursor":null}},"title":"Activity ยท ovsrobot/pw-ci"}