-
Bug
-
Resolution: External
-
P3
-
None
-
None
-
None
A user reported that the following email wasn't being posted to the associated PR:
https://mail.openjdk.org/pipermail/hotspot-dev/2022-October/065502.html
https://github.com/openjdk/jdk/pull/10745
It eventually got posted, but the delay was ~17h. Looking at logs, where we are now logging this delay explicitly, most emails experience a 10-20h delay before being posted to a PR, with very few exceptions.
It's not clear what the cause for this is. It may very well have something to do with SKARA-1525, or at least share some of the root cause. My first guess is that Skara is being fed stale data from the archive, possibly because it's trying to use Etag to be a good citizen, but the new hosting provider for the mailing list servers aren't supporting that.
https://mail.openjdk.org/pipermail/hotspot-dev/2022-October/065502.html
https://github.com/openjdk/jdk/pull/10745
It eventually got posted, but the delay was ~17h. Looking at logs, where we are now logging this delay explicitly, most emails experience a 10-20h delay before being posted to a PR, with very few exceptions.
It's not clear what the cause for this is. It may very well have something to do with SKARA-1525, or at least share some of the root cause. My first guess is that Skara is being fed stale data from the archive, possibly because it's trying to use Etag to be a good citizen, but the new hosting provider for the mailing list servers aren't supporting that.
- relates to
-
SKARA-1701 Make use of Etag optional for MailingListArchiveReaderBot
-
- Resolved
-
1.
|
Optimize the method MailmanListReader::conversations |
|
Closed | Guoxiong Li | |
2.
|
Optimize the method Mbox::parseMbox |
|
Closed | Unassigned |