-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Merged by Bors] - Remove confusing clock warning #5163
Conversation
Don't warn about skipping layers right after fresh start
Codecov Report
@@ Coverage Diff @@
## develop #5163 +/- ##
========================================
Coverage 77.6% 77.7%
========================================
Files 259 259
Lines 30457 30750 +293
========================================
+ Hits 23644 23902 +258
- Misses 5322 5357 +35
Partials 1491 1491
|
Combine conditional, drop metrics as well right after startup
bors merge |
Don't warn about skipping layers right after fresh start. This causes constant confusion among community members.
Build failed: |
bors merge |
Don't warn about skipping layers right after fresh start. This causes constant confusion among community members.
Build failed: |
The merge failed twice because of the node not being able to connect to |
bors merge |
Don't warn about skipping layers right after fresh start. This causes constant confusion among community members.
Build failed: |
flaky test: #4668 bors merge |
Don't warn about skipping layers right after fresh start. This causes constant confusion among community members.
Pull request successfully merged into develop. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Don't warn about skipping layers right after fresh start. This causes constant confusion among community members.