CommitTicketUpdater does not process commits in order

[Sebastian Huber]

The new CommitTicketUpdater? does not process commits in order. For example see:

​https://devel.rtems.org/ticket/3598#comment:40
​https://devel.rtems.org/ticket/3598#comment:41

Compare with Git commit order:

​https://git.rtems.org/rtems/log/?id=eaa5ea84eaf1b3dab72d7a7a6578f0dc59e55396&qt=range&q=1947449a5d6f01a44ccc61eda3e78ef7e06da952..5fc727fe77a632f9df38161a8474007dab020608

[Amar Takhar]

Hmm, this is the order that git-rev gives it to the script. I'll play around and try to figure out.

Since there are only two commits I can't tell if it's simply reversed I'd need at least 4 multiple times to see if I can simply reverse the order to fix this.

[Chris Johns]

Why not create a test repo as a personal repo and add the hooks for testing?

[Sebastian Huber]

I pushed at least seven commits today in one rush:

​https://devel.rtems.org/ticket/3621

They show up in reverse order.

[Amar Takhar]

Okay great thanks all I need to do is reverse the order of the commits fed into the updater. I'll do that shortly.

[Amar Takhar]

Replying to Chris Johns:

Why not create a test repo as a personal repo and add the hooks for testing?

Because we use quite a few scripts that do unique things for RTEMS infrastructure. It would be a lot of work to get the same environment running elsewhere for a check that can be done the next time 4 commits are pushed at the same time. Outside of aesthetics the tickets are still being updated. I'm not sure where the offending area is but now I think I know we'll see.

[Amar Takhar]

Since this is never been a problem before I didn't notice that git rev-list by default shows reverse chronological order. I added --reverse to the commandline hopefully that fixes this issue.

Please let me know if this fixes the issue.

[Sebastian Huber]

Thanks, it works now:

​https://devel.rtems.org/ticket/3621#comment:11