Page MenuHomePhabricator

Correctly detect new version of xhpast build
ClosedPublic

Authored by richardvanvelzen on May 19 2016, 10:52 AM.
Tags
None
Referenced Files
F19937417: D15945.diff
Sun, Apr 12, 11:33 PM
F19617005: D15945.id38398.diff
Feb 4 2026, 4:22 AM
F19547574: D15945.id38395.diff
Jan 26 2026, 9:57 AM
F19520758: D15945.id.diff
Jan 16 2026, 4:38 PM
F19517282: D15945.diff
Jan 15 2026, 9:27 AM
F19507282: D15945.diff
Jan 9 2026, 7:04 PM
F18845664: D15945.id38395.diff
Oct 29 2025, 1:46 PM
F18843752: D15945.diff
Oct 29 2025, 12:38 AM
Subscribers

Details

Summary

When running lint after xhpast is updated, it tests whether the version is up-to-date. Because the version isn't reset before the test, it would think that the build failed, requiring a second run of lint

Test Plan

Downgraded xhpast, ran lint. Saw broken xhpast, but correct xhpast on second run. Applied patch, and got correct lint results regardless of version.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

richardvanvelzen retitled this revision from to Correctly detect new version of xhpast build.
richardvanvelzen updated this object.
richardvanvelzen edited the test plan for this revision. (Show Details)
richardvanvelzen added a reviewer: epriestley.

Not really high-prio, but a minor annoyance after getting a fresh xhpast version.

epriestley edited edge metadata.
This revision is now accepted and ready to land.May 19 2016, 1:53 PM
chad added a reviewer: chad.
This revision was automatically updated to reflect the committed changes.