repo v2.29.6 prerelease

[LaMont Jones]

I have created a new release, but not yet pushed it live.  Instead, people have to opt-in to it by passing --repo-rev=main when running `repo init`.  You can then run `repo selfupdate && repo version` to double check your local state.

So please bang on things and let us know how it goes.  Even "it works" is useful feedback as it means I'm not the only one running it :).
If things look good the rest of this week, I'll publish it next week.

The changes since v2.29.5 are:

859d3d9 (Woody Lin) GitcInit: fix gitc-init failure
fa8d939 (LaMont Jones) sync: clear preciousObjects when set in error.
a6c52f5 (Joanna Wang) Set tracing to always on and save to .repo/TRACE_FILE.
0d130d2 (Peter Kjellerstedt) tests: Make the tests pass for Python < 3.8

Enjoy,

[Peter Kjellerstedt]

What is the point of repo now outputting:

 

    Trace outputs in <path to work dir>/.repo/TRACE_FILE

 

every time  repo sync is run? That file’s location is not likely to change, is it?

 

//Peter

 

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/CAMQmaoMgTcrn61TQe5yPSDp7i7Cs_ruu%2BorOeYY6v%3Do2zAyWxA%40mail.gmail.com.

[LaMont Jones]

On Sat, Nov 5, 2022 at 8:55 AM Peter Kjellerstedt <peter.kje...@axis.com> wrote:

What is the point of repo now outputting:

     Trace outputs in <path to work dir>/.repo/TRACE_FILE

every time  repo sync is run? That file’s location is not likely to change, is it?

I believe that output will go away in the near future - it's more of a confirmation that the version being used (in pre-existing automated jobs) has the logging.

[LaMont Jones]

I have pushed v2.29.6 to the stable branch.

[elzoc...@gmail.com]

Hi,

Had a couple of crashes [1] today related to the above TRACE_FILE.

In my setup, /data/jenkins/workspace/ is a separate drive, and apparenly "os.rename only works if source and destination are on the same file system." source stackoverflow [2]
OS where tmp is mounted as a tmpfs would probably have the same issue.


[1]
$ repo manifest

... A new version of repo (2.29) is available.
... New version is available at: /data/jenkins/workspace/test-cedric/h5chgmpp/.repo/repo/repo
... The launcher is run from: /bin/repo
!!! The launcher is not writable.  Please talk to your sysadmin or distro
!!! to get an update installed.

Trace outputs in /data/jenkins/workspace/test-cedric/h5chgmpp/.repo/TRACE_FILE
Traceback (most recent call last):
  File "/data/jenkins/workspace/test-cedric/h5chgmpp/.repo/repo/main.py", line 698, in <module>
    _Main(sys.argv[1:])
  File "/data/jenkins/workspace/test-cedric/h5chgmpp/.repo/repo/main.py", line 666, in _Main
    with Trace('starting new command: %s', ', '.join([name] + argv), first_trace=True):
  File "/data/jenkins/workspace/test-cedric/h5chgmpp/.repo/repo/repo_trace.py", line 84, in __init__
    _ClearOldTraces()
  File "/data/jenkins/workspace/test-cedric/h5chgmpp/.repo/repo/repo_trace.py", line 142, in _ClearOldTraces
    os.replace(temp.name, _TRACE_FILE)
OSError: [Errno 18] Invalid cross-device link: '/tmp/tmp956_dwbb' -> '/data/jenkins/workspace/test-cedric/h5chgmpp/.repo/TRACE_FILE'


[2] https://stackoverflow.com/questions/42392600/oserror-errno-18-invalid-cross-device-link