You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, an installer creation job failed because "The specified timestamp server either could not be reached or
returned an invalid response."
SignTool Error: The specified timestamp server either could not be reached or
returned an invalid response.
SignTool Error: An error occurred while attempting to sign: ReleaseDir\OpenJDK15-jdk_x64_windows_hotspot-15.0.0.30.msi
This is not the bug.
Connectivity issues with external servers happen, and I'm not raising a bug about that.
The issues that I'd like to solve here are:
That if this is encountered again, there should be a retry after a few seconds. Say, 15.
That the message before the failure (which seems to erroneously declares the signing a success), should be predicated on the success of the signing.
M-Davies
added
bug
Issues that are problems in the code as reported by the community
installer
Issues that relate to our installer jobs or installer repo
labels
Jul 8, 2020
Platform:
Windows x64
Problem
Recently, an installer creation job failed because "The specified timestamp server either could not be reached or
returned an invalid response."
This is not the bug.
Connectivity issues with external servers happen, and I'm not raising a bug about that.
The issues that I'd like to solve here are:
That if this is encountered again, there should be a retry after a few seconds. Say, 15.
That the message before the failure (which seems to erroneously declares the signing a success), should be predicated on the success of the signing.
Since this doesn't appear to be a blocker, I raise this knowing it likely won't see attention until after the July release.
The text was updated successfully, but these errors were encountered: