Encountering jiri issue while trying to run a previous commit

[waterlight m]

Hello,I have recently downloaded the latest version of Fuchsia and am trying to revert back to commit ed1641a804c68e01b44bd9bdf8d880f2b03e984a. I performed a git checkout operation and proceeded with the build. However, I encountered an error while using fx set core.x64. The error message is as follows:

ERROR at //src/connectivity/wlan/wlancfg/BUILD.gn:10:1: Can't load input file. import("//third_party/cobalt/metrics_registry.gni") ------------------------------------------------- Unable to load: /home/mdd/project/fuchsia/third_party/cobalt/metrics_registry.gni I also checked in the secondary tree for: /home/mdd/project/fuchsia/build/secondary/third_party/cobalt/metrics_registry.gni See //products/core.gni:33:3: which caused the file to be included. "//src/connectivity/wlan/wlancfg:wlancfg-core-shard", --------------------------------------------------- ERROR: error running gn gen: exit status 1

I believe this may be a mismatch issue with the third_party under prebuilt managed by jiri. I also switched the commit of the fuchsia/integration repository to the corresponding commit ofed1641a80, with the git log information excerpted below (only relevant information included):

commit 4cf31598f6809d5eb41a94ca862bce6e6f8fdee6 (HEAD) Original-Revision: ed1641a804c68e01b44bd9bdf8d880f2b03e984a

The output of jiri status is as follows:

mdd@vm ~/p/fuchsia ((ed1641a8…))> jiri status .: JIRI_HEAD: 9bec22f8c3b [netstack3] Make UDP recvfrom return zoned addresses where it can Current Revision: ed1641a804c [zircon] Add zx_socket_set_disposition system call Branch: DETACHED-HEAD(ed1641a804c [zircon] Add zx_socket_set_disposition system call) integration: JIRI_HEAD: 03b0645ea4 [roll] Roll fuchsia [netstack3] Make UDP recvfrom return zoned addresses where it can Current Revision: 4cf31598f6 [roll] Roll fuchsia [zircon] Add zx_socket_set_disposition system call Branch: DETACHED-HEAD(4cf31598f6 [roll] Roll fuchsia [zircon] Add zx_socket_set_disposition system call)

Additional Information: I have attempted using jiri update and fx sync-from-stem commands. However, both resulted in updating to the latest version. I am unsure if there's an incorrect usage or an issue elsewhere.

I am reaching out for any guidance or assistance to resolve this. Thank you for your time and consideration.

[Adam Barth]

You might want to try the -force-autoupdate=false flag for "jiri update".  It tells jiri to use the integration repository that you have locally instead of fetching the latest version from the server.  To use this flag, you'll want to use git to checkout the revision of the integration repository that you want to use and then have "jiri update -force-autoupdate=false" synchronize the rest of the source tree to match.  You can also try the -local-manifest flag, which is normally useful when you make local changes to your jiri manifests.

If those don't work, you can try manually setting the state of all the git repos to the revisions specified in the integration repository for the point in time you want to have locally.  After you do that, you'll still need to make all the prebuilt binaries match that version of the source tree, which you can do with the "jiri run-hooks" command.  However, it's highly preferable to have jiri get the right revisions of all the git repos.

Adam

--
All posts must follow the Fuchsia Code of Conduct https://fuchsia.dev/fuchsia-src/CODE_OF_CONDUCT or may be removed.
---
You received this message because you are subscribed to the Google Groups "discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss+u...@fuchsia.dev.
To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/discuss/586872af-91e0-444d-aae6-6ca9698a0ccdn%40fuchsia.dev.

[Adam Barth]

Sorry, I was slightly confused.  The flag to try is -local-manifest.  The -force-autoupdate flag is about the version of the jiri tool itself.

Adam

[waterlight m]

Thank you so much for taking the time to respond. Your assistance has been invaluable, and I truly can't express how grateful I am.
I used fx sync-from-stem, which included jiri update -local-manifest. The git version for integration changed to lock_at_4cf315.... However, I had an error with a repository: fatal: repository 'https://fuchsia.googlesource.com/third_party/rust-mirrors/rust-crypto/' not found.

Additionally, I encountered an issue with fx set core.x64:
mdd@vm ~/p/f/z/scripts ((ed1641a8…))> fx set core.x64
ERROR: Could not read file at //build/packages/prebuilt_test_manifest.gni:47:24.
...
ERROR: gn gen returned an exit status of 1.

Upon my investigation, it appears the file //prebuilt/third_party/chromium_tests/arch/x64/test_manifest.json is missing. I found the following manifest information in the current version of //integration/third_party/chromium/chromium:
<package name="chromium/fuchsia/tests-amd64"
         version="version:92.0.4515.93"
         path="prebuilt/third_party/chromium_tests/arch/x64"/>
I'm speculating there might have been a hiccup fetching this particular package. I'm unsure if I require additional configurations or if other reasons might be at play. Could you possibly guide me on this?
 Thank you once again for your invaluable support.

[Adam Barth]

On Fri, Oct 27, 2023 at 7:38 AM waterlight m <maag...@gmail.com> wrote:

Thank you so much for taking the time to respond. Your assistance has been invaluable, and I truly can't express how grateful I am.
I used fx sync-from-stem, which included jiri update -local-manifest. The git version for integration changed to lock_at_4cf315....

If I'm understanding correctly, you're looking at this revision:

https://fuchsia.googlesource.com/integration/+/4cf31598f6809d5eb41a94ca862bce6e6f8fdee6

... which is from 21 July 2021.

However, I had an error with a repository: fatal: repository 'https://fuchsia.googlesource.com/third_party/rust-mirrors/rust-crypto/' not found.

When I asks that URL directly in my browser, I get the following message:

"NOT_FOUND: Requested entity was not found"

I know we changed how we store our Rust dependencies at some point.  We now store our mirrors of Rust crates in https://fuchsia.googlesource.com/fuchsia/+/main/third_party/rust_crates/vendor/, although I don't see rust-crypto there.  It's quite possible that sometime between 2021 and now we removed the repository linked above, which is making it difficult to reconstruct a copy of the Fuchsia source tree as it was in 2021.

Additionally, I encountered an issue with fx set core.x64:
mdd@vm ~/p/f/z/scripts ((ed1641a8…))> fx set core.x64
ERROR: Could not read file at //build/packages/prebuilt_test_manifest.gni:47:24.
...
ERROR: gn gen returned an exit status of 1.

Upon my investigation, it appears the file //prebuilt/third_party/chromium_tests/arch/x64/test_manifest.json is missing. I found the following manifest information in the current version of //integration/third_party/chromium/chromium:
<package name="chromium/fuchsia/tests-amd64"
         version="version:92.0.4515.93"
         path="prebuilt/third_party/chromium_tests/arch/x64"/>
I'm speculating there might have been a hiccup fetching this particular package. I'm unsure if I require additional configurations or if other reasons might be at play. Could you possibly guide me on this?

If you use "jiri run-hooks -v", you'll get more information about the fetching of these prebuilts.  You can look through those logs to see if there's anything specific about this package.  It's also possible the error with the rust-crypto repository is causing jiri to give up on updating your source tree and therefore not downloading all the other pieces you need.

We do not regularly check that we can reconstruct source trees from multiple years in the past.  Obviously, retaining that ability is desirable, and we do try to keep that working on a best-effort basis, but I won't be surprised if we've unintentionally deleted some things that are needed to reconstruct the source tree from mid-2021.  It might still be possible to do (e.g., by changing the rust-crypto URL to point to a different git repository that you've populated with a copy of that crate from the right time period), but it might be a substantial amount of work depending on what difficulties you encounter.

Adam

[Adam Barth]

I wonder if your output directory has been corrupted as part of your working through the other issues.  You might try removing the output directory (rm -rf out) and then running "fx set core.x64" and "fx build" again.

Adam

On Fri, Oct 27, 2023 at 11:57 PM waterlight m <maag...@gmail.com> wrote:

Hello Adam,

Thank you so much for your previous guidance. It was incredibly helpful, and I've managed to resolve the initial issue based on your suggestions.

However, I've run into another challenge. While "fx set core.x64" works fine, I get a dependency cycle error with "fx build". The error is as follows:
ninja: Entering directory `/home/mdd/project/fuchsia/out/default'
ninja: error: dependency cycle: obj/src/connectivity/bluetooth/tools/dai-info/dai-info.stamp -> obj/src/connectivity/bluetooth/tools/dai-info/dai-info/meta.far -> obj/src/connectivity/bluetooth/tools/dai-info/dai-info.verify.stamp -> gen/src/connectivity/bluetooth/tools/dai-info/dai-info.verify -> dai-info -> obj/src/connectivity/bluetooth/tools/dai-info/dai-info.stamp

I'd appreciate any guidance or suggestions you might have regarding this issue.
Thank you once again for your continued support. It truly means a lot.

[Adam Barth]

Glad to hear it!

Adam

On Sun, Oct 29, 2023 at 12:38 AM waterlight m <maag...@gmail.com> wrote:

Thanks to your thorough and persistent responses, my issue has been resolved. I truly appreciate the time and effort you invested in assisting me. Thank you so much!

[waterlight m]

Hello Adam,

Thank you so much for your previous guidance. It was incredibly helpful, and I've managed to resolve the initial issue based on your suggestions.

However, I've run into another challenge. While "fx set core.x64" works fine, I get a dependency cycle error with "fx build". The error is as follows:
ninja: Entering directory `/home/mdd/project/fuchsia/out/default'
ninja: error: dependency cycle: obj/src/connectivity/bluetooth/tools/dai-info/dai-info.stamp -> obj/src/connectivity/bluetooth/tools/dai-info/dai-info/meta.far -> obj/src/connectivity/bluetooth/tools/dai-info/dai-info.verify.stamp -> gen/src/connectivity/bluetooth/tools/dai-info/dai-info.verify -> dai-info -> obj/src/connectivity/bluetooth/tools/dai-info/dai-info.stamp

I'd appreciate any guidance or suggestions you might have regarding this issue.
Thank you once again for your continued support. It truly means a lot.

[waterlight m]

Thanks to your thorough and persistent responses, my issue has been resolved. I truly appreciate the time and effort you invested in assisting me. Thank you so much!