Skip to content
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

1.19: 1 bit non-determinism in kube-scheduler.1 #94628

Closed
bmwiedemann opened this issue Sep 8, 2020 · 2 comments · Fixed by #94629
Closed

1.19: 1 bit non-determinism in kube-scheduler.1 #94628

bmwiedemann opened this issue Sep 8, 2020 · 2 comments · Fixed by #94629
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@bmwiedemann
Copy link
Contributor

What happened:
50% of builds have a different man page content

What you expected to happen:
It should be possible to get bit-identical build results - might need a patch similar to #68983 - @dims knows these things.

How to reproduce it (as minimally and precisely as possible):
build kubernetes1.19 openSUSE package a few times and compare results. e.g. with my rbk script

Anything else we need to know?:

Environment:

  • OS: openSUSE-Tumbleweed 20200906

While working on reproducible builds for openSUSE, I found that
when building the kubernetes1.19 package, there was sometimes such a difference between builds:

--- old//usr/share/man/man1/kube-scheduler.1    2020-09-08 18:04:00.987086806 +0000
+++ new//usr/share/man/man1/kube-scheduler.1    2020-09-08 18:04:01.015086912 +0000
@@ -257,7 +257,7 @@

 .PP
 \fB\-\-logging\-format string                                   Sets the log format. Permitted formats\fP
-        "json", "text".
+        "text", "json".

 .PP
 .RS
@bmwiedemann bmwiedemann added the kind/bug Categorizes issue or PR as related to a bug. label Sep 8, 2020
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 8, 2020
@bmwiedemann
Copy link
Contributor Author

/sig release

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 8, 2020
@neolit123
Copy link
Member

/sig scheduling

@k8s-ci-robot k8s-ci-robot added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants