Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] CDN issues with TCK binaries

On the certification request issue for WebSockets:

I calculate a different SHA256 then Joakin, but he is showing the download coming from the correct URL. I have added my download info and clearly they are different binaries as the sizes do not match. I had seen there be caching issues when working with the CDI TCK, but it as a most a few hours. It has been at least 7 hours between when Joakin downloaded and calculated the SHA256 vs when I did, so there is some significant cache delay somewhere. The curl -I header output indicates data should not be cached for more than 2 hours.

Is there an archived value in the build of this TCK:

In the build job that can be used to verify what the correct SHA256 should be for the websocket-tck?

Back to the top