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
For some configurations we have a race condition between the first pod and the fileserver. We should add wait until ready for the fileserver to ensure is ready when the first pod is starting.
@pepoviola The comment for an outstanding substrate PR says that tests are not passing due to this.
Indeed I saw a test failing repeatedly there, but now is green. Is this issue something that manifests sporadically? Is ok to merge our PR or we have to wait for this issue to be solved?
@pepoviola The comment for an outstanding substrate PR says that tests are not passing due to this.
Indeed I saw a test failing repeatedly there, but now is green. Is this issue something that manifests sporadically? Is ok to merge our PR or we have to wait for this issue to be solved?
Hi @davxy, this race condition happens sporadically (and under heavy load in our cluster). Is safe to merge the pr in substrate :)
For some configurations we have a race condition between the first pod and the fileserver. We should add
wait until ready
for the fileserver to ensure is ready when the first pod is starting.see: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2314818
cc: @michalkucharczyk
The text was updated successfully, but these errors were encountered: