http://bugzilla.opensuse.org/show_bug.cgi?id=1049186 http://bugzilla.opensuse.org/show_bug.cgi?id=1049186#c1 Jan Matejek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #1 from Jan Matejek --- The difference is basically a matter of reference count. Why it would be different based on the filesystem ordering, that I don't know. How do I use the disorderfs? Do you have tools that I can use to trigger the problem locally without manually running "osc build" several times and then manually unpacking rpms? :) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1049186 http://bugzilla.opensuse.org/show_bug.cgi?id=1049186#c3 --- Comment #3 from Jan Matejek --- (In reply to Bernhard Wiedemann from comment #2)

Then maybe the order of processing them makes a difference and we could avoid that by always processing them in the same order.

that's a possibility, but...

Is there asynchronous garbage collection that could matter for the reference counts?

...but you're not supposed to GC references that live inside a deterministically compiled code block. It seems somewhat more likely to me that the filesystem ordering is a red herring and the problem is actually caused by hash randomization (which changes order of elements in dicts, this could lead to something like "first listed element has one more reference because it's first") but we'll see -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1049186 http://bugzilla.opensuse.org/show_bug.cgi?id=1049186#c5 --- Comment #5 from Jan Matejek --- well of course that would help if disorderfs helps ;e) we can merge this and get reproducible builds. i'd hold off upstreaming though, because this doesn't address the underlying question of how a file gets a different bytecode based on its compilation order -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1049186 http://bugzilla.opensuse.org/show_bug.cgi?id=1049186#c11 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |mcepl@suse.com Resolution|UPSTREAM |--- --- Comment #11 from Bernhard Wiedemann --- Patch was dropped 2018-12 so this is open again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1049186 Hans-Peter Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hpj@urpla.net -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1049186 http://bugzilla.opensuse.org/show_bug.cgi?id=1049186#c39 --- Comment #39 from OBSbugzilla Bot --- This is an autogenerated message for OBS integration: This bug (1049186) was mentioned in https://build.opensuse.org/request/show/926876 Factory / python36 -- You are receiving this mail because: You are on the CC list for the bug.