[Chromium] failed to access specific tag

[pcorbineau]

Hey guys, I want to test your build system with a complex example build.

For this I test to build a specific version of https://github.com/chromiumembedded/cef/ that required https://github.com/chromium/chromium as dependency.

I write this .tipi/deps file :

{
    "chromiumembedded/cef": {
        "@": "5481",
        "requires": {
            "chromium/chromium": {
                "@": "110.0.5481.0"
            }
        }
    }
}

I can access to specific tag https://github.com/chromium/chromium/tree/110.0.5481.0 but tipi failed to get it.

PS C:\Users\pcorbineau\Documents\personal_workspace\tipi_sandbox> tipi -t windows .
Looking for 4 files
Found cache meta
 - Checking cache status for: chromiumembedded/cef<605475778197b8725fc2659a58859cc46974516b> ⚙️ update required
chromiumembedded/cef up-to-date check.
- done.
 ⚙️ querying and downloading cache for chromiumembedded/cef@: 5481 [605475778197b8725fc2659a58859cc46974516b]
- done.
Fetching : https://github.com/chromiumembedded/cef.git
- done.
chromiumembedded/cef@: 5481 [605475778197b8725fc2659a58859cc46974516b]
Looking for 2115 files
chromium/chromium up-to-date check.
- done.
● [err] Dynamic exception type: class std::runtime_error
std::exception::what: err : error:0 OKstatus: 502 accessing : https://api.github.com/repos/chromium/chromium/git/refs/tags
● [err] Something went wrong, for help on your issue, we would enjoy getting your report at https://tipi.build/#contact

Any idea how to deal with it ?

Here is the simple code to test it :

#include <iostream>

#include <include/cef_process_message.h>

int main(){
  auto message = CefProcessMessage::Create("test");

  auto args = message->GetArgumentList();
  args->SetString(0, "Hello");
  args->SetString(1, "World");

  auto arg0 = args->GetString(0);
  auto arg1 = args->GetString(1);

  std::cout << arg0 << " " << arg1 << std::endl;

  return 0;
}

[daminetreg]

Thanks for the great report, it seems that the specific tag is not on any branch which seems to get our clone implementation based on libgit2 to fail.

I think tipi will not be able to compile Cef with source scan as of today and need some special cmake middleware to get it right, but your specific issue you reported can definitely be fixed in changing the way we clone repositories.

[daminetreg]

We will dig into that and reach back.

[pcorbineau]

chromium builds are so big that your build system could be a game changer 🙏

[daminetreg]

chromium builds are so big that your build system could be a game changer 🙏

Thanks, we have users doing it with the chromium build system and using the cloud build nodes via the command :

tipi -t linux -j128 .run chrome-build-cmd

But then you don’t get our caching and all the speed up, only the cpu counts. We are going to make it work out of the box, we will reach back.