action #174607
open[openQA-in-openQA] test fails in single_container_webui: [Pipe::Sass] Could not compile "stylesheets/openqa.scss" Invalid US-ASCII character
0%
Description
Observation¶
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_from_containers@64bit-2G fails in
single_container_webui
Relevant error message:
[Pipe::Sass] Could not compile "stylesheets/openqa.scss" with opts={"include_paths" => [bless( do{\(my $o = "/usr/share/openqa/script/../assets/stylesheets")}, 'Mojo::File' ),bless( do{\(my $o = "/usr/share/openqa/script/../assets")}, 'Mojo::Home' )]}: /usr/share/openqa/assets/stylesheets/overview.scss:6: Invalid US-ASCII character "\xE2" (Sass::SyntaxError)
from (sass):24
Test suite description¶
Reproducible¶
Fails since (at least) Build :TW.33524 (current job)
Expected result¶
Last good: :TW.33523 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by jbaier_cz about 3 hours ago
- Related to action #162503: AssetPack should fail if sass fails size:M added
Updated by okurz about 3 hours ago
- Tags changed from alert, openqa-in-openqa to alert, openqa-in-openqa, reactive work
- Priority changed from High to Urgent
- Target version set to Ready
Updated by jbaier_cz about 3 hours ago
- Status changed from New to In Progress
- Assignee set to jbaier_cz
Updated by jbaier_cz about 3 hours ago
This was not what I expected. The issue is of course with the non-ascii character inside overview.scss, where we have
&:first-child:before {
content: "•";
}
The issue can be reproduced with podman:
podman run --rm -ti opensuse/leap:15.6 bash -c 'zypper ar -p 95 -f http://download.opensuse.org/repositories/devel:openQA/15.6 devel_openQA && zypper ar -p 90 -f http://download.opensuse.org/repositories/devel:openQA:Leap:15.6/15.6 devel_openQA_Leap && zypper --gpg-auto-import-keys ref && zypper in -y ca-certificates-mozilla curl openQA-local-db apache2 apache2-utils hostname which w3m "rubygem(sass)>=3.7.4" && cd /usr/share/openqa/assets && sass -I . stylesheets/openqa.scss'
What is the funny part, it is just the sass
reading the locale and deciding not to use UTF-8 support (the default locale in the container is POSIX
), so just adding LC_ALL=C.UTF-8
into the environment is enough to make this issue go away.
I will make the appropriate PR for our Dockerfiles, but I am not entirely sure if we should address that issue in some other way?
Updated by jbaier_cz about 2 hours ago
- Status changed from In Progress to Feedback
- Priority changed from Urgent to Normal
For our containers, https://github.com/os-autoinst/openQA/pull/6088 should be enough to make sure sass will not fail. Also it seems that although the core issue is 100% reproducible, the job will fail only sporadically, maybe the sass is not always recompiling the assets?