Apparent non-determinism in compilation of the .beam files, potentially interesting.
issues:
- captures_build_path_in_beam_cma_cmt_files
erlang-erlware-commons:
version: 1.3.1+dfsg-2
issues:
- captures_build_path_in_beam_cma_cmt_files
erlang-jiffy:
version: 0.14.6+dfsg-1
issues:
...
...
@@ -7531,8 +7523,6 @@ glob2:
version: 0.9.4.4-2.3
issues:
- scons_doesnt_pass_environment_to_build_tools
bugs:
- 1010466
global:
version: 6.5.6-2
issues:
...
...
@@ -16119,8 +16109,6 @@ metapixel:
version: 1.0.2-7.4
issues:
- gcc_captures_build_path
bugs:
- 1010486
metar:
version: 20190227.1-1
issues:
...
...
@@ -17825,10 +17813,6 @@ node-react:
version: 16.2.0-4
comments: |
I think this is exposed by nondeterminstic filesystem ordering but the root cause in that it generates an AST-like graph of all the source files in order to inject debug calls; my clue for this is the "but could not be resolved" error messages in the build log diffs.
node-react-audio-player:
version: 0.17.0-1
issues:
- captures_build_path
node-rollup:
version: 2.35.1-1
issues:
...
...
@@ -33518,10 +33502,6 @@ votca-csg:
votca-csg.7.gz will need a separate patch; it's generated by the %mtime macro at
