Skip to content
This repository has been archived by the owner on Sep 16, 2024. It is now read-only.

RUNBOT OCA does not build commits relative to the repository 11.0 #193

Open
jorgescalona opened this issue Jul 10, 2019 · 5 comments
Open

Comments

@jorgescalona
Copy link

Impacted versions:
11.0
An instance of tests was created via travis2docker of the OCA repo: runbot V11

Steps to reproduce:

  • The instance runs well and can be accessed via browser.
  • The runbot with gitlab integration module was installed.
  • Add the address ssh of the repo in gitlab in the repositories section of runbot.
  • The box is activated use gitlab.
  • A module to install was indicated.
  • From there the module will bring the corresponding branches to the configured repo.
  • The module will bring the corresponding builds to the configured repo.
  • When going to the web view: localhost/runbot, all the jobs in red are appreciated:
    image
  • Then when going to the logs, they are all blank 0 lines: logs/job_20_test_all.txt for example.
    image

Expected behaivor:

The normal of a runbot which creates the corresponding instances and logs, it is important to highlight that I have not made any modification to the code.

@moylop260
Copy link
Contributor

moylop260 commented Aug 12, 2019

Could you share the SHAs for each repository used?
And version of all pip packages

Could you share all logs from a red runbot build?

@jorgescalona
Copy link
Author

jorgescalona commented Aug 13, 2019

Hi @moylop260 I attach the file with the versions of the packages installed via pip
pip_freeze.txt

the gitlab repo for test is: https://gitlab.com/jorgemustaine/openacademy_v12 this repo runs the gitlab CI and is green so it executes the builds on that platform.

As I mentioned in the description of the issue it is not possible for me to share the generated logs since they are empty, As shown in the following screenshot:
logs_empty

I attached a video I just made, where it is appreciated this time that even the builds do not.

Finally, I must mention that i install via pip the following packages in the container docker:

  • watchdog
  • inotify
  • matplotlib
  • travis2docker

@moylop260
Copy link
Contributor

Check my last comment again, please.
You are sending me just one thing and I’m requesting 3

  • Sha of your repositories used.
  • All logs txt of the red builds (the logs records are empty, but I’m talking about the output txt logs base, all, run)

@jorgescalona
Copy link
Author

Sha of your repositories used.

I'm not sure what you need here, if the sha related to the last commit of the repository could be, that's why I shared the address of my repo. But the truth is I don't know what you need specifically. if that is the last sha is:
9edbbe36edf206c415055fa219279bcf4a1e6457

Logs are not generated. but I send you screenshots to see if they can help us.

runbot_build_information
status of builds is done and result is ko
status_of_build
finally the txt logs
full_base_log

@moylop260
Copy link
Contributor

If the first txt log was not generated so you need read the log of the main instance of odoo itself where runbot was started.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants