Dotty 0.16.0 was not released completely because of the CI resources problem #6922
Comments
|
By the way, the CI failure in question happened more for that release, but for a different commit: one, two. The first time failed on Another observation: the CI managed to reach the publish task at the time the load was small (I remember one-two tasks running together with mine). It failed earlier when there were many tasks running in parallel (4-5), which leads me to believe the reason is that the CI machine suffers from bad resource management. |
anatoliykmetyuk
changed the title
|
Related: #6641 |
|
Did this happen again? Does it make sense to keep the issue open? |
|
No, 0.18.1-RC1 and 0.17.0 were released properly. We should keep this open however since 0.16.0 is corrupted and we must fix it at some point. |
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
The new sbt-sonatype adds a command to publish all modules in one step (`sonatypeBundleRelease`) which should avoid getting into inconsistent states (scala#7190, scala#6922).
|
Close now, I think no users will care about 0.16.0 anymore. |
The release CI task encountered the same problem as #6832 multiple times. Namely the CI task was terminating abruptly at a random point, without an error message or apparent reason to do so. One time it happened on test_java11 task. Another time it happened on publish_release task which wrote some artefacts (but not all) to Sonatype. When I tried to re-run the task, it now terminated with a proper error once it tried to publish artefacts that were already published.
This diff shows which artefacts were not published (to the left, an example of a correct publish of 0.17.0-RC1, to the right, the broken publish of 0.16.0; versions replaced with a placeholder for clear diff). Precisely, the following artefacts were not published:
Hence, here, the
0.16.0folder is absent at all.So we need to manually publish the missing artefacts, and to investigate these CI failures. Unfortunately, I can't do it since I don't have access to the CI machine.
The text was updated successfully, but these errors were encountered: