We tested setBuildTimestamp on Koji instances with Python3 and on Brew instances with Python2. It is working on Koji but not on Brew with python2.
Here are results of testing: https://docs.google.com/document/d/1yJx8VvvoEcI7TNRaBq546slcl1mx2Ch-MHqRKwWSS9s/edit?usp=sharing
Koji packages on Fedora hub: koji-hub-1.16.9-1.fc28.noarch koji-utils-1.16.9-1.fc28.noarch python3-koji-1.16.9-1.fc28.noarch koji-hub-plugins-1.16.9-1.fc28.noarch koji-web-1.16.9-1.fc28.noarch python2-koji-1.16.9-1.fc28.noarch koji-1.16.9-1.fc28.noarch
Koji packages on Fedora builder: koji-builder-1.16.9-1.fc28.noarch python2-koji-1.16.9-1.fc28.noarch koji-1.16.9-1.fc28.noarch koji-builder-plugins-1.16.9-1.fc28.noarch python3-koji-1.16.9-1.fc28.noarch
Koji packages on RHEL7 hub: rh-koji-theme-1.14-1.el7.noarch rh-koji-plugins-1.63-1.el7.noarch koji-1.16.1-31.2.el7_5.noarch koji-hub-1.16.1-31.2.el7_5.noarch koji-hub-plugins-1.16.1-31.2.el7_5.noarch koji-web-1.16.1-31.2.el7_5.noarch koji-utils-1.16.1-31.2.el7_5.noarch python2-koji-1.16.1-31.2.el7_5.noarch
Koji packages on RHEL7 builder: rh-koji-plugins-builder-1.63-1.el7.noarch koji-1.16.1-31.2.el7_5.noarch koji-builder-1.16.1-31.2.el7_5.noarch python2-koji-1.16.1-31.2.el7_5.noarch koji-builder-plugins-1.16.1-31.2.el7_5.noarch
There is a weird 5 minutes difference. It seems to be connected with db, not directly with koji. Anyway, I'm not able to replicate it now.
Sorry, 5 hours - which is more sensible. Those testing environments are set in timezones which are in this distance, so timestamps reflects that.
Yes, you are right. This is our QE problem. We can drop this issue.
Metadata Update from @jcupova: - Issue close_status updated to: Dropped - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/1230
Please continue any further discussion there.