meta potbot: reporting against incorrect changesets

[netweb]

meta potbot is reporting against incorrect changesets.

Example:

• potbot made a commit, r1025 6 days ago
• potbot believes this was against r1024
• it was in fact against r962 from four weeks ago

Expected:

• potbot runs against most recent commit and reports correct changeset

[netweb]

Nacin in Slack ​here

"..it simply says it is generating the current revision, not the actual revision a string might have been changed from. so it's "current to rev 1080"

This makes sense, thus making 90% of this ticket worksforme.

The only thing is the timeliness of potbot's runs, is this automated or manually run?

If automated a little more frequently than once a month would be beneficial IMHO.

[nacin]

It runs every hour but it'll only commit anything if there's something to commit.

[netweb]

Replying to nacin:

It runs every hour but it'll only commit anything if there's something to commit.

Has this changed recently? Per the original ticket r1025 was committed four weeks after the r962 commit

[netweb]

Also r1081 was only a date (year) change in wpmobileapps.pot, the previous string change in that repo was that same r962 commit mentioned above ~8 weeks ago.

If potbot believes that the year change is valid enough to run for a date change withwpmobileapps.pot should it not then run the same for other .pot files throughout meta?

[nacin]

Replying to netweb:

Has this changed recently? Per the original ticket r1025 was committed four weeks after the r962 commit

It is occasionally disabled (or broken or frozen). It was un-frozen on December 4.

should it not then run the same for other .pot files throughout meta?

It only runs for .pot files for which it is configured to run.

[netweb]

Thanks, makes sense now :)