<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <br>
    <div class="moz-cite-prefix">On 1/6/16 1:52 PM, Martin von
      Zweigbergk wrote:<br>
    </div>
    <blockquote
cite="mid:CAESOdVAQo1qoU5JLudK4oybDGKU60kStUqrp4kmMrOV9xJVdhg@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr">
        <div class="gmail_quote">
          <div dir="ltr">On Wed, Jan 6, 2016 at 1:45 PM Laurent
            Charignon <<a moz-do-not-send="true"
              href="mailto:lcharignon@fb.com" target="_blank">lcharignon@fb.com</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div style="word-wrap:break-word">
              <div>
                <blockquote type="cite">
                  <div>On Jan 6, 2016, at 1:39 PM, Martin von Zweigbergk
                    <<a moz-do-not-send="true"
                      href="mailto:martinvonz@google.com"
                      target="_blank">martinvonz@google.com</a>>
                    wrote:</div>
                  <br>
                  <div>
                    <p dir="ltr">I would not expect our tests to work on
                      other projects, and it seems unfortunate to
                      include knowledge of a specific other project
                      (lz4revlog) in hg core, even though the other
                      project may be related to hg.</p>
                    <div><br>
                    </div>
                  </div>
                </blockquote>
                <div><br>
                </div>
              </div>
            </div>
            <div style="word-wrap:break-word">
              <div>
                <div>Ok, I will find another way to make it work...</div>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
        </div>
        <div dir="ltr">
          <div class="gmail_quote">
            <div>If the goal was to be able to use extensions that add
              requirements on an hg core clone, I would be more open to
              it. Let's say you were instead using lz4revlog on hg core,
              would tests fail then? I can imagine they would since your
              ~/.hgrc is not read (right?). Perhaps the test runner
              could export a ORIG_HOME or so pointing to your ~ and we
              could do 'HOME="$ORIG_HOME" hg locate'? I don't know if we
              care enough about enabling extensions on hg core repos
              that we want to complicate our tests, though. What do you
              think? Others?</div>
          </div>
        </div>
        <div dir="ltr">
          <div class="gmail_quote">
            <div> <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    Yes, this applies to hg core too.  If hg core is cloned with lz4,
    all of the test-check-* tests fail because they run hg with all
    extensions disabled (which is desirable for the actual test
    invocations, since it means they are consistent regardless of system
    settings).<br>
    <br>
    Maybe we can add a hg_sys command that is available inside the test
    suite and allows us to run the normal system Mercurial without all
    the configs disabled?<br>
    <br>
    It's not specific to home directories though (we have system wide
    hgrc's that need to be loaded too).<br>
  </body>
</html>