This pretty much covers all the common reasons. I will add an anecdote to further illustrate the difficulty. Not too long ago I was training a student to do a simple experimental procedure that has 5 steps and takes about 3 minutes to perform. I would demonstrate and explain while the student was watching, and was expecting them to do things the same way immediately after me. It took us three repeats before they got it right, and this is not something that requires extreme manual dexterity.
Trying to reproduce what someone else did, from a procedure that likely hasn't been described in great detail and involves many steps, is going to be very difficult. I would like to think that you didn't get wildly different results, because that would indicate either you doing something very wrong, or the published results being questionable. Yet some variance is results is expected and likely innocuous.
Just a comment here, even at the lowest computational level you could find output differences by how the processor was build. You could see unconsistancy between Mac M1 and M2 chips for example.
"unconsistency" is likely not going to occur. It is possible that results would not be identical but they will not be completely different. Time required for execution may be significantly different because of differences in hardware as a whole (memory etc) that will go with the architecture.
If the results are not identitical they cannot be called consistent.
I was thinking about this kind of issues
In terms of numeric precision yes. But we already know that to be the case because of non-deterministic outcomes from software.
I very strongly disagree with this. What we case about is biological conclusions. If two sets of results point to the same biological conclusion, then the exact identity of the numeric results is not important.
You can have consistency in your results interpretation, where hopefully the biological conclusion drawn will be infinitely stronger whatever the numerical precision output by non-deterministic algorithms, hardware, packages or even tools.
However, one has to keep in mind the potential bias that could be involved in any analysis and in fine ignore those with extremely low variability (like non-deterministic algorithms) in regard to the final question.
If ones question is to calculate rocket trajectory in space, numerical values certainty is of highest importance. To calculate pvalue or fold change on genes, probably not.
I think very little in biology is like calculating a rocket trajectory. In fact, I'd say we are rarely even bothered about the pvalue or fold change of an indevidaul gene, and more bothered about the general patterns across whole sets of genes.
If you are able to push your findings to github I would be happy to link to it. I have a section for "ad-hoc reproductions" on ARR: https://github.com/leipzig/awesome-reproducible-research