VersionNotSetError: builder must call SetVersionInfo first in lumpy-incremental-paladin |
|||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-incremental-paladin/builds/10967/steps/BuildPackages%20%28pre-Patch%29/logs/stdio The paladin has failed the last 5 runs in the same stage. I suspect it's in some bad state, but just in case here are the CLs common to all 5 runs. 5 portage-stable | vapier | 428970 5 portage-stable | vapier | 428950 5 platform2 | vapier | 428951 5 firmware | hungte | 428513 5 autotest | briannorris | 428551
,
Jan 18 2017
Adding more people who worked on related code recently.
,
Jan 18 2017
semenzato@luigi:~/.../chromite/cbuildbot/stages$ git show 9a58098e8 This shows that a change from 12/17 is using self.archive_path, which was not used before. That member is a "property", that is it causes the invocation of user-defined methods. The failure occurs in one of that methods.
,
Jan 18 2017
,
Jan 18 2017
,
Jan 18 2017
Could you elaborate what the issue is with using the archive_path? Looking into the builds more..
,
Jan 18 2017
Hmm. Yep, that makes sense. chingcodes@ on the incremental builder, we run BuildPackages twice : once with the tree prior to applying test patches, and once after. During that first phase, cbuildbot doesn't yet know the version name of the build that we are testing (that gets defined later on in CommitQueueSyncStage) and so apparently self.archive_path is therefore undefined. I think you should modify your logic to catch the VersionNotSetError there if it is raised, and if so simply not do the build event logging. We can leave a TODO behind to untangle the problem better eventually.
,
Jan 18 2017
Ok, added quick catch of VersionNotsetError. https://chromium-review.googlesource.com/#/c/430092/
,
Jun 29 2017
,
Jan 22 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by semenzato@chromium.org
, Jan 18 2017