Closed
Bug 1238800
Opened 8 years ago
Closed 7 years ago
travis is failing to run tox_env.sh for buildbot-configs
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jlund, Unassigned)
Details
log: https://api.travis-ci.org/jobs/101719246/log.txt?deansi=true snippet: Finished processing dependencies for buildbot===0.8.2-hg-7fb354d77dec-production-0.8 ERROR: InvocationError: '/home/travis/build/mozilla/build-buildbot-configs/tox_env.sh /home/travis/build/mozilla/build-buildbot-configs /home/travis/build/mozilla/build-buildbot-configs/.tox' ___________________________________ summary ____________________________________ ERROR: py27: commands failed irc: <jlund> "ERROR: InvocationError: '/home/travis/build/mozilla/build-buildbot-configs/tox_env.sh /home/travis/build/mozilla/build-buildbot-configs /home/travis/build/mozilla/build-buildbot-configs/.tox'" 16:13:37 <kmoir> yeah 16:16:47 <kmoir> my local test-master.sh still passes green for all master types 16:16:56 <kmoir> I need to learn more about how tox can fail 16:17:04 <kmoir> so I can fix it 16:17:16 <jlund> yeah, that's what I'm trying to grok atm 16:23:41 <jlund> kmoir: this is odd https://pastebin.mozilla.org/8856420 16:24:04 <jlund> iirc - there was a change to allthethings.json today? or how it was generated. somethign in email. 16:24:10 <jlund> I wonder if that's a fluke or related 16:24:39 <kmoir> yes there was I saw an email 16:25:23 <jlund> wonder if this is failing: https://dxr.mozilla.org/build-central/source/buildbot-configs/tox_env.sh#27
Comment 1•8 years ago
|
||
the buildbotcustom version of the tox_env.sh doesn't use allthethings.json 7:34 PM <kmoir> https://dxr.mozilla.org/build-central/source/buildbotcustom/tox_env.sh 7:34 PM <kmoir> and those tests are passing
Comment 2•8 years ago
|
||
kmoir or jlund can you please provide me more info on how can I simulate the script? Can I use taskcluster to do that or do I need to use docker?
Flags: needinfo?(kmoir)
Flags: needinfo?(jlund)
Comment 3•8 years ago
|
||
Just as a fyi Jordan fixed the issue last night, by backing out the changes armen had made here https://hg.mozilla.org/build/braindump/rev/47ecad7037b0
Flags: needinfo?(kmoir)
Comment 4•8 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #3) > Just as a fyi Jordan fixed the issue last night, by backing out the changes > armen had made here > https://hg.mozilla.org/build/braindump/rev/47ecad7037b0 Great, I didn't know . The bug can be closed ? I also removed the need info from :jlund
Flags: needinfo?(jlund)
Reporter | ||
Comment 5•8 years ago
|
||
yep. for now. Armen will either try to fix his patch or we will leave the working copy as is.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•8 years ago
|
||
hitting issues with this again: https://travis-ci.org/mozilla/build-buildbot-configs/jobs/106862376 log: py27 runtests: commands[0] | ./tox_env.sh /home/travis/build/mozilla/build-buildbot-configs /home/travis/build/mozilla/build-buildbot-configs/.tox abort: repository default not found! ERROR: InvocationError: '/home/travis/build/mozilla/build-buildbot-configs/tox_env.sh /home/travis/build/mozilla/build-buildbot-configs /home/travis/build/mozilla/build-buildbot-configs/.tox' ___________________________________ summary ____________________________________ ERROR: py27: commands failed
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 7•8 years ago
|
||
`abort: repository default not found!` is the best clue. unfortunately we don't get much output form tox_env.sh but this is likely while trying to 'pull' from a repo: http://hg.mozilla.org/build/buildbot-configs/file/22f1e00d700c/tox_env.sh#l13 and we end up having a bad hgrc (e.g. [paths] default), using a new version of hg, or something has changed at hgmo. I suppose this could be from a new travis 'worker' or change in venv installed versions.
Updated•7 years ago
|
Status: REOPENED → RESOLVED
Closed: 8 years ago → 7 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•