Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable color logs in CI #15719

Open
wants to merge 2 commits into
base: devel
Choose a base branch
from
Open

Conversation

AlanCoding
Copy link
Member

SUMMARY

Trying to further cleanup the logs you can download as an artifact after a test run.

ISSUE TYPE
  • Bug, Docs Fix or other nominal change
COMPONENT NAME
  • API

@AlanCoding
Copy link
Member Author

This is the next step after #15717

@AlanCoding
Copy link
Member Author

As of opening this, working for:


2024-12-19 16:28:03,390 WARN exited: awx-rsyslogd (exit status 1; not expected)
2024-12-19 16:28:03,392 INFO spawned: 'awx-rsyslogd' with pid 2014
rsyslogd: could not open config file '/var/lib/awx/rsyslog/rsyslog.conf': Permission denied [v8.2102.0-106.el9 try https://www.rsyslog.com/e/2104 ]
rsyslogd: run failed with error -2104 (see rsyslog.h or try https://www.rsyslog.com/e/2104 to learn what that number means)
2024-12-19 16:28:03,401 INFO success: awx-rsyslogd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
awx-rsyslogd stderr | rsyslogd: could not open config file '/var/lib/awx/rsyslog/rsyslog.conf': Permission denied [v8.2102.0-106.el9 try https://www.rsyslog.com/e/2104 ]
awx-rsyslogd stderr | rsyslogd: run failed with error -2104 (see rsyslog.h or try https://www.rsyslog.com/e/2104 to learn what that number means)
awx-rsyslogd stderr | 

still not working for

WARNINGS:
�[33;1m?: (staticfiles.W004) The directory '/awx_devel/awx/ui/build' in the STATICFILES_DIRS setting does not exist.�[0m
�[36;1mOperations to perform:�[0m
�[1m  Apply all migrations: �[0mauth, conf, contenttypes, dab_rbac, dab_resource_registry, flags, main, sessions, sites
�[36;1mRunning migrations:�[0m
  Applying contenttypes.0001_initial...�[32;1m OK�[0m
  Applying contenttypes.0002_remove_content_type_name...�[32;1m OK�[0m
  Applying auth.0001_initial...�[32;1m OK�[0m
  Applying main.0001_initial...�[32;1m OK�[0m
  Applying main.0002_squashed_v300_release...�[32;1m OK�[0m

I think these are specific to management commands.

@AlanCoding
Copy link
Member Author

Lifecycle is good

2024-12-19 16:26:39,267 INFO     [-] awx.analytics.job_lifecycle projectupdate-1 waiting {"type": "projectupdate", "task_id": 1, "state": "waiting", "work_unit_id": null, "task_name": "project-with-requirements"}

ok, this covers the main thing I wanted.

@AlanCoding
Copy link
Member Author

Looking much better:

System check identified some issues:

WARNINGS:
?: (staticfiles.W004) The directory '/awx_devel/awx/ui/build' in the STATICFILES_DIRS setting does not exist.
Operations to perform:
  Apply all migrations: auth, conf, contenttypes, dab_rbac, dab_resource_registry, flags, main, sessions, sites
Running migrations:
  Applying contenttypes.0001_initial... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0001_initial... OK
  Applying main.0001_initial... OK

Very happy with this now.

@AlanCoding AlanCoding marked this pull request as ready for review December 19, 2024 18:34
@if [ "$(VENV_BASE)" ]; then \
. $(VENV_BASE)/awx/bin/activate; \
fi; \
supervisord --pidfile=/tmp/supervisor_pid -n
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've grown kind of tired of this pattern of make-calls-docker, then docker-calls-supervisord-entrpoint, then supervisord-calls-make.

While we could get more explicit about documenting "these targets are ran inside docker" vs "these targets are ran outside docker", in this case it makes more sense to just delete the unnecessary step.

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

Successfully merging this pull request may close these issues.

2 participants